Promote Svif Project to Agnir Core/profile 1.0

[mattamior]

Explicit Principal-authorized, semantics-preserving Agnir Core/profile 0.2 → 1.0 promotion for the Svif Project.

Normative basis: iorLab/agnir/spec/CORE_0_2_TO_1_0_PROMOTION.md.

Authorization and source:

• Principal explicitly authorized this promotion on 2026-09-07;
• captured authoritative source: a00ad6ed9f18abddbed1979a619f932350cefe54;
• source Core/profile: 0.2 / repository-filesystem/0.2;
• source Project identity: urn:svif:project:svif-core;
• source lineage: urn:svif:lineage:authoritative;
• source selector: refs/heads/main.

Candidate target:

• AGNIR.yaml: Core 1.0, repository-filesystem/1.0;
• Agnir operational provenance: immutable v1.0.0@6d16dcfd17b8e9f22fd25804e22b9f8a516d06c3;
• SVIF.yaml: continuity compatibility/profile 1.0 / repository-filesystem/1.0;
• Svif product line remains 0.2 and Project Binding remains project-binding/0.2.

Required preservation verified during candidate construction:

• Project identity unchanged;
• logical lineage unchanged;
• VCS selector/binding unchanged;
• memory locators unchanged;
• .agnir/state.md, .agnir/next-actions.md, .agnir/decisions.md unchanged in staging;
• brand assets unchanged;
• VERSION unchanged;
• immutable v0.2.0-preview.1 unchanged;
• released Preview.1 first-use bootstrap remains Agnir Core/profile 0.1 and is not retroactively rewritten.

Implementation/conformance:

• Svif Agnir adapter retains historical 0.1/0.2 support and adds stable 1.0 dispatch with the accepted lineage/selector semantics;
• repository binding guard adds 1.0 support;
• 1.0 load/lineage and checkpoint/lineage/VCS tests added;
• current repository self-consumption guards move to v1.0.0;
• full staging run 34076031454 passed source freshness, preservation, repository integrity, full unittest discovery, and portable conformance.

Publication gates:

1. PR synthetic-merge product checks must be green;
2. immediately before merge, authoritative main must still equal/reconcile from the captured source; stale source requires candidate reconstruction;
3. publish the complete promotion coherently;
4. fresh-resolve authoritative main through Core/profile 1.0 and require product checks green;
5. only then checkpoint canonical State / Next Actions / Decisions / Evidence.

This PR is a compatibility-line promotion only. It does not authorize a Svif product-version change, Preview retagging, brand redesign, or first-use distribution-baseline change.

[mattamior]

Final authoritative continuity-repair receipt after the accepted Agnir Core/profile 1.0 promotion:

• promotion merge remains 5da0eb76e38e817ba0f5111ce2b08750afa3b9c3;
• canonical continuity checkpoint 6c2c33da68e88a221ba36289d895f0423d64063a exposed only two documentation-guard regressions: missing previously durable distribution/architecture markers in .agnir/state.md and .agnir/next-actions.md;
• no promotion implementation, tests, AGNIR.yaml, SVIF.yaml, Project identity, lineage, selector, locator, brand, VERSION, or immutable Preview tag changed in the repair;
• minimal fast-forward repair commit: 47ab7615f731c3c647d307c9658bc83df860d0c2;
• repair diff is exactly .agnir/state.md + .agnir/next-actions.md;
• final authoritative main product-check run 34077112740: repository-integrity SUCCESS, runtime-kernel SUCCESS (full unittest discovery), portable-contracts SUCCESS.

This closes the final continuity/documentation guard after the Principal-authorized Svif Project promotion to Agnir Core/profile 1.0 without creating a new CI-receipt commit loop.