[carlrannaberg]

Template selection could expand into reading multiple full contracts, and the generic “document template” fallback pointed to no real filename. Project recap also hid its required retrospective taxonomy below the selection sections.

This two-file change makes selection use metadata and Use/Do-not-use sections, permits a targeted section read for a specific unresolved fit question, and loads the full chosen contract at Build step 1. It names Report as the prose-led fallback and moves Project recap’s existing eligibility rules into Use when without duplicating them or changing its section requirements.

Validation:

• Package and authoring checks pass; four pre-existing easing warnings remain.
• Strict inventory: 35 template contracts. Preview matrix: 34 generated fixtures, all passing strict detection.
• Two fresh subagents received only a workspace assignment, the supplied skill, and a normal artifact request. No template choice, read count, suspected failure, or selection procedure was supplied in their task prompts; no follow-up coaching occurred.
• Raw calls/results show selection-section extraction, then exactly one full template loaded into context per trial: Report for a results-only pilot recap, Project recap for a Shipped/Skipped/Shifted/Learned weekly retrospective. The extraction scripts read files locally but expose only selection sections.
• Both generated artifacts preserve the supplied facts, pass detector/contrast checks, and render without horizontal overflow on desktop and phone. Optional favicon/social metadata warnings remain.
• Two fresh independent final reviewers found no issues.

Evidence limits: direct skill-path tests cover procedure following, not automatic activation or statistical reliability. The results agent read mandatory host bootstrap instructions before its isolated workspace; the retrospective trial stayed in its workspace. Empty recap sections and tally rendering were not exercised; their existing instructions are preserved. Plaintext task prompts, source hashes, complete tool call/result snapshots, and rendered artifacts are saved locally under temp/template-selection/.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}