I2407 — The monitor is released and deployed
Bump the minor version on the branch, record the CHANGELOG entry, land through the lane, let the release pipeline cut it and verify majordomus.dev serves it.
BLOCKED wave 4 · p1 · implementation profile · runs alone
Blocked. This issue cannot start until I2402, I2404, I2405, I2406 are done. The status is derived from that, not declared.
Objective
Bump the minor version on the branch, record the CHANGELOG entry, land through the lane, let the release pipeline cut it and verify majordomus.dev serves it.
Why
Owner: version bumped, deployed, used.
Current state
0.20.0 is released without it.
Desired state
The next minor release carries majordomus monitor and the site serves its docs and article.
Scope
- apps/majordomus-cli/Cargo.toml
- CHANGELOG.md
Dependencies
- I2402READY majordomus monitor follows the stream from a terminal and a script
- I2404READY The Cockpit shows the stream live
- I2405READY Every session is told what happened since its last look
- I2406BLOCKED The stream is documented where a reader looks
Acceptance criteria
- The released version's majordomus monitor answers
- majordomus.dev serves latest.json at that version, the docs page and the article
Validation
- bin/majordomus plan validate
Evidence required
- released_and_deployed
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/I2407.yaml. Read it back with majordomus plan show I2407.