luigidemasi commented on issue #83: URL: https://github.com/apache/camel-kit/issues/83#issuecomment-6336908005
> Comment by [luigidemasi](https://github.com/luigidemasi) on 2026-08-26 ([original](https://github.com/luigidemasi/camel-kit/issues/182#issuecomment-5428504964)). --- ## Completion summary Issue luigidemasi/camel-kit#182 is complete. The six planned product-boundary clusters were delivered through: - luigidemasi/camel-kit#183 — remove the main-package evidence command; - luigidemasi/camel-kit#184 — run VALIDATE evidence directly without the attestation stack; - luigidemasi/camel-kit#185 — remove duplicate Maven Central downloads; - luigidemasi/camel-kit#186 — simplify catalog reads and evidence-set validation; - luigidemasi/camel-kit#190 — simplify worker recovery and redaction boundaries; - luigidemasi/camel-kit#191 — simplify security/controller boundaries and relocate the publication registry. luigidemasi/camel-kit#187 restored keep-going coverage, luigidemasi/camel-kit#189 landed the reviewed stacked clusters, and luigidemasi/camel-kit#192 corrected the canonical PLAN route-path contract exposed by the authenticated certification and invalidated legacy PLAN results after that semantic change. Final verification: - `main` contains luigidemasi/camel-kit#192 as merge commit `279e8ffd`; - post-merge [run 32968899413](https://github.com/luigidemasi/camel-kit/actions/runs/32968899413) passed formatting, the full build/tests, and Ship certification on Java 17, 21, and 25; - the authenticated Pi/Linux profile and a separately registered `camel-kit ship` invocation completed successfully before merge, as recorded in luigidemasi/camel-kit#192; - website impact is **required and fulfilled** by [camel-kit-web PR luigidemasi/camel-kit#30](https://github.com/luigidemasi/camel-kit-web/pull/30); its [production build and deployment](https://github.com/luigidemasi/camel-kit-web/actions/runs/32730890032) passed and the updated documentation is live. Closing as completed. -- 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]
