Make adoption input guidance executable from the CLI

[iperev]

Summary

• Add on-demand, command-owned input guides for materialization and first-source authoring. One connected example links requirement sources, bindings and test inventory; the source plan is obtained from the CLI, not fabricated.
• Exercise the original published commands, modes, pointers and launcher through whole-CLI tests and the existing installed-carrier smoke runner. Preserve owner review, native execution and exact plan/apply boundaries.
• Clarify aggregate inventory contract v2 versus direct inventory schema v1 without changing accepted inputs. Preserve the remaining ABI and frozen fixtures.
• Prepare compatible release 0.14.5 and retain optional hosted-browser publication as deferred design work only.

Validation

Candidate: a6129cfb3a76b381cd09c2ee1d4fd90c88c6113d.
Base: ab83b7668c169e801c272ccae6f166fe0ccc720b.

• Full npm run check passed with pinned npm 12.0.2 on the clean, unchanged committed candidate, including 315 browser tests.
• Whole-CLI example extraction, three intent modes, child admission, plan/apply and written-record re-admission passed. Broken-link and launcher variants are covered.
• Three retained guide-operand mutants fail the intended assertions; the installed carrier mutation table also passes.
• Exact source comparison found one declared inventory-summary change and 19 generated native-source digest updates in the machine contract, with every other parsed value unchanged. Nineteen historical fixture entries retain their exact Git identity.
• The release-note expectation repair is exactly five changed lines; its independent before/after review retains the existing negative oracles.
• git diff --check passed. Provider checks remain a separate merge prerequisite.

Review Boundaries

No confirmed actionable finding remains in this bounded patch after independent review and self-review. The review does not establish universal architectural optimality, hard reviewer-host isolation, measured cognitive/token superiority or exhaustive optional-field coverage. Those limits are retained rather than represented as a passing perfection audit.

Fresh CLI-only no-specification/no-test journeys, the full recovery matrix, StrictDoc/OpenSpec comparison and source-codec decisions remain separate work. The synthetic guide does not authorize real writes, approve product meaning, prove native test execution or complete the roadmap.

Merge And Release

Merge only after all applicable exact-head checks pass, using squash with an empty body. Verify the merged tree, signature and postmerge checks before separately publishing and verifying npm, PyPI and GitHub release identities.