[Chore] Prepare 0.1.0 minor release notes

[roomote-roomote]

Opened on behalf of Matt Rubens. Follow up by mentioning @openmote, in the web UI, or in Slack.

Related issue

N/A — internal Roomote release prep (changeset notes + release-skill guidance).

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

What changed

Adds the remaining post-0.0.4 user-facing/operator-facing release notes under .changeset/ so the next product release can be cut as 0.1.0 (minor).

Also tightens changeset authoring conventions after review:

• Normalizes every pending changeset frontmatter to a single '@roomote/web': <level> line (package names only carry bump level; multi-package maps looked like inaccurate package inventories).
• Updates .agents/skills/changeset-release-pr/SKILL.md and .changeset/README.md so future release prep always uses that single conventional package line and states expected version with real semver math (0.0.4 + minor → 0.1.0).

This PR does not bump package.json or edit CHANGELOG.md — merging it lets release CI open or refresh the Release Roomote 0.1.0 Version PR, which applies the bump and changelog.

Expected next version

0.0.4 → 0.1.0 (highest pending level across all changesets is minor).

Drafted CHANGELOG preview

Minor changes

• Plan mode is now always on; the planning model role is renamed to Advisor and also powers a coding-agent advisor subagent when stuck or seeking a second opinion.
• Bitbucket Cloud is a first-class source-control provider (API-token auth, per-workspace repo sync, webhooks, PR automation, task git credentials, SDK PR ops).
• Zero is available as a deployment-scoped workspace wallet integration (Settings connect, Zero MCP, on-demand CLI, packaged skill).
• Task analytics can switch the chart between Tasks, Tokens, and Cost (URL-backed metric=).

Patch changes

• /auth/dev-login requires explicit WEB_DEV_LOGIN_ENABLED=true opt-in (local/pnpm dev still set it automatically).
• Slack-started tasks can create/update environments via live acting-user resolution.
• Slack/Telegram cancel works when the run has no live acting user.
• Settings → Sandboxes surfaces base-image provisioning progress, failures, and retry.
• Worker sandboxes no longer inject hosting deployment APP_ENV/R_APP_ENV into user-facing task/shell env.
• Slack-started tasks get external integration MCPs again (mapped human initiators + deployment-scoped connectors without a hard actor requirement).
• Zero CLI install uses its own npm prefix so enabling Zero cannot prune sandbox runtime packages.
• OpenCode turns recover from stalled model streams instead of hanging and dropping follow-ups.
• Teams bot credentials fall back to Microsoft app env vars when dedicated R_TEAMS_BOT_* pair is unset.

intentionally skipped (no new notes)

Chores and polish that ride along without a changelog bullet: lightbulb Advisor icon (#196), fictional test fixtures (#192), main-image build dispatch (#190), GitHub bot-identity refactor (#177). Already-covered merges: Advisor (#193), worker app env (#195), Slack cancel (#191), env writes (#188), planning-model env forward (#187), dev-login flag (#186), Sandboxes provisioning (#175). The changeset-release skill itself is updated in this PR for process only (no product release note).

How it was tested

• Diff base v0.0.4 / root version 0.0.4 / CHANGELOG top section reviewed.
• Classified git log v0.0.4..origin/develop --oneline --first-parent against pending .changeset/*.md.
• Confirmed computeNextVersion('0.0.4', ['minor', 'patch']) → 0.1.0.
• Normalized all pending changesets to single '@roomote/web' frontmatter; pre-push lint:fast / check-types:fast / knip green.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset

Impact

Merging this PR does not ship the version bump by itself. Once it lands on develop, release CI will open or refresh Release Roomote 0.1.0, which is what updates version + CHANGELOG; merging that Version PR then cuts the promote-to-main path as usual. Future release prep should no longer invent multi-package frontmatter or mislabel minor bumps as X.Y.Z+1.

[roomote-roomote]

Re-reviewed the latest commit that normalizes every changeset to a single '@roomote/web' bump line and documents the version math in the changeset skill/README. No new issues. Bump levels are unchanged (highest is still minor, so the next version stays 0.1.0), the release script (scripts/release/lib.mjs) ignores package names entirely, and the added semver guidance (0.0.4 + minor = 0.1.0) matches computeNextVersion. The earlier package-attribution note is now resolved by the deliberate single-package convention. See task

• 🟢 Non-blocking (resolved): changeset package attributions previously didn't match the packages actually changed by the underlying PRs. The new commit normalizes all frontmatter to a single '@roomote/web': <level> line and codifies "frontmatter is bump-level only" in .changeset/README.md and the changeset-release-pr skill, so the attribution-accuracy concern no longer applies. Confirmed no release impact: scripts/release/lib.mjs reads only each note's highest bump level (changelog grouping) and the max level across notes (root version).

[roomote-roomote]

Addressed the package-attribution note: every pending changeset now uses a single '@roomote/web': <level> frontmatter line (package names only carry bump level for the product version), and .agents/skills/changeset-release-pr + .changeset/README.md spell that out—plus the minor version math (0.0.4 → 0.1.0)—so future release prep doesn't invent multi-package maps again.