Guard source compatibility and qualified binding projections

[iperev]

Summary

• Add permanent cross-owner tests for all 30 canonical legacy field coordinates, lifecycle/deferral variants and independent update-policy flags, using the real private codec and complete reconstructed public-source values.
• Protect public v1 identity/path admission and qualified requirement/scenario/witness payloads, including known-but-wrong source paths and duplicate tuples.
• Retain explicit public/private resource-domain counterexamples without raising limits or narrowing current admission.
• Clarify the boundary in ADOPTION and prepare the compatible 0.14.18 change record. No production code, CLI-contract bytes, dependencies or supported-platform claims change.

Validation

The full npm run check passed on final commit
e2ae1fbdcf50b59b3cdc9f4feae7e521ba57a30b, including 333 browser cases,
package verification and self-hosting checks. Three fresh final reviews were
independently admitted without findings in their assigned scope. Earlier local
test gaps were reproduced and fixed. Narrow checks passed, including the
explicit small race subset and exact CLI-contract/release checks. Large resource
fixtures remain in the ordinary mandatory Go suite; earlier broad race attempts
timed out and are not claimed as passed. Nine isolated mutation controls detect
the selected faults; three of those were first reproduced as surviving the old
fixtures, then detected after repair. This is not exhaustive mutation testing.

Plan Boundaries

The external field disposition covers 30 legacy and 74 candidate fields without
turning newly introduced private semantics into legacy data. Common-domain
field correspondence is distinct from entire-language inclusion. P9-02 still
depends on the selected public identity/path and scenario-body cutover design;
P9-05 still requires the remaining eligible-candidate safety qualification.
No source-format winner, human study, nested public schema or source cutover is
claimed. Design and implementation-plan documents are not part of this PR.

Non-Claims

Declaration routes do not prove native execution, test adequacy, currentness,
producer authentication, merge approval, registry publication, deployment,
rollout or production readiness. Provider and release evidence must be checked
separately on the final source.