<!--
Maintainer-owned PRs may use a shorter body. Community PRs must keep these sections.
Write for reviewers: explain why this change is right, not every line that changed.
-->

## Intent

<!-- What problem does this solve? Link the issue if one exists. -->

Issue:

<!-- Use Closes/Fixes only when this PR fully resolves the issue. Use Refs or N/A otherwise. -->

## Approach

<!-- Explain the fix shape or design choice. Avoid a file-by-file change list. -->

## Scope

Primary area:

Why this belongs in this repo:

<!-- Printed-CLI-only fixes belong in the generated CLI or public library repo. If the symptom came from a printed CLI, explain the general Printing Press behavior this changes. -->

## Risk

<!-- What could this break? Include generated output, MCP surface, auth, catalog, publish flow, verifier, scorer, or release behavior if relevant. -->

N/A

## Output Contract

<!-- Required only if this PR changes templates, generated files, manifests, command output, MCP schemas, scorecard output, catalog rendering, or pipeline artifacts. Otherwise write "N/A". -->

N/A

## Verification

<!-- List commands actually run. Say "Not run" with a reason if not run. -->

## AI / Automation Disclosure

- [ ] No AI or automation was used
- [ ] Human-reviewed: AI or automation was used, and a human reviewed the work for intent, fit, and obvious issues before submission
- [ ] AI-reviewed only: an AI agent reviewed the work, but no human reviewed it before submission
- [ ] Fully automated: generated and submitted without human review for this specific change
