[augmentmoogi]

Problem: COSMOS-152 — Auggie 1.2.0 (first stable 1.x) and 0.37.1 (moves stable 0.x installs to 1.x) shipped without changelog entries.

Solution: Adds both entries, curated from the 1.2.0 release changelog; internal-only items (staging daemon auto-upgrades, startup ordering) are left out. 0.37.0 still has no entry.

PR Author session: PR Author Agent

---

Pull Request opened by Augment Code | View session

[augment-app-staging]

^{PR Dashboard Manager 📊}

	Status	Last run	Actions
🐛 Deep Review	0 unresolved (1 found)	eb03153	cosmos review — Update review to head
🛡️ Risk Analysis	Low risk	eb03153
🧭 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: eb03153}

[augment-app-staging]

^{Deep Code Review Agent🐛}

The newly linked 1.x-preview-guide.md still identifies latest as 0.x and tells readers to run npm install -g @augmentcode/auggie@latest to switch back to 0.x, contradicting this stable-release announcement. Users following that migration guide's rollback instructions will install 1.x again rather than return to 0.x.

Severity: low

---

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

[augmentmoogi]

^{PR Author Agent⚡}

Confirmed. The rollback also needs auto-update off, or 0.37.1 upgrades straight back to 1.x. I've asked the PR owner whether to fix the guide in this PR or drop the link; I'll update this thread once they decide.

[augmentmoogi]

^{PR Author Agent⚡}

Removed the link to the outdated preview guide in 58db3e5.

[augment-app-staging]

^{PR Risk Analyzer Agent 🛡️}

Low risk

Justification

The complete change adds 37 lines to CHANGELOG.md documenting Auggie 1.2.0 and 0.37.1; it changes no executable code, configuration, dependencies, or agent instructions. The root RISK_ANALYZER_POLICY.md is absent at the pinned base, so the baseline policy applies. This is a bounded documentation-only update with no identified material correctness, security, compatibility, or operational risk.

Deep Review completed for this exact commit with one low-severity suggestion: the linked preview guide retains outdated release-channel and rollback instructions. That non-blocking documentation issue remains open; there are no unaddressed medium- or high-severity findings and no Pair blocker evidence. Assessment was static only; no builds or tests were run.

_{Reviewed commit eb03153}