Repository navigation
feat(opencode): integrate the V2 compatibility chain - #27
Conversation
Integrate the verified V2 beta migration, session-bound local TUI commands, routing correction, npm launcher, and 0.2.0 release metadata into the feature tracker. Retain the current main branch manual review workflow and unchanged dependency versions.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
Run failed. View the logs →
|

Summary
opencode2), including server routing, TUI commands/feedback and installed launcher support.opencode-herdr@0.2.0is published on npm (latest=0.2.0) and GitHub; verified release commit1c29055.Checklist
Test plan
--ignore-scripts --legacy-peer-deps, automatic peer installation not proved).test: CI 37641482198 passed with exact head/current-main binding.v0.2.0at integrated main1c29055; stable GitHub release published. OIDC Publish run 37645115605 passed; npm version andlatestboth 0.2.0, published 37-file package contents match verified main.Chain context
All children were folded leaf-to-root without rewriting branches: 32→31→30→29→28→27. Final tracker retains the exact corrected release source plus current-main manual Pullfrog workflow. Cohesive over-budget slices were accepted under actual repository policy; tests/docs were not cut or compressed.
Verification limits
@opencode-ai/cli@0.0.0-beta-17823, not a blanket claim for all V2 releases.d918d461100b5ca50799ad7d056cded87c231da57c4ae774d5798ffa3784fad7.