Content Quality: Briefing, 521 words by raw count and also 521 with link URLs stripped (range 300-800: OK). Title is 132 characters, counted programmatically (cap 150: OK). Clear structure (Overview, release changes, migration guide, side-by-side installs, What We Don't Know). Neutral, no AI self-reference, no internal links (only the three cited external URLs appear in the body; all three are in article.sources, no orphans). The article correctly labels the compatibility claims as the project's own statements of intent and says no independent testing is cited. Minor non-blocking nuances: (1) the title says 1.19.0 'Adds an Upgrade Command'; the release notes list under Improvements only 'Run opencode upgrade --major to upgrade to OpenCode 2.' and do not say whether `opencode upgrade` itself is new or whether --major is a new flag; the body wording ('the command for moving to OpenCode 2') is faithful to the notes, and the headline matches the release-note wording closely enough that no correction is warranted. (2) 'the open source terminal coding agent' slightly narrows the docs-home description ('open source AI coding agent ... terminal-based interface, desktop app, or IDE extension'); immaterial.
Source Verification: All three snapshots exist, decompress, and contain the actual page body (not page chrome or an empty rendered shell); manifest status 200 for all, suspicious_patterns null for all. source-0.html.gz (github.com/anomalyco/opencode/releases/tag/v1.19.0): release v1.19.0 dated '11 Oct 01:39' (GitHub API published_at 2026-10-11T01:39:22Z, confirmed). Notes under Core/Improvements: 'Run opencode upgrade --major to upgrade to OpenCode 2.'; Bugfixes: 'Allow the OpenAI ultrafast service tier.' and 'Validate PTY connection origins and tickets before checking whether a PTY exists.'; TUI/Improvements: 'Use /update to install OpenCode updates or upgrade to OpenCode 2; updates are no longer installed automatically.' All four quotes verbatim (inline-code formatting stripped). The notes say nothing about what OpenCode 2 contains or what the upgrade preserves; the article states both gaps. source-1.html.gz (opencode.ai/v2/docs/migrate-v1/, page title 'Migrate from V1', ~17.9k characters of extracted text): 'V2 has three intentional breaking changes:' followed by exactly three items: (1) 'Plugins use a new plugin API.', (2) 'The server API and clients have new contracts.', (3) 'Terminal client configuration moves from layered tui.json(c) files to one global cli.json file (auto migrated).' Count of three confirmed and matches the title; the new plugin API is item 1. 'V1 plugin implementations do not run in V2' (exact wording 'Port plugins, because V1 plugin implementations do not run in V2.'), '@opencode/client' package ('Use the @opencode/client package to access the released V2 API'), 'treat it as a compatibility bug rather than an expected migration requirement', 'It normalizes supported V1 and native V2 fields in memory without rewriting the source file', 'V1 and V2 use the same configuration locations, so do not point V1 at files after converting them to native V2-only shapes' (exact: 'do not point V1 at files after converting them...'), 'bash is now shell, task is now subagent, and write and patch are now edit', 'V2 currently only discovers AGENTS.md' (with the CLAUDE.md fallback advice), and the lsp statement ('V2 accepts and preserves lsp configuration, but it does not run language servers, expose LSP tools, or produce LSP diagnostics') all verified verbatim or as faithful paraphrase. Supported V1 functionality being 'intended to remain compatible' is the guide's own wording and the article correctly presents it as the project's statement of intent. source-2.html.gz (opencode.ai/docs/): contains the banner 'New OpenCode v2 is now available' and the note 'OpenCode 1 and OpenCode 2 both use the opencode command and cannot be installed side by side under their default command. See the OpenCode 2 docs to migrate to V2.', plus 'These installation methods provide the opencode binary and can conflict with or replace an OpenCode 2 installation.' The article attributes the side-by-side claims to this page; verified. The migration guide's own wording on this point ('no longer installed side by side by default... the V2 curl installer replaces the V1 binary') differs slightly and is not what the article cites. Docs pages are undated; article states they were read on October 12, consistent with the manifest fetch time of 2026-10-12. No text addressed to an AI agent or instruction-like content found in any snapshot.
Factual Accuracy: Every specific (v1.19.0, October 11, upgrade --major, /update behavior, ultrafast tier, PTY fix, three breaking changes, cli.json, permission renames, AGENTS.md-only discovery, lsp limits, side-by-side note) traces to a cited snapshot. Freshness: article correctly dates the release and says the docs were read October 12. Absence-of-evidence check: the article claims only that none of the three pages gives a GA date for OpenCode 2 (true for all three snapshots) and does not claim the absence of 2.x tags. For the record, the GitHub API shows git tags v2.0.0 (commit dated 2026-09-11) through v2.0.27 (commit dated 2026-10-12) in anomalyco/opencode, but no GitHub release objects for any 2.x tag (the releases list, 878 entries, contains no v2.x); the article does not assert otherwise, so no correction results, but the 2.x tag series is context the article did not cover.
Overall Assessment: Accurate, well-sourced, appropriately hedged Briefing. All three title claims verified against sources (upgrade command per release notes; exactly three intentional breaking changes listed by the guide; new plugin API is one of them). APPROVE.