GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Delegate bridge interruption

Browse source
This commit is contained in:
Meta Vens 2026-07-12 00:52:19 +01:00
commit a682f7acd7
6 changed files with 46 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

7
notes/fresh-workspace-handoff.md
View file

@ -1882,8 +1882,11 @@ historical-input fixture. Native `--interrupt-binding` is now live:
`interrupt_coordinator_job` owns revision/binding validation and canonical
binding mutation, while status reports `cancelRequested=false` honestly. A
focused core test and status-command test prove the transition. Explicit
`--codex` retains compatibility. The bridge still duplicates interruption
choreography; delegate it to `EpiphanyCoordinatorService::interrupt_job` next.
`--codex` retains compatibility. The bridge now delegates interruption to
`EpiphanyCoordinatorService::interrupt_job`; nine bridge tests prove no local
binding mutation policy remains, and the vendored app-server compiles. General
update/promotion persistence still uses the host hook and is the next surviving
state-authority seam.
## Immediate Re-entry Instruction

7
notes/native-coordinator-liberation-map.md
View file

@ -269,5 +269,8 @@ Interruption now has a native owner. `interrupt_coordinator_job` validates the
binding and revision, records the operator reason through the canonical state
owner, and reports `cancelRequested=false` rather than inventing backend
cancellation. `epiphany-mvp-status --interrupt-binding` uses this path by
default; `--codex` selects the compatibility route explicitly. The bridge still
contains its older interruption choreography and should delegate next.
default; `--codex` selects the compatibility route explicitly. The bridge now
delegates interruption to `EpiphanyCoordinatorService::interrupt_job`; a source
guard rejects local binding mutation, and stale unified state is refused before
commit. General update/promotion routes still persist through the host hook and
are the next surviving state-authority seam.