Decide native vs translated continuum.debug.hello.v1 posture

[flyingrobots]

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

Problem:
WARP TTD can treat git-warp/graft as a translated-substrate witness today, but native Continuum runtime hello support should be an explicit git-warp decision. Without that decision, WARP TTD must keep nativeContinuumWitness: false for translated facts.

Desired outcome:
Decide whether git-warp will publish native continuum.debug.hello.v1 runtime hello facts, or remain represented through WARP TTD translated-substrate wrapping for now.

Acceptance criteria:

• If git-warp implements native hello, it consumes the Continuum-owned schema and reports native evidence only through the producer contract.
• If native hello is deferred, WARP TTD docs/tests continue to mark translated git-warp/graft facts as nativeContinuumWitness: false.
• No app/vendor-name branching is required in WARP TTD to inspect git-warp compatibility posture.

Related:

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

[flyingrobots]

Backlog triage: labeling this as a later-priority architecture/protocol question.

Reasoning: the issue asks for a native-vs-translated Continuum posture decision for continuum.debug.hello.v1. It is not a v18.0.0 release blocker and should not sit unlabeled in the live tracker.