Merge Sim ba6523a905 docs(orchestration): stop two structured-worker comments claiming guarantees the code does not give ...

The send-time owner re-check reads `target.refusal`, the snapshot the resolver
already admitted, so `decideStructuredPointerDelivery` can only agree with the
resolve-time answer and `owner-not-settled-native` is unreachable from that call
site. What actually fences an owner that moved is `expectedRuntimeFence`, which a
handoff bumps. Say that, so nobody later drops the fence trusting a re-check that
is structurally a tautology.

`discardCreatedSession` was credited with retiring "a published background tab
that no dispatch owns". It hides the DURABLE tab reference and closes the
session; the live tab snapshot keeps the row, so the background tab this start
published stays on screen until the app restarts. Same for stop and release. The
comment now describes what the two calls do — including that both are no-ops on a
session that was never attached, which is what makes the non-definitive-refusal
path safe to reach unconditionally.

2026-09-05 05:46:28 -07:00

..

cli

feat(orchestration): orchestrate native-born structured chat sessions

2026-09-05 04:38:22 -07:00

main

docs(orchestration): stop two structured-worker comments claiming guarantees the code does not give

2026-09-05 05:46:28 -07:00

preload

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

relay

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

renderer

fix(orchestration): answer the structured idle gate from the reduced timeline

2026-09-05 04:58:37 -07:00

shared

fix(renderer): stop a Node-only process-table module blanking the app at boot (#18814)

2026-09-05 02:07:37 -07:00

types

…