Crosswalk public surfaces and bind bounded execution evidence

[Riverbraid]

What changed

Pre-P0 v0.3 control-package alignment

• Updates docs/F0_F4_CONTROL_PACKAGE_SOURCE_CUSTODY.md so v0.3-proposed is the current proposed basis and v0.2-proposed is preserved only as historical lineage.
• Updates docs/F0_F4_GITHUB_COMPARISON_PREPARATION.json to schema version 2.0.0, covering all eight current preparation pull requests and the current v0.3 source-role boundary.
• Records the known pre-P0 identity split:
  • current v0.3 manual digest prefix: 1643b9d9;
  • legacy machine-package manual digest prefix: 5a6be223.
• Adds docs/PRE_P0_GITHUB_HANDOFF.md and docs/PRE_P0_GITHUB_HANDOFF.json to freeze the exact bounded GitHub preparation subjects and prohibit treating draft-head evidence as adoption or F0–F4 closure.
• Opens issue Rebind pre-P0 machine package to v0.3 before founder adoption #27 as the explicit PRE_P0_HOLD / IDENTITY_REBIND_REQUIRED tracker.

Public repository and control-package crosswalks

• Adds docs/PUBLIC_REPOSITORY_CLASSIFICATION_CROSSWALK.md to keep role, lifecycle, registry membership, verification depth, and future F3/F4 membership separate.
• Preserves the F0–F4 source-custody boundary: the actual current package bytes remain outside GitHub and are not uploaded, normalized, adopted, or executed by this PR.

Evaluation Kit evidence and supply-chain boundaries

• Converts docs/evidence-plans/EVALUATION_KIT_ALLOWLIST.md into an attributable record for exact head 868341e2a26ae1ac912be170a2930034b06623ee, run 30286309516, job 90044856022.
• Records command allowlisting, negative command denial, lifecycle-script denial, digest-bound Docker identity, and full pinned-profile execution.
• Preserves the remaining OS/npm network acquisition, registry-freshness, verification-depth, and independence boundaries.

Repository-specific evidence states

• Converts docs/evidence-plans/REFUSAL_GOLD_FAIL_CLOSED.md into an exact draft-head positive/negative execution record.
• Reclassifies docs/evidence-plans/HARNESS_GOLD_GPG_BINDING.md as BLOCKED_BY_SOURCE_CONTRACT, preserving GPG execution as NOT_ASSESSED.
• Converts docs/evidence-plans/GOLD_V2_DEPENDENCY_BOUNDARY.md into an exact draft-head local-build and optional-workspace unavailable-state record.
• Converts docs/evidence-plans/PHASE_2_6_PETAL_DEPTH_EXECUTION.md into a differentiated pinned-commit depth record:
  • Memory-Gold: multi-vector behavioral verifier;
  • Judicial-Gold: canonical-vector behavioral check;
  • Safety-Gold: canonical-vector behavioral check;
  • Integration-Gold: canonical coherence check, not F3 integration.

Seven-repository scaffold execution

• Adds docs/evidence-plans/AUDIT_FINAL_SCAFFOLD_CONTRACT.json binding seven exact repository commits.
• Adds scripts/verify-audit-final-scaffolds.mjs.
• Adds .github/workflows/audit-final-scaffold-evidence.yml pinned to Ubuntu 24.04, Node 20.11.0, and exact checkout/setup-node action commits.
• Acquires each public source at the exact commit, verifies checkout identity, calculates the audit_final.js SHA-256, executes the unchanged positive script, and performs a disposable missing-README negative case.
• Converts docs/evidence-plans/AUDIT_FINAL_SCAFFOLD_CHECKS.md into an execution record with a strict presence-check-only-not-full-verification ceiling.

Central ledgers and trackers

• Updates docs/KNOWN_LIMITATIONS.md with exact execution, blocker, manual-setting, network, freshness, and merge boundaries.
• Updates Documentation issues phase 4 security floor inventory: exact mixed evidence and blocker states #11 and Post-Phase-4: mixed execution, boundary, and blocker evidence #24 so no listed evidence subject remains generically PLAN_ONLY or inaccurately PATCHED_UNVERIFIED.
• Preserves the distinction between a green blocked-state validator and successful execution of the blocked operation.
• Pins the Documentation verification workflow to Ubuntu 24.04, Node 20.11.0, and exact action commits.

Current GitHub preparation subjects

The handoff records these eight open draft pull requests as bounded source subjects:

• Riverbraid/Riverbraid-Core#7;
• Riverbraid/Riverbraid-Evaluation-Kit#13;
• Riverbraid/Riverbraid-Golds#6;
• Riverbraid/Riverbraid-Documentation#26;
• Riverbraid/.github#5;
• Riverbraid/Riverbraid-Refusal-Gold#7;
• Riverbraid/Riverbraid-Harness-Gold#6;
• Riverbraid/Riverbraid-Gold-V2#3.

All remain draft and unmerged. Any head movement creates a new source subject requiring revalidation.

Source-custody and execution boundary

The exact v0.3 manual, companion-profile, machine-package, successor adoption, and complete checksum bytes are not uploaded, adopted, normalized, or executed by this PR.

Issue #27 records the remaining bounded resolution: rebind the machine package to exact v0.3 bytes, produce one coherent successor or consolidated adoption identity, recompute checksums, rerun the schema/156-fixture/RFC 8785/end-to-end qualification, bind the local execution context, and emit PRE_P0_READY only if supported.

Exact-head validation

Current post-handoff head:

2a227ecea06abeb1d64c7ac5b2adc1db8589743c

Successful exact-head workflows:

1. Audit Final Scaffold Evidence: run 30414122229, job 90456729059.
   • exact Documentation evidence-harness checkout passed;
   • exact seven-repository source acquisition passed;
   • positive scaffold execution passed;
   • disposable missing-README negative cases passed;
   • bounded result-record validation passed.
2. Verify: run 30414122260, job 90456729136.
   • repository checkout passed;
   • pinned Node setup passed;
   • repository verification passed.

The earlier pre-handoff head d41c1a19f707654378648b48fefc29aef6f4bfb7 also passed its recorded workflows, but it is a distinct historical draft subject.

Boundaries

This PR remains draft and unmerged.

It does not mutate registry pins, merge repository repair PRs, change releases or tags, configure repository settings, establish independent reproduction, upload or adopt the F0–F4 control package, issue PRE_P0_READY, execute P0, close F0, or advance F1, F2, F3, or F4.

It establishes only documented crosswalks, exact bounded evidence states, a v0.3 source-custody correction, a frozen GitHub preparation handoff, and one visible pre-P0 identity hold. It does not establish certification, production readiness, external audit, full-constellation operation, F3 integration, universal support, or absence of defects.

[Riverbraid]

Pre-P0 GitHub handoff update

Exact current head:

2a227ecea06abeb1d64c7ac5b2adc1db8589743c

This head now contains:

• v0.3-aligned control-package source-custody record;
• version 2.0.0 GitHub comparison-preparation record;
• human-readable pre-P0 GitHub handoff;
• machine-readable pre-P0 GitHub handoff;
• explicit issue Rebind pre-P0 machine package to v0.3 before founder adoption #27 tracking the v0.3 machine-package rebind hold.

Exact-head workflow evidence:

• Audit Final Scaffold Evidence: run 30414122229, job 90456729059 — success;
• Verify: run 30414122260, job 90456729136 — success.

All eight preparation PRs remain draft and unmerged. This update does not upload or adopt the current control-package bytes, establish PRE_P0_READY, execute P0, close F0, change registry pins, alter releases or tags, configure repository settings, or advance F1–F4.