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

   > Comment by [luigidemasi](https://github.com/luigidemasi) on 2026-08-19 
([original](https://github.com/luigidemasi/camel-kit/issues/149#issuecomment-5342615699)).
   
   ---
   
   Closing: the last acceptance criterion completed on 2026-08-19.
   
   **Authenticated Pi/Linux run through the registered entry point** — a 
document-driven workflow with oversight `never`, started, resumed, and aborted 
only through the registered `camel-kit ship` command at the merged 
thin-delegate main:
   
   - **Configuration:** Pi `0.83.0` and Node `22.22.2` — the maintained pins, 
both recorded `supported` in the Stamp — with the Bubblewrap sandbox on a 
merged-/usr Linux host (amd64, Java 21, Camel 4.21.0 recorded for diagnostics). 
The Pi executable was version-pinned deliberately: the globally installed Pi 
had self-updated to 0.84.2 the same day, so the run used a separately installed 
0.83.0, and the Stamp records that exact executable path and version.
   - **Stages:** all five completed. Execute needed two attempts — the first 
returned a prose-wrapped result, and the controller rejected it as an invalid 
typed stage result instead of committing it; the resumed attempt completed. The 
worker model was `nvidia/nemotron-3.5-lightning:free` via OpenRouter through 
the Pi harness; provider credentials stayed with the harness throughout, per 
the product boundary.
   - **Stamp:** `pass`, with all six mandatory checks passing — artifact 
policy, catalog usage, route schema, package-and-inspect, runtime 
resolve-and-start, and one discovered and executed Citrus test — each with 
retained, digest-bound command evidence.
   - **Publication:** the route, Citrus test, `.camel-kit/config.properties`, 
`pom.xml`, and artifact manifest were published to the project only after 
validation, through the guarded publication path.
   
   An earlier run the same day failed closed at discovery when the first 
free-tier model endpoint returned repeated upstream 429 errors; it was 
explicitly aborted and retained as evidence of the failure path — the 
controller never committed a stage on degraded worker output.
   
   Website: the Ship cutover merged earlier as camel-kit-web#28; the live-gate 
status sentence is updated in camel-kit-web#29.
   
   All acceptance and delivery checklist items are now 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