chore(release): 0.9.0

[stephane-segning]

1. Summary

This PR changes:

• Dates the CHANGELOG.md [0.9.0] section from "unreleased" to 2026-07-28.
• No package.json version changes — all eleven workspace packages were already bumped to 0.9.0 in #61 (the devtools PR). No code changes, no lockfile changes.

It solves:

• Marks the 0.9.0 line ready to publish via publish.yml, per this repo's convention that a release entry gets dated once the packages are ready to ship (see the equivalent 0.8.1 release commit).

---

2. Intent

The intent of this PR is:

Close out the 0.9.0 release line — which already includes the devtools/devtools-mcp packages (#61), the trace log tier + bridge/logging ADRs (#62), and the models-info modelsInfoHideTextOnly + periodic-refresh-scheduler work (#68) — so gh workflow run publish.yml -f dry_run=false can be triggered against main right after this merges.

---

3. Scope

In Scope

• CHANGELOG.md: ## [0.9.0] — unreleased → ## [0.9.0] — 2026-07-28.

Out of Scope

• Any version bump (already done in feat(devtools): add @vymalo/opencode-devtools plugin + MCP server #61).
• Any code or behavior change.
• Triggering publish.yml itself — that happens after this PR merges, as a separate workflow_dispatch.

---

4. Verification

I verified this change by:

• Running automated tests
• Running manual tests
• Checking logs
• Checking metrics
• Testing error cases
• Testing permissions/security behavior
• Testing rollback or failure behavior, if relevant

Commands run:

pnpm format:check
pnpm lint

Results:

biome format packages apps test-env *.json: Checked 242 files in 46ms. No fixes applied.
biome lint packages apps test-env *.json: Checked 242 files in 71ms. No fixes applied.

A full pnpm -r build && pnpm -r typecheck && pnpm coverage was already run and passed for the code content of this release in #68; this PR itself only edits CHANGELOG.md, so no code-affecting checks were re-run.

---

5. Screenshots / Evidence

Add evidence here:

• Screenshot: N/A (changelog-only change)
• Logs: N/A
• Metrics: N/A
• Recording: N/A

---

6. Risk Assessment

Risk level:

• Low

Potential risks:

• None — single-line documentation change, no code or version-field edits.

Mitigation:

• N/A

---

7. AI Usage Declaration

AI was used for:

• Drafting documentation
• Understanding existing code
• Generating code
• Refactoring
• Generating tests
• Reviewing the diff
• Not used

Human verification:

• I understand every meaningful change in this PR
• I checked generated code manually
• I checked generated tests manually
• I removed unsupported AI assumptions
• I accept responsibility for this PR

---

8. Reviewer Focus

Please focus your review on:

• Correctness
• Architecture
• Security
• Performance
• Tests
• Maintainability
• Product intent
• Edge cases

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a0d13a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

✅ AI Governance check passed

This PR declares AI usage, references a source of truth, and provides verification evidence. Thank you.