Document PR

Improve the PR description, not the implementation. Read code only to understand and verify behavior. Propose a complete replacement body and wait for approval before changing GitHub.

Principles

• Explain what changed and why in natural, concrete language.
• Keep small PRs to a short paragraph. Use bullets only when they improve scanning.
• Remove template debris, release-note tone, hype, repeated commits, and implementation trivia.
• Never claim behavior, tests, or evidence that was not verified.
• Every independently reviewable behavior needs its own relevant before/after proof.
• A written explanation is not proof. Use it only after exhausting practical capture options.
• Source code is context, never behavioral proof. Reviewers can already read the diff.

Temporary workspace

Before generating anything, create one OS-managed temporary root: