luigidemasi opened a new issue, #100: URL: https://github.com/apache/camel-kit/issues/100
> Imported from [luigidemasi/camel-kit#229](https://github.com/luigidemasi/camel-kit/issues/229), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-09-09. --- Parent tracker: https://github.com/luigidemasi/camel-kit/issues/221 ## Description Preserve Pi's existing Camel Ship execution path while the shared controller gains native subagent integrations for other agents. This is a compatibility task: Pi should not be migrated to a new subagent model or require an additional extension. ## Acceptance criteria - [ ] Keep the current Pi/Node worker launch, prerequisites, supported-version handling, and registered standalone/JBang-plugin behavior. - [ ] Preserve the Pi-native skill entry point and generated/reinitialized project behavior. - [ ] Keep existing Pi run records, session/result markers, and execution provenance readable and resumable after the shared-contract changes. - [ ] Verify normal completion, oversight pauses, resume, timeout, abort, and recovery from partial/interrupted attempts. - [ ] Confirm that native-mode selection for other agents does not change or accidentally select a different backend for existing Pi runs. - [ ] Preserve controller-owned validation, artifact/workspace restrictions, and publication checks. - [ ] Run focused compatibility regressions and the existing real Pi certification path through a registered entry point, alongside the required wrapper/source checks. The shared controller work in the parent is the dependency. No new Pi subagent extension, extra execution mode, runtime expansion, or forced migration is part of this task. **Website impact: not required** for this compatibility-only task because the intended Pi behavior remains unchanged. The parent's website follow-up will describe Pi as the retained execution path alongside the newly supported native integrations. -- 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]
