Jinal-Sarvaiya commented on PR #150:
URL: https://github.com/apache/camel-kit/pull/150#issuecomment-6580236904
### Live Pi Certification Evidence — 2026-11-02
**Revision:** `42a4d0ef` + `ShipStageResult` parser resilience fix (new
commit)
**Environment:**
| Component | Version | Path |
|-----------|---------|------|
| OS | Linux 6.8.0-117-generic aarch64 | Docker
`eclipse-temurin:21-jdk-jammy` |
| Java | 21.0.12.1 (Temurin LTS) | `/opt/java/openjdk/bin/java` |
| Pi | 0.84.2 | `/root/.nvm/versions/node/v22.22.2/bin/pi` |
| Node | 22.22.2 | `/root/.nvm/versions/node/v22.22.2/bin/node` |
| API | Red Hat EnMaaS | `api.enmaas.devshift.net` |
**Command:**
```bash
CAMEL_KIT_SHIP_LIVE_PI=/root/.nvm/versions/node/v22.22.2/bin/pi \
CAMEL_KIT_SHIP_LIVE_NODE=/root/.nvm/versions/node/v22.22.2/bin/node \
./mvnw -B -pl kit/camel-kit-core -am -Plinux-ship-certification \
-Dformat.skip=true -Dmaven.test.failure.ignore=true \
-Dit.test=ShipCoordinatorLiveIT verify
Result:
ShipCoordinatorLiveIT.documentDrivenWorkflowCompletesWithRealPiAndLocalEvidence
— PASS (154.4s)
All five stages (DISCOVERY → DESIGN → PLAN → EXECUTE → VALIDATE) completed
on single attempts, document-driven with oversight NEVER. ShipLocalStamp status
PASS with all six mandatory tool versions (pi, node, java, camel, os,
architecture) and all five checks (artifact-policy, catalog-usage,
route-schema, main-runtime-resolve-and-start, citrus-integration-test-001)
passing. Pi 0.84.2 and Node 22.22.2 both reported SUPPORTED.
Parser fix required: Pi 0.84.2 wraps stage JSON in markdown prose despite
the prompt's "do not use Markdown fences or surrounding prose" instruction.
ShipStageResult.parse() now extracts JSON from markdown code fences as a
fallback, using the first ```json ``` block or first {…} boundary when raw
parsing fails. Existing ShipStageResultTest (10 tests) and focused
ShipCommandTest tests pass.
--
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]
