Repository navigation
ci(goal): prove pinned OpenCode 2.1.4 native lifecycle and restart (#283) - #285
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c87a19ebf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| node-version: "24" | ||
| - name: Install exact repository dependencies and build native plugin | ||
| run: | | ||
| npm ci |
There was a problem hiding this comment.
Use an install command that works without a lockfile
This new job always stops here because commit 8674d44 tracks neither package-lock.json nor npm-shrinkwrap.json. Running the exact command reports EUSAGE with npm's explanation that npm ci can only install when one of those lockfiles exists, so the pinned 2.1.4 lifecycle and restart steps never execute. Commit a lockfile or retain npm install for this lane.
Useful? React with 👍 / 👎.
Scope
The current Goal matrix labels a pinned OpenCode 2.0.16 job as "current stable" and tests a moving latest host separately. OpenCode 2.1.4 changes provider-replay and compaction data contracts; a reproducible pinned 2.1.4 real native lane is needed before broad Goal #276 and release upgrades.
Changes
npm ci+ Goal build./goalhost lifecycle, waiting-user and ownership canary, plus same-session re-arm after server restart; prove against actual host, not only mocks.Merge criteria
All PR CI/real-host checks pass and exact 2.1.4 canary produces successful evidence. If host 2.1.4 fails, fix the actual native contract/test and preserve the failure signal; no bypass. This closes only the stable Ubuntu slice of Goal #283, not the entire dev/Windows/macOS matrix. Cross-plugin issue Loop #185.