Skip to content

chore: bump to 0.5.3 for the asset-admission work - #179

Merged
eaitbrahim merged 1 commit into
mainfrom
chore/bump-0.5.3
Aug 7, 2026
Merged

chore: bump to 0.5.3 for the asset-admission work#179
eaitbrahim merged 1 commit into
mainfrom
chore/bump-0.5.3

Conversation

@eaitbrahim

Copy link
Copy Markdown
Contributor

Version bump only — no code changes. Ships #176, #177 and #178.

Patch: no schema change, no rail change, nothing that alters what the agent trades or when.

Why cut this now rather than wait

#176 fixed a reporting bug that is live on the deployment right now. history was missing from DATA_DERIVED_FAILURES — the tag set marking a failure as downstream of an empty cache — so keel assets propose and keel assets holdings --screen printed:

This is a MISSING-DATA verdict, not a verdict about the asset.
  ✗ history: 0 daily bars < 1460 required

An asset nobody had ever fetched was reported as too young to trade. The fix is at the tag set, and three independently drifting copies of the split were consolidated into one.

Also included

  • The TUI can reach the admission gatescreen / propose / discover in the menu. propose and screen are fully offline; discover is network-gated behind an explicit keypress like f. None can attest, admit, or trade — attest stays CLI-only, since it is the human judgment the gate rests on. An independent review verified this with sockets hard-disabled: zero network calls on open, poll or refresh, and the DB byte-identical across every path.
  • fix(admission): close the non-UTF-8 shortlist hole and pin the claims #176 made #177UnicodeDecodeError subclasses ValueError, not OSError, so a non-UTF-8 shortlist escaped except OSError and broke build_propose_view's documented never-raises contract, wedging the propose overlay on every repaint. Plus tests pinning that both TUI overlays route through _screen_product, which mutation-testing showed was convention-only.
  • feat(tui): show the patch segment in the dashboard header #178 — the header shows the patch segment, so 0.5.1 and 0.5.3 no longer render identically as v0.5.

uv.lock relocked in the same commit, per 0.5.0 through 0.5.2 — leaving it behind is what made 0.4.0 fail its self-identification check. Verified with uv sync --frozen, which accepted the lock and rewrote nothing beyond the five pyproject.toml bumps.

Gate: 2083 tests pass, ruff clean.

🤖 Generated with Claude Code

Patch: no schema change, no rail change, nothing that alters what the agent
trades or when. Ships #176, #177 and #178.

The reason to cut this rather than wait is #176's fix to `DATA_DERIVED_FAILURES`,
which is a reporting bug live on the deployment right now: `history` was missing
from the tag set that marks a failure as downstream of an empty cache, so
`keel assets propose` and `keel assets holdings --screen` printed
`x history: 0 daily bars < 1460 required` directly beneath their own note saying
the verdict was about missing data rather than about the asset. An asset nobody
had ever fetched was reported as too young to trade.

Also in: the TUI can now reach the admission gate (`screen`/`propose`/`discover`,
read-only, `discover` network-gated behind an explicit keypress like `f`); the
non-UTF-8 shortlist hole that broke `build_propose_view`'s documented never-raises
contract; and the header now shows the patch segment, so 0.5.1 and 0.5.3 no longer
render identically as `v0.5`.

uv.lock relocked in the SAME commit, per 0.5.0-0.5.2. Verified with
`uv sync --frozen`, which accepted the lock and rewrote nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@eaitbrahim
eaitbrahim merged commit a2a1ea6 into main Aug 7, 2026
1 check passed
@eaitbrahim
eaitbrahim deleted the chore/bump-0.5.3 branch August 7, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant