WP15: proposal package — README first screen, docs/ tree with R16, adoption artifacts

[HeliCorgi]

Implements spec §6 WP15 (§269–285) + R16. Completes the WP10–WP15 chain.

What this adds

• README restructured to the spec first-screen order (~150 lines): verbatim §1 blurb, the placeholder-independent core up front, compact generated digest blocks, the exact L-tagged safety formula, one-command reproduce, honesty one click away. The adversarial cold-read verdict (skeptical-engineer persona): "CORRECT and honest — no overclaim on the first screen", with the headline 0.285× verified against the committed CSV (0.285218).
• docs/ tree (14 files): concept (with the counterfactual paragraph — ClearSpace-1 ~€86M/~2028, ADRAS-J2 ~¥13.2B/FY2027–28 hedged, live-web re-verified — and the installer-niche statement), technical_architecture, gnc, safety (full WP5 + WP12 ladder tables as generated blocks), target_selection (full sail sweep + WP13 kit + class-C blocks), cost_model (full WP6 block; WP14 anchor by reference), legal_regulatory, limitations, roadmap, pitch_agencies (self-framed "adoption brief — NOT a mission proposal", agency-agnostic per spec §1), one_pager, technical_summary_5p, pitch_deck (12-slide md source), release_engineering.
• R16 enforced, not aspirational: new tools/docs/fill_docs_numbers.py regenerates every DOCS-* marker block from committed CSVs (+ docs_numbers ctest); the claims-audit gains a docs/ sweep (R15 pin-list outside marker blocks, banned words with honest-discussion carve-outs, mandated-file-list check — enforcement scope documented, mirroring the R14 pattern-list precedent); the CI reproducibility gate now covers docs/ (generated + evidence + README + docs, all SHA-stable — validated live in this PR's runs).
• Comment-only sweep of 9 C++ files repoints stale "see README" comments at the moved docs/ homes (verified comment-only by diff scan).

Disclosed items (spec §10)

1. DOI deferred: the exact Zenodo procedure is documented in docs/release_engineering.md; execution awaits an owner-provided account (spec:279–282 "considered and documented" path). A git tag + GitHub release land at this merge.
2. release_engineering.md flags two owner decisions found during the work: CMakeLists.txt project(VERSION 4.0) is not in lockstep with the git-tag scheme, and WP13/WP14 merged without phase tags (backfill vs accept).
3. R16 numeric enforcement is a pin-list scan (not a blanket no-digits rule — DOIs/years/citations would false-positive); scope documented in the audit.
4. One R16 one-home nit: the archived 0.014 baseline appears in 3 places as contextual cross-references to the same archived pin (safety BEFORE/AFTER home, tag rationale, changelog) — judged defensible by the verifier.

Verification

• CI fully green ×2 (build + 18 ctest incl. new docs_numbers + both fillers + the extended 4-path gate).
• Mandatory adversarial verification (spec §10): one blocker found — the 5-page technical summary was missing the binding anchor phrase "Kessler-precursor removal" (spec §1) — fixed and re-verified. All other attacks passed: 8+ hand-typed numbers spot-checked against CSVs (exact), ladder table exact vs wp12_ladder.csv, forbidden-phrase sweep clean, 151 relative links resolve, pitch-vs-disclaimer consistency confirmed (the adoption brief self-rates its agency-decision-moving probability LOW — anti-overclaim by design).

🤖 Generated with Claude Code