In plain English: the version label in the app banner says the wrong version
What is this about: The release bump to 0.88.0 updated most version labels but missed the banner inside the TUI, and the CI test that guards the banner correctly failed.
Why do we need it: Master CI must be green for the master/deploy wait proof (M10) to close.
Why is it still open: Awaiting CI, then merge, then the definitive M10 await on the new master head.
What would let us close this
Banner test green; merged to master
M10 await on new master head resolves success via deploy_qualify
Version impact
patch — same behaviour, correct label
# In plain English: the version label in the app banner says the wrong version
**What is this about:** The release bump to 0.88.0 updated most version labels but missed the banner inside the TUI, and the CI test that guards the banner correctly failed.
**Why do we need it:** Master CI must be green for the master/deploy wait proof (M10) to close.
**Why is it still open:** Awaiting CI, then merge, then the definitive M10 await on the new master head.
# What would let us close this
- [ ] Banner test green; merged to master
- [ ] M10 await on new master head resolves success via deploy_qualify
# Version impact
- [x] patch — same behaviour, correct label
The converged-release bump updated __init__/header but missed the TUI
banner string at rune_tui.py:1888; the banner-surface test correctly
failed master CI. The version-surfaces checker watches the header
comment only — banner added to the gap list for the bump workflow.
🤖Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.
🤖 **Headless spec gate (non-blocking, #204 first slice)**
Spec-gate agent produced no text output — check runner logs.
<details><summary>Deterministic floors still govern the merge</summary>
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
🤖Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.
🤖 **Headless spec gate (non-blocking, #204 first slice)**
Spec-gate agent produced no text output — check runner logs.
<details><summary>Deterministic floors still govern the merge</summary>
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In plain English: the version label in the app banner says the wrong version
What is this about: The release bump to 0.88.0 updated most version labels but missed the banner inside the TUI, and the CI test that guards the banner correctly failed.
Why do we need it: Master CI must be green for the master/deploy wait proof (M10) to close.
Why is it still open: Awaiting CI, then merge, then the definitive M10 await on the new master head.
What would let us close this
Version impact
745b4f7e75toac936a8ba9🤖 Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.
🤖 Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.