Publish native continuum.debug.hello.v1 runtime hello

[flyingrobots]

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

Problem:
Echo is the intended first native Continuum runtime witness for WARP TTD, but it does not yet publish a native continuum.debug.hello.v1 producer. WARP TTD should not infer native Continuum witnesshood from app names, roots, or adapter-local facts.

Desired outcome:
Echo publishes a read-only runtime hello payload using the Continuum-owned continuum.debug.hello.v1 contract once that schema exists.

Acceptance criteria:

• Echo reports runtime identity and supported Continuum family posture through the shared hello contract.
• Native Continuum evidence is only claimed through the runtime-side producer contract.
• Missing/unpublished facts remain explicit absence or obstruction posture.
• No authority, admission, credential exchange, or host mutation occurs through hello.

Related:

• flyingrobots/continuum issue for continuum.debug.hello.v1 schema.
• Vendor-neutral Continuum runtime hello handshake warp-ttd#80
• docs(design): define Continuum runtime hello handshake warp-ttd#93

[coderabbitai]

🔗 Related PRs

#323 - Witnessed suffix admission evaluator [merged]
#326 - Echo contract hosting roadmap [merged]
#344 - feat(wesley): consume canonical requirements artifacts [merged]
#365 - feat(wesley): emit query observer host helpers [merged]
#529 - Add Hello Echo demo and docs lifecycle policy [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!