Use an explicit chat_create operation_id as the durable bootstrap key while retaining envelope IDs for reply correlation. Legacy requests receive fresh server-scoped identities, so independent cli-1/android-1 requests do not collide; clients that retry retain one operation_id. Update Android creation state and repository calls to preserve an operation identity across retries, and cover durable reconnect retries, duplicate barriers, changed input, legacy correlation reuse, and protocol serialization. Checked packaged templates: none describe chat_create. Checked packaged authoring-skill references: the existing description is stale, but shared references and README must not be edited by an item; docs/notes/bootstrap-create-identity.md records the required docs-fold update and rollout compatibility.
1.0 KiB
Chat-create operation identity
chat_create now carries chat_create.operation_id as its durable create-intent
key. The envelope id remains only response correlation and may restart at
cli-1 or android-1 in a fresh process. Clients that need exactly-once retry
after reconnect or a lost response must retain and resend operation_id; legacy
clients receive a server-generated per-request scope and therefore have no
cross-reconnect retry guarantee.
docs/cli.md and the packaged OpenCode skill references that describe
chat_create are stale: they should document this additive field, the legacy
compatibility behavior, and rollout requirement that retry-capable clients send a
stable operation identity.
Compatibility rollout: deploy the additive server support before a client that
sends operation_id; old clients remain able to create chats but cannot safely
retry across reconnects. Once clients send a stable key per create intent, they
must keep that key for every retry and allocate a new key for each new chat.