[steipete]

Prepare the next maintenance release notes by rewriting only Unreleased, ordered by user impact. Consolidate the existing browser, remote-service, Azure, and dependency fixes and restore missing entries for dry-run isolation, dead-controller session cleanup, Deep Research effort, and Japanese effort labels. All released sections are byte-identical.

Merge LAST, after #452 and #454. #450 and #453 have merged. All three remaining PRs are independently based on main at 7481937, and #452/#454 no longer edit CHANGELOG.md. This PR is the single owner of their release-note coverage and preserves the complete proposed Unreleased section. It does not claim the two pending fixes have merged.

Current head: a262502. The complete draft is byte-identical to the previous release-notes head fc6c88d. Released sections from 0.18.0 onward remain byte-identical to main.

Recommendation: patch 0.18.1, not a minor release. No version bump, tag, release, package publication, or tap update is performed here.

Validation: checked the complete non-merge history since v0.18.0, verified contributor attribution for the added dead-controller entry, checked formatting and diff whitespace, and verified released sections remained byte-identical. Fresh branch autoreview against origin/main is scoped-clean through P2. Formatting and diff checks passed; exact-head CI is recorded in the final proof comment.

Publication gates remain separate: CI on the integrated main head, signed-in Pro/reattach smoke, notifier signing/notarization verification, npm artifact verification, GitHub release assets, and Homebrew tap update. Issue #443 confirms that v0.18.0 still lacks its expected GitHub tarball; repairing that publication requires release authorization.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs changes before merge. Reviewed September 5, 2026, 6:16 PM ET / 22:16 UTC.

ClawSweeper review

What this changes

Rewrites Oracle’s Unreleased changelog into impact-ordered maintenance notes, restores omitted fixes, and preserves all released sections.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The focused changelog revision remains useful and has no actionable patch defects. The owner’s explicit merge-order requirement still applies to the two pending browser fixes.

Priority: P3
Reviewed head: a262502c88477f5292497551b3231900bb0ba60b

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, coherent documentation patch with preserved release history and no blocking correctness findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: This owner-authored changelog PR changes no production behavior; runtime proof for the prerequisite fixes belongs to their implementation reviews.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This owner-authored changelog PR changes no production behavior; runtime proof for the prerequisite fixes belongs to their implementation reviews.
Evidence reviewed	5 items	Verified scope and preserved release history: The pinned base-to-head diff changes only Unreleased: 22 additions and 23 deletions in CHANGELOG.md. A read-only byte comparison confirmed that sections from 0.18.0 onward are identical; the revised section contains 20 bullets. The whitespace check passed and the checkout remained clean. Current merge prerequisites: The captured PR body explicitly requires landing after #452 and #454. Both remain open in the supplied context; #450 and #453 are verified merged there. The release-notes branch intentionally owns the pending fixes’ changelog coverage. Maintenance history and routing: The non-merge history since v0.18.0 includes the restored dry-run, Japanese effort-label, Deep Research thinking-time, and dead-controller fixes. Main-branch changelog history shows repeated release and maintenance work by Peter Steinberger, supporting routing to steipete independently of this PR’s authorship.
Findings	None	None.
Security	None	None.

How this fits together

Oracle’s changelog explains browser, CLI, and provider changes to users. Its version sections supply the notes copied into GitHub releases.

flowchart LR
  A[Maintenance fixes] --> B[Unreleased changelog]
  C[Pending browser fixes] --> B
  B --> D[Release preparation]
  D --> E[Published release notes]

Loading

Before merge

• Complete next step (P2) - Land after fix(browser): stop remote runs when isolated tab creation fails #452 and fix(browser): block sends while attachments are uploading #454, then confirm the complete Unreleased text matches the integrated changes.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Release-history preservation	1 file changed; all released sections byte-identical	The edit stays within Unreleased without rewriting published history.

Technical review

Best possible solution:

Keep one consolidated, product-facing Unreleased section that accurately reflects the integrated fixes and retains the explicit remote-service breaking-change notice.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR edits release notes rather than runtime behavior; its scope and preservation claims are directly checkable from the diff.

Is this the best way to solve the issue?

