docs(hermes): define native transport contract

[galligan]

Context

The first Hermes adapter needs a precise transport boundary before implementation. The contract must preserve local delivery authority, prevent unsafe resubmission, and distinguish native continuity evidence from assumptions about Desktop or HTTP execution.

What changed

• Selects a Dispatch-owned native TUI gateway child over stdio on the authorized default profile, with dedicated sessions and per-session working directories.
• Requires local reservations and generation quarantine; a changed gateway generation cannot automatically resume an earlier stored session because ordinary resume may auto-continue.
• Keeps ambiguous requests unresolved and non-retransmittable.
• Documents HTTP Runs for explicitly API-managed automation and keeps it outside the adapter fallback path.
• Records the failed warm Desktop/API continuity probe as an unresolved boundary for a separate proof.

Verification

• just check passed Ruff, formatting, strict mypy, 1,345 tests with 17 live tests deselected, wheel and sdist builds, and package-content validation at the current stack tip.
• Hermes's isolated auto-continue suite passed 20 tests in 2.9 seconds.
• Targeted review report dis-84-research-r4.json is schema-valid and clean at 5/5 with zero P0–P2 findings.
• Markdown links and fences across the five changed files and git diff --check passed.
• Final exact-head composed-stack review at 7e5d6ba is clean at 5/5 with zero P0–P3 findings; adversarial supervisor coverage exercised all 27 immediate and 12 delayed recovery/closure outcome combinations.
• Hosted current-head check and Bootstrap smoke (macOS) are successful.

Risks and boundaries

No adapter implementation, merge, release, deployment, installed-runtime replacement, or installed registry migration is included. The stack remains ready for review and unmerged.

Closes: DIS-84

[linear-code]

DIS-84

[galligan]

• feat(hermes): add operator diagnostics and package proof #122
• fix(hermes): quarantine replaced session generations #121
• feat(hermes): add correlated local adapter #120
• feat(daemon): isolate provider startup recovery #119
• feat(providers): persist correlated receipt observations #118
• feat(delivery): freeze provider requests before submission #117
• docs(hermes): define native turn correlation contract #116
• feat(providers): guard binding-qualified routing #115
• docs(hermes): define native transport contract #114 👈 (View in Graphite)
• feat(registry): scope identity by provider binding #113
• fix(protocol): validate schema at daemon execution #112
• docs(providers): define shared provider identity contract #111
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Low Risk
Documentation-only changes with no runtime, migration, or adapter code; they constrain future Hermes integration design rather than altering production behavior.

Overview
This PR records DIS-84 native Hermes transport research as documentation only: it picks the Dispatch-owned TUI gateway over stdio for the first coding adapter (dedicated sessions, per-session cwd) and adds two research contracts plus updates to the execution plan, retro ledger, and ADR-0028.

hermes-native-provider-contract.md defines launch/profile env, session vs stored keys, prompt/event receipt rules, and hard limits: no native idempotency on stdio, unknown outcomes must not retransmit, and automatic resume across gateway generation changes stays off until Hermes offers a safe non-executing recovery path (lazy watch is diagnostic only).

hermes-http-runs-contract.md captures the HTTP Runs probe (keyed replay, polling, etc.) for API-managed automation but explicitly excludes HTTP as adapter fallback because Runs cannot honor session cwd and warm Desktop → API → Desktop context failed live.

PLAN.md, RETRO.md, and ADR-0028 are aligned: DIS-84 is renamed to transport proof, foundation work points at the verified contract, process ownership is long-lived stdio child (not detaching from an external Hermes API client), and successful probes still do not bypass DIS-81/82/85+ implementation gates.

^{Reviewed by Cursor Bugbot for commit 4fd0b96. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_7d3b45d5-3bf6-4a39-b71e-273b84e1dc4f)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-13T22:06:28.643337Z	0e8fdc6	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3c142755-7cb5-4657-bb62-d1ff66214461)

[galligan]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 3f78f189a6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[galligan]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 422423ae1c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_222dd483-94fa-43b7-9c17-345d836eb472)

[galligan]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 0e8fdc607a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[galligan]

Merge activity

• Sep 13, 11:23 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Sep 13, 11:30 PM UTC: Graphite rebased this pull request as part of a merge.
• Sep 13, 11:30 PM UTC: @galligan merged this pull request with Graphite.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_c4c94be6-390a-4322-9954-402b04501d69)