Spec: notifications, the runner contract, the Estate repository and the naming rules #206

Parent

#195

What to build

The spec text the delivery path cites that needs no new decision record, in one small PR:

• Chapter 55, notifications. A commit status on the publishing commit, one Estate-repository issue per Project condition, and Discord.
• Chapter 55, the runner contract.
  • Verbs up <tag> and down <tag>, the tag being the revision's first 12 hex digits.
  • Fixed variables: database host and port, database name, Secret Store address, Vault role, and the owner credential path database/creds/<project>-owner.
• Chapter 60. The Estate repository, the dispatch and Collector GitHub Apps, and handover with home-portal first.
• Chapter 16. A project's database is <project>_db; Vault role and policy are named <namespace>-<identity>; backup pods get their own NetworkPolicy.
• CONTEXT.md. The Collector, Estate repository, Backup Identity, Backup Claim and Migration Proof entries, already drafted in the working tree.

Acceptance criteria

• Chapters 16, 55 and 60 and CONTEXT.md say the above.
• npm run verify passes.

Blocked by

None (can start immediately).