Preserve typed request thread in resident launch

This commit is contained in:
Meta Vens 2026-08-08 01:19:07 +01:00
commit 8a9439ca2e
6 changed files with 182 additions and 39 deletions

View file

@ -1257,6 +1257,15 @@ failed turn and schedules the replacement within the same physiological action.
Concurrent issuers still derive the same next ordinal and contend on the one
pending-pressure CAS, so attempt identity does not weaken single consumption.
Typed pressure does not own a new coordinator thread. Imagination
consideration, admitted-model direction consideration, and autonomous proposal
Modeling requests each carry the implementation thread that owns their causal
state. Resident preparation reloads that exact request from the runtime store,
verifies its runtime identity, and binds its thread into the coordinator argv.
The prepared argv is then the single source for child launch and lease thread
identity. Only plain operator objectives use the resident runtime thread.
`epiphany-swarm` no longer reconstructs a fixed thread after preparation.
## Exact release build cache ownership
Release construction has two serialized cache authorities. The graph cache is

View file

@ -59,10 +59,28 @@ The retry test now uses the same heartbeat schedule/action and proves attempt 2
receives a distinct grant while retaining the same pressure authority. All 16
resident-Self tests pass.
Exact pushed `d4b446ab` packages as
`sha256-d31ab4329dd34d93e101fa3a783373b6b1f3bc311fac057c6f0d0b4ce5911122`
with witness
`sha256-d5256ee2181dcacc3da87c8f491a12c359a0bde6139a362d40053d453acac4b8`.
The v34 live timeline proved the deliberate failure, cancellation, attempt-2
grant, and replacement launch. Running the replacement under persistent
`epiphany-swarm serve` reached coordinator validation, which correctly refused
`model direction consideration provenance mismatch`: resident preparation had
substituted fixed thread `resident-self-thread-epiphany-starfire` for the
implementation thread owned by the typed direction request.
The current worktree reloads typed direction, Imagination-consideration, and
proposal-Modeling requests during preparation and carries their exact runtime
and thread identity through argv, child launch, and lease. Plain operator
pressure alone retains the fixed resident thread. All 16 resident-Self tests and
both packaged swarm tests pass; typed launch tests assert the request-owned
thread.
## Next action
1. Commit, push, package, and authenticate attempt-qualified retry grants.
2. Preserve v31 through v33 as failure evidence; clone the recovered boundary
1. Commit, push, package, and authenticate request-owned resident threads.
2. Preserve v31 through v34 as failure evidence; clone the recovered boundary
into a new replay runtime using an approved `.epiphany-dogfood` artifact root.
3. Re-run heartbeat selection and resident launch, including exact retry after
one deliberate failed launch.