chore: bump to 0.5.4 to unbreak the TUI propose overlay - #181
Merged
Conversation
Patch: one fix, #180. No schema change, no rail change, nothing that alters what the agent trades or when. 0.5.3 shipped the propose overlay picking the newest `*.json` in the proposals directory. That directory is shared -- a scout run writes a shortlist plus sibling param-proposal and research-brief files -- so the overlay selected whichever was written last and reported the operator's own strategy output as a malformed shortlist. Selection now matches the filename convention (`*shortlist.json`), so a sibling written seconds later cannot shadow the real shortlist. Worth cutting on its own rather than batching: the overlay is unusable on the deployment until this ships, and it is the surface the whole admission workflow was added for. uv.lock relocked in the SAME commit, per 0.5.0-0.5.3. Verified with `uv sync --frozen`, which accepted the lock and rewrote nothing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only — no code changes. Ships #180.
Patch: no schema change, no rail change, nothing that alters what the agent trades or when.
Why this is worth cutting on its own
0.5.3 shipped the propose overlay selecting the newest
*.jsonin the proposals directory. That directory is shared — a scout run writes a shortlist plus sibling param-proposal and research-brief files — so the overlay picked whichever was written last and told the operator their own strategy output was a malformed shortlist.The overlay is unusable on the deployment until this ships, and it is the surface the entire admission workflow in #176 was added for. Batching it behind other work would leave the feature broken on the box for no reason.
uv.lockrelocked in the same commit, per 0.5.0 through 0.5.3. Verified withuv sync --frozen, which accepted the lock and rewrote nothing beyond the fivepyproject.tomlbumps.Gate: 2085 tests pass, ruff clean.
🤖 Generated with Claude Code