coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(execution): retain scoped cleanup after uncertain outcomes

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a140c4-354a-7823-8f0d-8f717397f786
This commit is contained in:
codex 2026-10-16 01:51:53 +02:00
parent 3b6e647aa0
commit 59d1441cf8
7 changed files with 462 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/task-execution-plan-compiler.md
View file

@ -94,7 +94,9 @@ cleanup use; this component records limits, it does not enforce native expiry/us
or provide a hard elapsed timer. Trusted owner runtime must bound parser/import/
filesystem/compiler work by remaining action budget before any actual call.
Token custody/revoke, temporary object removal, owner-private recovery after unknown
and truthful native readback remain gates. General lifecycle/apply/exec/default
and truthful native readback remain gates. The 2026-10-16 source cleanup journal
and fixed driver are documented in task-execution-cleanup.md; they preserve unknown
outcomes but are not yet bound into this compiler or a production mediator. General lifecycle/apply/exec/default
migration and SecretsT06/RPF35T02/T12 cannot close from this source component.
Validation:45 compiler tests and 15 journal tests pass, covering real owner K8s/OIDC body generation,