Yes: consolidating Unreleased in a single documentation PR follows the repository’s release guidance and avoids competing changelog edits.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 748193758d54.

Labels

Label justifications:

• P3: This is release-note consolidation with no runtime or publication changes.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This owner-authored changelog PR changes no production behavior; runtime proof for the prerequisite fixes belongs to their implementation reviews.

Evidence

What I checked:

• Verified scope and preserved release history: The pinned base-to-head diff changes only Unreleased: 22 additions and 23 deletions in CHANGELOG.md. A read-only byte comparison confirmed that sections from 0.18.0 onward are identical; the revised section contains 20 bullets. The whitespace check passed and the checkout remained clean. (CHANGELOG.md:3, a262502c8847)
• Current merge prerequisites: The captured PR body explicitly requires landing after fix(browser): stop remote runs when isolated tab creation fails #452 and fix(browser): block sends while attachments are uploading #454. Both remain open in the supplied context; fix(cli): honor configured remote Chrome defaults #450 and chore(deps): refresh provider SDKs and test tooling #453 are verified merged there. The release-notes branch intentionally owns the pending fixes’ changelog coverage. (CHANGELOG.md:7, a262502c8847)
• Maintenance history and routing: The non-merge history since v0.18.0 includes the restored dry-run, Japanese effort-label, Deep Research thinking-time, and dead-controller fixes. Main-branch changelog history shows repeated release and maintenance work by Peter Steinberger, supporting routing to steipete independently of this PR’s authorship. (CHANGELOG.md, 748193758d54)
• Release policy: The release checklist calls for product-facing highlights and requires published notes to match the version’s changelog section. This patch changes neither publication machinery nor a released version; publication checks remain separate. (docs/RELEASING.md:27, a262502c8847)
• Re-review continuity and inspection limits: The prior completed review recorded no findings or rank-up moves and required prerequisite landing. The current body narrows that requirement to two pending PRs. The earlier reviewed commit could not be retrieved for an independent byte comparison, and GitHub refresh requests failed because network resolution was unavailable; current-head source inspection and the supplied discussion were available. (a262502c8847)

Likely related people:

• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)

• reviewed 2026-09-05T21:52:54.367Z sha fc6c88d :: needs changes before merge. :: none

[steipete]

LAND-READY after #450, #452, #453, and #454, at fc6c88d.

CI is green on this exact head: https://github.com/steipete/oracle/actions/runs/33994205149. All three OS build/test jobs passed initially. The first Chromium proof attempt failed during browser startup with ECONNREFUSED before either disconnect assertion; rerunning only that failed job passed without a source change.

Branch autoreview against origin/main is scoped-clean through P2. The diff changes only Unreleased; released sections from 0.18.0 onward are byte-identical. The complete non-merge history since v0.18.0 was reviewed, and the four prerequisite PRs carry their own runtime proof and exact-head green CI.

Merge this PR last and preserve its complete Unreleased text when reconciling overlapping changelog edits. Recommended release: patch 0.18.1. No version bump, tag, publication, or issue closure has been performed. Integrated-main CI, signed-in Pro/reattach proof, package/notifier checks, GitHub assets and Homebrew remain publication gates.

[steipete]

LAND-READY after #452 and #454, at a262502, independently based on main 7481937.

Exact-head CI succeeded on Linux, macOS, Windows and the Chromium proof job without a retry: https://github.com/steipete/oracle/actions/runs/33995209563. Fresh branch autoreview against origin/main is scoped-clean through P2. Formatting and diff checks passed.

This changes only CHANGELOG.md. The entire complete draft is byte-identical to fc6c88d, and all released sections from 0.18.0 onward remain byte-identical to main. #450 and #453 have merged; #452 and #454 have no changelog changes, so this is the single owner of the complete Unreleased section. Merge this PR last.

Recommended release remains patch 0.18.1. The v0.18.0 asset diagnosis and required 0.18.1 artifact flow are recorded at #443 (comment). Integrated-main CI, signed-in Pro/reattach proof, notifier signing/notarization, npm verification, uploaded GitHub assets and Homebrew remain release gates. No merge, version bump, tag or publication performed.