Record browser stable release evidence

[petyosi]

Summary

Record the verified browser RUM stable publication, its exact feature/version merge SHAs, npm and registry-consumer evidence, repaired GitHub release metadata, and the downstream Platform handoff.

The roadmap intentionally remains active and R9 remains in progress until the evidence merge is verified to cause no publication, the feature branch is retired, and the final cleanup record passes its own no-publication gate.

Verification

• pre-commit vp check --fix
• push hook package builds and all package tests
• registry artifact verifier for browser 0.17.0 and replay 0.1.0
• complete npm dist-tag and GitHub tag/release comparison

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cd923b62-4f91-45be-ab19-48f7402c832d

📥 Commits

Reviewing files that changed from the base of the PR and between dbd7125 and e10c8d6.

📒 Files selected for processing (1)

• plans/roadmaps/001-browser-rum-release-remediation.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• pydantic/logfire (manual)
• pydantic/pydantic-ai (manual)

🚧 Files skipped from review as they are similar to previous changes (1)

• plans/roadmaps/001-browser-rum-release-remediation.md

---

📝 Walkthrough

Walkthrough

Updated the browser stable-release runbook and remediation roadmap to mark release criteria complete. Added dated evidence for the stable publication, package versions, npm tag verification, artifact checks, Changesets behavior, and Platform handoff. The roadmap now records the publication results and retains R9 as in progress pending durable evidence and cleanup gates.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title concisely matches the main change: recording browser stable release evidence.
Description check	✅ Passed	The description accurately summarizes the evidence-recording and verification work in the changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch petyosi/r9-release-evidence

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@plans/roadmaps/001-browser-rum-release-remediation.md`:
- Around line 379-381: Update the release validation summary in the roadmap to
explicitly record the GitHub-release recovery exception: the workflow skipped
that step because published=true was unavailable, and GitHub tags/releases were
created manually. Replace the wording that implies the automated GitHub release
gate passed normally, while preserving the documented package and
unrelated-package validation results.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ebad8aaa-62cf-4599-8139-9731b7b9d514

📥 Commits

Reviewing files that changed from the base of the PR and between 1f3b1cb and dbd7125.

📒 Files selected for processing (2)

• plans/031-browser-stable-release-runbook.md
• plans/roadmaps/001-browser-rum-release-remediation.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• pydantic/logfire (manual)
• pydantic/pydantic-ai (manual)