ADRs: publish on release tags, Pause and Rollback, and isolate a refused Project #196

Parent

#195

What to build

The three delivery decisions as decision records, each with the spec text it justifies, in one small PR:

• A fragment publishes on a release tag and carries its version. release-please tags a release; the tag publishes the fragment; a merge that is not released does not deploy. Rewrites 0051's amendment of 0042 in chapter 40.
• Pause and Rollback.
  • A pause freezes a Project's pin, recorded as annotations on its pin file.
  • A Rollback re-composes an earlier release, named by version, with the schema at its newest.
  • Only a release proven against the current schema, the one the Migration Proof's testedAgainst names, is offered.
  • A Rollback first takes a backup of the data the Project reaches, kept 7 days, and moves the pin only once that backup succeeds.
  • It leaves its Project paused.
  • This goes in chapter 55.
• Composition isolates a refused Project. Its Project stays at its last composed fragment while every other Project still composes. This replaces chapter 40's "every collision fails the run".

CONTEXT.md's Rollback and Pause entries, already drafted in the working tree, land here.

Acceptance criteria

• Three ADRs, each numbered from the next free estate-wide number (check both registers), with an Alternatives table, a register row and a normative: anchor that resolves.
• Chapters 40 and 55 state what the ADRs decide.
• npm run verify passes, ADR, link and meaning lints included.

Blocked by

None (can start immediately).