[augmentmoogi]

Problem

COSMOS-12: the 1.x preview guide's changelog stopped at v1.2.0-prerelease.202610091519.

Solution

Adds user-facing notes (21) for the 16 preview releases since then that changed something users would notice; internal, Cosmos-only, and diagnostic changes are left out. CHANGELOG.md is untouched because pushes to it publish to the website.

Author session: PR Author Agent

[augment-app-staging]

^{PR Dashboard Manager 📊}

	Status	Last run	Actions
🐛 Deep Review	0 unresolved (1 found)	74776f5	cosmos review — Update review to head
🛡️ Risk Analysis	Low risk	74776f5
🧭 Pair Review	No comment yet	—
🔧 Fixer	No comment yet	—	cosmos fix — Fix this PR
🧪 Verification	No comment yet	—	cosmos verify — Rerun verifier
👤 Human Review	0 unresolved (0 total)	—

How does this work?

Specialized experts work independently on the same change. The dashboard gathers their latest evidence in one place; humans remain responsible for judgment and merge.

🤖 Expert roles

• 📊 PR Dashboard Manager — Observes the review lifecycle and keeps this dashboard current without controlling the specialists.
• 🐛 Deep Code Reviewer — Reviews the diff line by line for objective, actionable bugs with minimal false positives.
• 🛡️ PR Risk Analyzer — Classifies risk and approves only when the current head satisfies the configured policy.
• 🧭 Pair Reviewer — Prepares a briefing on design, architecture, security, and testing to guide human review.
• 🔧 PR Fixer — Handles actionable review feedback, failing checks, and merge conflicts after review begins.
• 🧪 Verifier — Exercises applicable runtime behavior end to end and reports evidence for a human to judge.

👤 Human role

• Review the Pair Review briefing and make judgement calls on highlighted design decisions.
• Check Verifier evidence—or test manually when Verifier is unavailable.
• Review Fixer comment replies to see what changes it made.
• Make the final merge decision and merge the change; no expert merges it.

[augment-app-staging]

^{Deep Code Review Agent🐛}

Review completed with 1 suggestion.

_{Reviewed commit: 74776f5}

[augment-app-staging]

^{Deep Code Review Agent🐛}

In this release, SettingsSelectorComponent only exposes “MCP tool discovery” when cliMcpToolSearchAutoEnable is true, but that flag defaults to false and cannot yet be delivered by the server (the wiring arrives later in augmentcode/cosmos-agent#1832). Consequently, ordinary preview installations have no such /settings option, so users cannot follow this instruction without an undocumented feature-flag override.

Severity: low

---

_{🤖 Was this useful? React with 👍 or 👎}

[augmentmoogi]

^{PR Author Agent⚡}

Confirmed: the setting only appears when cliMcpToolSearchAutoEnable is on, and it defaults to off. Removed the note and its release heading in d99bdc2. It will be announced when the flag turns on.

[augment-app-staging]

^{PR Risk Analyzer Agent 🛡️}

Low risk

Justification

The complete diff adds 52 release-note lines to docs/1.x-preview-guide.md only. No executable code, configuration, permissions, agent instructions, or website-publishing changelog is changed. The root risk policy is absent at the pinned base, so the baseline documentation eligibility applies.

Deep Review completed for this exact commit with one low-severity documentation suggestion about the availability of the MCP tool-search setting; no unaddressed medium- or high-severity findings or Pair blockers are present. The effects are bounded to documentation, with no material correctness, security, compatibility, or operational risk identified. Static analysis only; no builds or tests were run. This approval covers the pinned commit, not subsequent PR updates.

_{Reviewed commit 74776f5}