[FEATURE]: Docs automation has been dead since the org transfer, and 2.x releases publish no release notes #60273

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The problem

Since 2.0, OpenCode ships features faster than its docs and release notes describe them, so after an update I cannot find out what is new or how to use it. The only way to discover post-2.0 behaviour is to read PRs, source, and git log.

I'm scoping this to the two concrete, cheap items underneath that. The rest of the symptoms are already tracked elsewhere.

Ask 1 — re-enable the docs automation (fixes #57623)

docs-update.yml gates its job on if: github.repository == 'sst/opencode'. The repo moved to anomalyco/opencode, so the condition can never be true: the last successful run was 2026-01-02, and ~582 runs since then are conclusion: skipped. docs-locale-sync.yml is if: false, and the v2 tree has no locale directories at all while v1 has 17.

This was reported in #57623 and confirmed by the triage bot on latest dev. As of today it is still open and unfixed. This is the highest-leverage item here: it is a one-line if: change plus a decision about which docs tree the workflow owns (#57623 notes both workflows write packages/web/src/content/docs/, the v1 tree that serves /docs, while the v2 tree is services/www/src/docs/content/).

Ask 2 — publish release notes for every 2.x release

There is no changelog a user can read for 2.x:

• changelog: v2 releases have no published release notes #52184 and No offical release notes for 2.x.x #50345 — v2 releases have no published release notes
• desktop: What's New popup never appears after updates (changelog.json has no highlights) #60134 — the desktop "What's New" popup never appears, because changelog.json has no highlights
• The /highlights command returns "No matching commands" after upgrading to v2.1.1 #57608 — /highlights returns "No matching commands" on v2.1.1
• [FEATURE]: RSS feed for changelogs #58525 — users are asking for an RSS feed, i.e. building their own change feed

So the in-app surfaces for release notes already exist and are wired to data that is simply never populated. Publishing a short highlights list per release into changelog.json and GitHub Releases would light up the popup and /highlights for free, without new UI work.

For context on pace: since 2026-09-01 the repo has ~3296 commits (commits API, per_page=1, read from the Link header), against 103 commits touching packages/web/src/content/docs and 236 touching services/www/src/docs/content — about 1 in 7. Meanwhile v2.2.0 and v2.2.1 shipped on 2026-10-27 and 2026-10-29.

Why these two and not "write more docs"

Features that exist today but have no documented path to adoption — OTEL support (#47195), opencode mcp add --url/--header from #31054 (#55285), V2 keyless websearch (#54311), V2 service API auth (#51724), subagent_depth defaulting to 1 so subagents silently cannot delegate (#59826) — are a docs-velocity problem, not a docs-effort problem. Fixing the automation that has been dead since January, and telling users what each release changed, addresses the cause rather than the ~25 individual symptoms filed since.