chore(main): release 0.50.0

[mlorentedev]

🤖 I have created a release beep boop

0.50.0 (2026-08-26)

Features

• agents: fan out the invocable roster — five personas, the steward catalog entry, and a drift guard (#1240) (2729c09)

Bug Fixes

• cli-042: the post-deploy check reported FAIL when healthy and SKIP when dead (#1235) (d49e6f8)
• opencode: drop the ollama provider, which had stopped opencode from starting (#1242) (f2a2d77)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 2fcb9996-19ca-4e3b-9463-3e60158938b3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: bd822c2a-a53b-4571-9c31-17e5e11f1f30

📥 Commits

Reviewing files that changed from the base of the PR and between d49e6f8 and 9423c28.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• versions.conf

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The release metadata was updated from 0.49.0 to 0.49.1 in the release manifest and versions.conf. The changelog now records the 2026-08-26 release and the cli-042 post-deploy check fix.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 9423c

This release updates version metadata and the changelog only; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title says "chore(main): release 0.50.0", but the changed files and PR objective release version 0.49.1.	Change the title to identify the actual release, for example "chore(main): release 0.49.1".
Description check	⚠️ Warning	The description contains Release Please notes but omits the required Summary, SDD checklist, SDD skip rationale, and Test plan sections from the template.	Add the required template sections. Complete the Summary, SDD checklist, and Test plan, or provide a specific SDD skip rationale if using the skip-sdd label.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[mlorentedev]

Review triage

All checks green (goreleaser release is skipping, which is its expected pre-merge state). CodeRabbit reviewed and posted no actionable findings — 0 inline comments. Nothing to apply, ticket, or decline.

Checked explicitly: this release body carries no closing keyword. That is the failure mode #1214 tracks, and it has fired on four consecutive releases — most recently on #1210, which closed #1190 two seconds after merging while two of its acceptance criteria were still unverified.

It did not fire here, and the reason is mechanical rather than lucky: the commits in #1235 deliberately carried no issue footer, so release-please had nothing to aggregate into a closes list. Lesson 115's rule — a sub-PR of a multi-PR sequence must not reference the parent issue in its footer at all — is the thing that held.

Contents: one fix, #1235 (d49e6f8), correcting three defects in CLI-042's post-deploy verification script — a satisfied criterion reported as FAIL, a crash-looping daemon reported as SKIP, and a credential-holding daemon reported as not holding it.

Safe to merge once a human has reviewed it, per the standing rule that a merge is a supervised action.

[mlorentedev]

🤖 Created releases:

• v0.50.0

🌻