fix(registry): harden ecosystem projection semantics

[ndrorchestration]

Controller: #694.

This lane hardens the ecosystem registry as an evidence-bounded, curated projection. It is intentionally isolated from protected main; do not merge before #679's retained-byte checkpoint is satisfied.

Implemented on current head 78bf6fb30683adadbbae6e6c80c6dfe588a754b5:

• semantic validator for projection provenance/status, current persona-authority leakage, unscoped governance/compliance/production claims, deployment evidence binding, and observable GitHub metadata drift;
• private-repository absence is NOT_OBSERVABLE, not negative evidence;
• registry v0.5 reconciliation with explicit current/historical boundaries and corrected observable visibility metadata;
• Vercel project identity is separated from runtime-currentness claims;
• PR-triggered ecosystem audit coverage;
• historical-boundary notice for the S067 lifecycle artifact and repos/ propagation mirrors;
• regression tests include the checked-in registry itself, preventing fixture-only green results while the projection drifts.

TDD evidence:

• RED head 67092c234fd97a7969b8a5121abadcb224180258: Python quality reached pytest with exactly the intended new failures: 2 failed / 897 passed / 4 skipped; static/type/lint checks were green.
• GREEN/verification head: 78bf6fb30683adadbbae6e6c80c6dfe588a754b5.

Exact-head verification on 78bf6fb...: terminal green across the full returned PR workflow surface. This includes Ecosystem Registry Audit, Python Tests & Quality Checks (3.10/3.11/3.12, security, staging, downstream integration), Claim Hygiene, Doc Lint, PR-scoped Doc Lint, IP Hygiene, DGAF Regression, Truth Layer Validation/Tests, Epistemic Evidence, PDMAL Harness, PPTL CI, Control-State HEAD Binding, Control-State Consistency, Critical PR Lane Custody, Full Repository Coverage, PR Issue-State Keyword Guard, Governance CI, PDMAL Pre-Freeze Runner Validation, and Vercel SUCCESS.

Classification: VERIFIED implementation readiness / HOLD. The verification closes the #694 implementation lane technically, but does not satisfy the separate #679 operator-local retained-byte checkpoint and does not authorize moving main.

Non-effects:

• no Track A retained bytes are created or admitted;
• no dataset lock, unblinding, primary-analysis authority, efficacy claim, High-Assurance state, or scientific N is changed;
• protected main remains 1fb2c665587d5a0e7b213aef1cc5c870097cdc9b; Track A Epoch 002: admit externally executed collection into dataset-lock evidence chain #679 remains the controlling human/private-byte boundary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dynamicgovernanceagenticformation	Ready	Preview	Sep 15, 2026 11:05am UTC

[ndrorchestration]

Exact-head verification closure — HOLD preserved

Fresh verification of PR #695 head 78bf6fb30683adadbbae6e6c80c6dfe588a754b5 confirms the full returned PR workflow surface is terminal green. Governance CI run 34961332219 and PDMAL Pre-Freeze Runner Validation run 34961332012, previously still running, both completed successfully. The already-recorded ecosystem audit, Python quality/security/integration matrix, claim/doc/IP hygiene, regression, truth/evidence, custody, control-state, PPTL, PDMAL harness, and HEAD-binding checks remain successful on this exact head.

Classification: VERIFIED implementation readiness / HOLD. This does not satisfy the separate #679 retained-byte checkpoint and does not authorize merging #695 or moving protected main.

Protected main remains 1fb2c665587d5a0e7b213aef1cc5c870097cdc9b. No dataset-lock, unblinding, primary-analysis, efficacy, High-Assurance, or scientific-N transition is implied.

[ndrorchestration]

Superseded as an active implementation lane by merged #737 on protected main (972f71cf52ee7a1a7dc636eb00ed8c268496af57). The only unique still-useful delta identified after reconciliation was the historical-boundary/Markdown-hygiene patch to docs/lifecycle_harness_v2.md; that exact narrow change has been preserved on fresh current-main lineage in #738. No scientific, authorization, efficacy, High-Assurance, or scientific-N state is changed by this disposition. Historical #695 commits remain available for provenance; do not merge this stale divergent branch.