Add cross-repo contract family registry

[flyingrobots]

Summary

Adds the first Continuum-owned cross-repo contract family registry.

This PR:

• adds docs/contract-family-registry.md
• adds design packet 0029-cross-repo-contract-family-registry
• records the old registry backlog item as packet origin
• links the registry from README.md and schemas/README.md
• narrows the remaining compatibility-matrix backlog item to witness/evidence cuts

Why

The sibling-runtime doctrine is now explicit, but the repo still needed one practical map for shared contract families: authored home, shared nouns, Wesley status, runtime status, consumers, evidence, and open cuts.

The registry keeps Continuum as coordination truth. It does not add runtime code, schema code, or a new compiler surface.

Validation

• npx --yes markdownlint-cli -- README.md schemas/README.md docs/contract-family-registry.md docs/design/0029-cross-repo-contract-family-registry/README.md docs/design/0029-cross-repo-contract-family-registry/backlog-origin.md docs/method/backlog/asap/EVIDENCE_continuum-compatibility-matrix-and-witness-cuts.md
• git diff --cached --check
• git diff --check HEAD~1..HEAD

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 45154318-d3c7-4740-b2f5-98fc88657254

📥 Commits

Reviewing files that changed from the base of the PR and between 3527ca3 and 3f9a00f.

📒 Files selected for processing (7)

• README.md
• docs/contract-family-registry.md
• docs/design/0029-cross-repo-contract-family-registry/README.md
• docs/design/0029-cross-repo-contract-family-registry/backlog-origin.md
• docs/method/backlog/asap/EVIDENCE_continuum-compatibility-matrix-and-witness-cuts.md
• docs/method/backlog/up-next/SOURCE_cross-repo-contract-family-registry.md
• schemas/README.md

💤 Files with no reviewable changes (1)

• docs/method/backlog/up-next/SOURCE_cross-repo-contract-family-registry.md

---

Summary by CodeRabbit

• Documentation
  • Added comprehensive Contract Family Registry documenting shared contract families, versions, consumers, and compatibility status.
  • Introduced design specifications for cross-repository registry coordination and evidence tracking rules.
  • Updated documentation references to guide users to registry resources.

Walkthrough

This PR establishes a new "Contract Family Registry" documentation system to coordinate shared GraphQL contract families across Continuum, Wesley, Echo, git-warp, and warp-ttd. It introduces the registry at docs/contract-family-registry.md, supporting design and origin documents, and updates existing documentation to reference this new coordination artifact.

Changes

Contract Family Registry Introduction

Layer / File(s)	Summary
Design & Rationale docs/design/0029-cross-repo-contract-family-registry/README.md, docs/design/0029-cross-repo-contract-family-registry/backlog-origin.md	Design cycle 0029 establishes the registry's purpose: making shared contract-family authorship, shared nouns, witness posture, and sibling runtime compatibility evidence visible across the stack. Registry rules separate authored meaning from runtime truth and require evidence for runtime status claims.
Registry Definition docs/contract-family-registry.md	The registry itself, defining role separation, status vocabulary, family matrix entries for receipt-family, settlement-family, neighborhood-core-family, and runtime-boundary-family, a runtime-boundary noun matrix, a repo role matrix, compatibility claims with evidence requirements, and maintenance rules.
Integration & Cross-References README.md, schemas/README.md	Entry points updated to direct users to the registry documentation for cross-repo ownership, consumer, and witness posture information.
Backlog & Methodology Updates docs/method/backlog/asap/EVIDENCE_continuum-compatibility-matrix-and-witness-cuts.md	Backlog item reframed to target turning registry open cuts into witnessed evidence with explicit Wesley profiling and fixture witness requirements for runtime-boundary-family. docs/method/backlog/up-next/SOURCE_cross-repo-contract-family-registry.md

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Poem

📋 A registry born in markdown's grace,
Maps families across the codebase space—
Authorship, roles, and witness cuts made plain,
No more shadows, no more pain.
Continuum speaks, the stack listens well! 🎯

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the primary change: adding a cross-repo contract family registry as documented in the changeset.
Description check	✅ Passed	The description is well-structured, directly related to the changeset, and thoroughly explains the motivation, scope, and validation approach for the registry addition.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/cross-repo-contract-registry

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}