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

   > Comment by [luigidemasi](https://github.com/luigidemasi) on 2026-08-18 
([original](https://github.com/luigidemasi/camel-kit/issues/149#issuecomment-5326884362)).
   
   ---
   
   Acceptance state reconciled after PRs 
luigidemasi/camel-kit#171–luigidemasi/camel-kit#174.
   
   The registered controller now covers explicit context input, lifecycle and 
process-interruption recovery, oversight,
   contextual resume, deterministic verification and evidence, guarded 
publication, truthful status output, user
   configuration, and both public command surfaces. The issue body now marks 20 
of 24 acceptance criteria complete.
   
   The remaining closure work is:
   
   - replace the prompt-owned `camel-ship` workflow and 
`.camel-kit/pipeline.json` state machine with thin delegates to
     the registered CLI;
   - complete one authenticated, non-skipped Pi/Linux workflow through 
`camel-kit ship` or `camel kit ship` — the
     existing real-Pi fixture exercises the coordinator directly, while the 
registered entry point is not yet certified;
   - update repository and migration documentation plus the website, then 
verify the production website build.
   
   The wording was also aligned with the delivered contract:
   
   - interruption safety means ordinary process interruption, not a blanket 
OS/power-loss durability guarantee;
   - supplied context is delivered before Discovery questions and the worker is 
instructed to group only unresolved
     questions, rather than promising that a language model can never repeat 
one;
   - cancellation may finish explicitly `ABORTED`, not only `FAILED`;
   - public Stamp outcomes are `pass` or `fail`; this issue exposes no 
waiver-authority flow;
   - Pi and Node failures provide installation guidance, while Ship resolves 
its Camel validation payloads without a
     separately installed Camel CLI.
   
   Website impact remains **required**. The current site still describes 
`/camel-ship` as the workflow owner, so luigidemasi/camel-kit#149
   stays open until the thin-delegate cutover, registered-CLI live gate, and 
documentation work are complete.
   


-- 
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