I3071 — /ui/delivery shows how much landed work waits for a release, and since when
Read release.currency on /ui/delivery as one more source, asked without the version, because the hero's Next reads release.version and one screen names one next version. The hero gains a Since then tile with the stance (current, owed, overdue or unknown). A panel, Is the trunk released?, shows the answer's sentence, the count of landed commits and landings, the wait and how it was dated (as this clone saw it land, or at most from the commit time), and the release it is measured from. Its source line leads to the capability's API route and technical view, like every other value on the screen. The panel says that a published snapshot shows it as read when the snapshot was built. Case 3471 serves the screen over a fixture and holds it to the answer, and the intent's criterion shown names that case.
BLOCKED wave 1 · p2 · implementation profile · runs alone
Blocked. This issue cannot start until I3070 is done. The status is derived from that, not declared.
Objective
Read release.currency on /ui/delivery as one more source, asked without the version, because the hero's Next reads release.version and one screen names one next version. The hero gains a Since then tile with the stance (current, owed, overdue or unknown). A panel, Is the trunk released?, shows the answer's sentence, the count of landed commits and landings, the wait and how it was dated (as this clone saw it land, or at most from the commit time), and the release it is measured from. Its source line leads to the capability's API route and technical view, like every other value on the screen. The panel says that a published snapshot shows it as read when the snapshot was built. Case 3471 serves the screen over a fixture and holds it to the answer, and the intent's criterion shown names that case.
Why
The delivery screen is where a person checks whether work reached the public. Release debt is the step between merged and published that it does not show.
Current state
/ui/delivery shows integration and deployment facts and no release debt.
Desired state
/ui/delivery says whether the trunk has been released, from the same answer the brief and doctor read.
Scope
- apps/majordomus-cli/src/ui/delivery.rs
- docs/MAJORDOMUS_UI.md
- docs/RELEASE.md
- .ai/repo/project/intents/a-version-follows-every-session.yaml
- .ai/repo/rules/project/land-and-publish.v1.md
- test/cases/3471_the_delivery_screen_shows_what_waits_for_a_release.sh
Dependencies
Acceptance criteria
- /ui/delivery shows release.currency's stance, its sentence, its counts, its wait and how it was dated, and the release it is measured from, each equal to what release.currency answers, and its source line leads to the capability's API route and technical view
- The screen names one next version, the hero's, read from release.version
Validation
- bin/majordomus plan validate
- bash test/run.sh 3471_the_delivery_screen_shows_what_waits_for_a_release
Evidence required
- case_the_delivery_screen_shows_what_waits_for_a_release
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I3071.yaml. Read it back with majordomus plan show I3071.