Define continuum.debug.hello.v1 runtime hello contract

[flyingrobots]

Source: flyingrobots/warp-ttd#80 and flyingrobots/warp-ttd#93.

Problem:
WARP TTD needs a vendor-neutral runtime hello contract so it can ask any Continuum-compatible runtime what debug protocol and shared families it speaks without branching on app/vendor names. The semantic owner should be Continuum, not WARP TTD.

Desired outcome:
Define continuum.debug.hello.v1 in Continuum as a read-only runtime compatibility declaration. The contract should cover runtime identity, protocol version, supported shared families, debugger-facing capability posture, evidence posture, consent/auth posture, redaction posture, source refs, and obstruction reasons.

Acceptance criteria:

• Continuum owns the schema/registry entry for continuum.debug.hello.v1.
• Generated artifacts can be consumed by WARP TTD, Echo, git-warp, and future vendor runtimes.
• The contract does not issue authority, perform admission, exchange credentials, or mutate host state.
• Native evidence posture and translated-substrate posture are distinct.

Related:

• Vendor-neutral Continuum runtime hello handshake warp-ttd#80
• docs(design): define Continuum runtime hello handshake warp-ttd#93

[coderabbitai]

🔗 Related PRs

#19 - Add cross-repo contract family registry [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!