Add embodied succession and publication recovery contract

[BigBirdReturns]

Object

The live Organ Evolution census identified two distinct facts on axm-embodied main: the repository lacks a root succession record, and its latest observed Pages publication receipt is red. This PR first closes the succession defect without mixing it with post-v1 action custody.

Continuity contract

CONTINUITY.md classifies axm-embodied as the physical-evidence organ and records:

• what the organ owns;
• what it is forbidden to decide;
• the exact Genesis-pinned CI and drift boundary;
• the distinction between evidence custody and Pages publication;
• the post-v1 donor and physical-acceptance hold;
• recovery commands;
• a maintainer transfer checklist;
• the requirement that physical observations remain evidence rather than accepted outcomes.

The document explicitly preserves Arc replay required for provisional Unity or Quest candidates and refuses to treat donor source as current-main capability merely because it exists.

Pages observation

The existing Pages workflow is unchanged in this first repair. Merging a root documentation file will trigger a fresh current run. If that exact run fails, the resulting current receipt becomes the demonstrated boundary for a separate Pages repair. The previous red publication receipt is not hidden or relabeled as an evidence-custody failure.

Boundary

This PR does not merge action-session, spool, strict-JSON, journal, or Quest-return donors into main. It does not change the Genesis pin, evidence schema, package, tests, or authority law.

Control question

Can a successor preserve and verify the physical record, explain its limits, and continue the organ without acquiring authority over the meaning or outcome of what was observed?