luigidemasi commented on issue #79:
URL: https://github.com/apache/camel-kit/issues/79#issuecomment-6336893757

   > Comment by [luigidemasi](https://github.com/luigidemasi) on 2026-07-25 
([original](https://github.com/luigidemasi/camel-kit/issues/149#issuecomment-5077559994)).
   
   ---
   
   PR luigidemasi/camel-kit#166 is open for the bounded Pi/Linux worker and 
local-evidence substrate.
   
   The implementation uses one bounded Pi RPC process per prompt. A one-shot 
process terminated before the first assistant response did not leave resumable 
context, while RPC produced an abortable turn and the `agent_settled` lifecycle 
event needed for exact transcript validation. The maintained baseline therefore 
moves to Pi 0.80.6; it remains `experimental` until the real end-to-end gate 
passes.
   
   This slice adds controller-owned attempt staging, bounded local command 
execution, copy-on-write Pi sessions, cancellation/timeout recovery, strict 
local Stamp persistence, and atomic validated-session publication. It remains 
internal and does not register `camel-kit ship`.
   
   The Delivery checkbox for the Pi/Linux worker path stays open: this is not 
yet the real no-context/document-driven end-to-end fixture. Atomic session 
publication is also not exactly-once composition with the `ShipRun` transition. 
The next slice needs a durable result marker keyed by run, stage, input digest, 
and attempt, a changed-workspace secret scan, deterministic 
validator/build/Citrus composition, and the live resume/interruption gates.
   
   The worker's working directory is not an OS sandbox; hostile same-user 
containment remains outside the issue boundary.
   
   Website impact: **required**, tracked by the existing repository/website 
documentation checkbox for public cutover.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to