promote: stable v1.18.1 — sync stable tag with latest

[ranxianglei]

Promotes npm dist-tag stable from 1.14.26 → 1.18.1, bringing @stable in line with the current @latest release. Requested in #400 (floor 6): "本项目先发一个stable版本".

Why

• v1.18.1 has been running as latest since 2026-09-15 (PR release: v1.18.1 — paper preprint v0.2 into the repo (docs only) #401, docs-only patch) — ~2 days of production validation
• stable has sat at 1.14.26 since 2026-09-03 (PR promote: stable v1.14.26 — sync stable tag with latest (1.14.19 → 1.14.26) #358) — seven releases behind
• The README install command is opencode plugin opencode-acp@stable --global, so @stable users are missing high-severity fixes: context-limit safety net ([Bug] In-flight prune is a no-op (postTokens == prePruneTokens) at 229k tokens → request exceeds server context → empty-response resume loop #346) + budget guard ([Bug] Silent context-overflow death on resume when model reports limit.context=0 (custom providers): uncalibrated thresholds → 400 → empty exit-0 loop #347) in v1.17.0, and the transform performance fix 13.6 s → 1.2 ms (perf: avoid transform work that scales with compression history #384/perf: avoid transform work that scales with compression history (#384) #385) in v1.17.1

What this PR does

No code changes — devlog only (devlog/2026-09-17_promote-stable-v1.18.1/REQ.md + WORKLOG.md). On merge, release.yml Pattern 3/4 detects the promote-stable branch name / commit title and runs npm dist-tag add opencode-acp@1.18.1 stable. package.json version is untouched → no changelog entry required (check-pr skips it).

Content shipped in stable 1.14.26 → 1.18.1

Version	Headline
v1.14.27	Self-disable also triggers in manual proxy mode (/bili/ baseURL detection, #338); soft deprecation of minContextLimit/modelMinLimits (#352)
v1.15.0	compress.reasoning — drop oversized thinking from closed-turn compress calls (#377, fixes #368)
v1.16.0	Top-level storagePath — relocate session-state files (#380, fixes #379)
v1.17.0	Context-limit safety net (#349, fixes #346) + context budget guard (#350, fixes #347) — no more silent HTTP-400 death loops; plus nudge/exec counter alignment, tier-aware cadence reset, reasoning tokens in estimates, /acp error-log leak fix
v1.17.1	Transform no longer scales with compression history: 13.6 s → 1.2 ms (#385, fixes #384); qualityGate.algorithms false warning fix (#389); fork PR builds green again (#390)
v1.18.0	Adaptive compression candidates (MICRO/EPISODE targets) — opt-in via compress.candidates, default OFF is byte-exact v1.17.1 (#341)
v1.18.1	Paper preprint v0.2 into the repo (docs only, #394)

Note: PR #403 (Windows path-separator normalization in protectedFilePatterns) landed after v1.18.1 and rides the next patch release — it does not block this promotion.

Verification

• ./scripts/ci/check-pr.sh 2026-09-17_promote-stable-v1.18.1 origin/master — all checks passed (branch name, devlog REQ/WORKLOG present, version unchanged)
• npm run typecheck — clean; npm run build — success
• npm test — 1265/1267 pass; the 2 failures are local-environment artifacts (both tests hardcode /tmp paths, which is a read-only mount in the agent sandbox; pre-existing on master, unaffected on CI runners where /tmp is writable)

[github-actions]

📦 Built Plugin Artifact

Branch: 2026-09-17_promote-stable-v1.18.1 (ae1ab8a)

Option A — Install from npm PR tag (recommended)

opencode plugin opencode-acp@pr-433 --global

Each push to this PR publishes a new version under the pr-433 npm tag.

Option B — Install from GitHub

opencode plugin "github:ranxianglei/opencode-acp#2026-09-17_promote-stable-v1.18.1" --global

Option C — Download artifact

1. Download the artifact from the Actions run
2. Extract the tarball and install:

tar xzf opencode-acp-pr433.tgz
cp -r package/dist ~/.cache/opencode/packages/opencode-acp@latest/node_modules/opencode-acp/dist

3. Restart opencode to pick up changes.

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Verifying PR #433 (promote-stable v1.18.1). Findings so far:

Branch & diff — pulled 2026-09-17_promote-stable-v1.18.1 (head ae1ab8a7, based on master 06efd39c):

• Diff vs master is exactly 2 files, both additive: devlog/2026-09-17_promote-stable-v1.18.1/REQ.md (+28) and WORKLOG.md (+23). No code, config, workflow, or package.json changes — matches the promote-only pattern of promote: stable v1.14.11 — sync stable tag with latest #270/promote: stable v1.14.12 — sync stable tag with latest #273/promote: stable v1.14.13 #283/promote: stable v1.14.19 — pipeline-fixed release incl. 14.14/14.16 content #309/promote: stable v1.14.26 — sync stable tag with latest (1.14.19 → 1.14.26) #358.

Mechanism — confirmed in .github/workflows/release.yml:

• Commit title promote: stable v1.18.1 — sync stable tag with latest (1.14.26 → 1.18.1) matches Pattern 3 (^promote: stable v[0-9]+\.[0-9]+\.[0-9]+) and branch name matches Pattern 4 (..._promote-stable-v...), so either merge style triggers the "Promote to npm stable tag" step: npm dist-tag add opencode-acp@1.18.1 stable.
• The promote step is independent of the publish path — since package.json version is unchanged, no release/tag/npm-publish happens, consistent with the issue description.

npm state (live check): stable: 1.14.26, latest: 1.18.1 — promotion target exists and is current.

CI: pr-validation ✅, build ✅, build-artifact ✅, test (22) ✅, test (24) ✅; e2e still running — I'll confirm as soon as it finishes.

Merge is a human-only operation per project rules — click merge when ready; CI will do the dist-tag update automatically. After merge, verify with npm view opencode-acp dist-tags → expect stable: 1.18.1.

初步结论：分支仅含 devlog（无代码改动、version 未动），release.yml 的 promote-stable 触发路径已核实，CI 基本全绿，等 e2e 跑完即可由人工合并。

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 CI fully green — PR #433 verified and ready to merge.

Final check-run status on head ae1ab8a7:

Check	Result
pr-validation	✅ success
build	✅ success
build-artifact	✅ success
test (Node 22)	✅ success
test (Node 24)	✅ success
e2e	✅ success

Also re-confirmed just now: the branch still contains current origin/master (06efd39c) — no rebase needed. The 2 local test failures noted in the issue body are sandbox-only artifacts (read-only /tmp); both pass on CI runners as expected.

Summary of verification:

1. Diff = 2 devlog files only (REQ.md + WORKLOG.md); zero code/config/workflow changes; package.json version untouched → no changelog requirement, no npm publish triggered.
2. Merge commit will match release.yml Pattern 3 (squash title promote: stable v1.18.1 — …) or Pattern 4 (standard merge of branch …_promote-stable-v1.18.1) → CI runs npm dist-tag add opencode-acp@1.18.1 stable.
3. Live npm state pre-merge: stable: 1.14.26, latest: 1.18.1.

Next step is yours: merge the PR (human-only per project rules). After the workflow completes, verify with npm view opencode-acp dist-tags → expect stable: 1.18.1; the workflow also comments on the PR with the promotion confirmation.

中文摘要：已核对 PR 仅含 devlog、无代码与版本改动，release.yml 的 promote-stable 触发路径（Pattern 3/4）确认无误，全部 6 项 CI 检查通过且分支与 master 同步——可以合并，合并后 CI 会自动把 npm stable 标签指向 1.18.1。

[github-actions]

✅ Promoted opencode-acp@1.18.1 to npm stable tag.

opencode plugin opencode-acp@stable --global