Clarify specification context and scenario ownership

[iperev]

Summary

• Add a lazy connected catalog/tree example to requirement-context-compose --help, using the tree owner's canonical projection.
• Explain exact working-tree/index/commit/artifact review subjects and link the existing current-subject guide to canonical context capture.
• Strengthen whole-CLI oracles for complete binding provenance, existing-but-unrelated nodes, exact rejection causes and normative guidance polarity.
• Document the bounded scenario-storage decision and close the completed traceability design work. Prepare the compatible 0.14.19 release record, including the earlier source-intake guidance.

Validation

• Full npm run check passed on exact committed head 20b2a741335f96cf0fe6c55896485c64fded7779: 333 browser tests, package/wheel checks, self-hosting 109/109 requirements and 382 scenarios, coverage and release closeout.
• Selected positive CLI tests pass; three mutations that survived the initial oracles now fail for the intended reasons.
• All CLI contract fields except 18 native-source canonical digests are unchanged; generated projections and the ABI golden are current.
• External synthetic qualification exercised two source namespaces, TypeScript/FastAPI, parameterized and many-to-many routes, native failure/skip/missing/currentness controls, a real cooperative Git check and 14 explicit source-intake/materialization cases. Exact retained artifacts were re-admitted through the current candidate CLI.
• Four original/final static review lanes identified the local oracle gaps; repairs were checked independently. Two additional reviewers confirmed the current oracle structure while correctly leaving unsupplied runtime artifacts unverified; root separately rehashed and replayed those exact bodies.

Boundaries

Public requirement-source v1 remains active. No new scenario schema, generic native runner, automatic semantic scan, approval service or Git hook is installed. Local observations are not producer authentication or provider enforcement. Pinned StrictDoc/OpenSpec trials and four count-only inputs are not a universal superiority or human-usability result. Human format qualification and the remaining source transition remain open.

Product design/implementation plans and private pilot artifacts are not added to the package or repository. Existing public instructions retain the reusable conclusions.