fix(C-373 PR-4): retag v1 to main + release immutability policy

[kaizencycle]

C-373 PR-4: Release Engineering — retag v1 + immutability policy

Handoff: ATLAS HANDOFF C-373 (ledger_id: mobius:epicon:mvp-extraction-c373)

Problem (live defect)

v1 pointed at c0e5e10 (pre-guard-core). Consumers installing @v1 got code that
did not match the README — silent enforcement of old rules.

Solution

1. TAG_POLICY.md — v1.0.0 immutable; floating v1 moves only post-merge on main; movement logged
2. v1.0.0.md — release manifest for first public release matching README + guard-core
3. v1.md movement log — records retag from c0e5e10 → merge SHA
4. MVP_SPEC_AMENDMENTS.md — packages/guard-core/ accepted over packages/validator/

Post-merge: v1.0.0 and v1 tags pushed to merge commit; GitHub Release created.

Tests

• node test/classify.test.mjs — 11/11
• node test/policy-ref.test.mjs — 9/9

Intent

epicon_id: EPICON_C-373_CI_release-retag-v1_v1
ledger_id: mobius:epicon:mvp-extraction-c373
scope: ci
mode: normal
issued_at: 2026-07-15T00:00:00Z
expires_at: 2026-08-15T00:00:00Z
justification:
  VALUES INVOKED: integrity, transparency, reliability
  REASONING: Floating v1 tag was 15+ commits behind main — silent install of
    pre-guard-core code. Retag aligns Quick Start with shipped validator.
  ANCHORS:
    - docs/releases/TAG_POLICY.md
    - C-373 witness table (v1 drift verdict)
  BOUNDARIES: Tags + release docs only; no validator logic changes
  COUNTERFACTUAL: If federation Guard runs regress after retag, restore v1 to prior SHA and halt
counterfactuals:
  - If external installs fail after retag, revert tag movement immediately
  - If tests fail, do not push tags

  

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.