[lx-0]

Follow-up to #32: the two findings of the Codex re-review on 8dd603e, which arrived after the merge, plus the 0.5.0 release commit.

What

• Default ref selection by ancestry (bin/ytstack-status). The script picked the newer of origin/<default> and <default> by committer date. Dates tie at second resolution and can run backwards, so a fetched origin/<default> that was ahead could lose to a stale local branch. Now: origin/<default>, unless the local <default> contains it (unpushed commits). Diverged refs resolve to the remote one.
• Integration snippet survives set -e / pipefail (docs/statusline.md). Both lines end in || true: the script exits 1 when it has nothing to print, and the glob fails while the plugin is not installed. Either one killed a status line script that runs under set -e.
• STATE.md no longer says PR feat: status line segment (bin/ytstack-status) with STATE progress block #32 is open.

Release 0.5.0

plugin.json, marketplace.json and the Codex manifest are at 0.5.0, as are the README badge and status line. CHANGELOG [Unreleased] is folded into [0.5.0] - 2026-11-11. The tag v0.5.0 goes on the merge commit once main is green.

Verification

• tests/ytstack-status.test.sh: 36 cases pass. Two are new or changed and failed before the fix: origin ahead with an older committer date, and an unpushed local default branch with an older date than origin.
• bash tests/run-all.sh: 13 suites pass on macOS. bin/ytstack-check: 27 warnings, as on main. codex_plugin_test.py (manifest agreement) OK, claude plugin validate . passed.
• The documented snippet ran under set -euo pipefail against a fake plugin cache: inside a project it appended the segment, outside a project and with no plugin installed it printed the plain line, exit 0 each time.

🤖 Generated with Claude Code

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 1e2c3537-0fed-4aba-91a5-dfd19463ac19)

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-11T10:55:44.597529Z	c6ec86e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 6936b17a-3a84-4ced-b563-47c8a8c8b9c5)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c6ec86e2ec

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".