Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2407

The monitor is released and deployed

Where it stands

devtask.issue
Readiness
blocked 4 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
everything-is-followed-in-one-stream
Milestone status
ACTIVE
Wave
4
Waiting on
I2402I2404I2405I2406
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI2402I2402 is not DONE
issueI2404I2404 is not DONE
issueI2405I2405 is not DONE
issueI2406I2406 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2407

majordomus plan verify I2407

majordomus plan done I2407

What it is

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.
Now
0.20.0 is released without it.
Wanted
The next minor release carries majordomus monitor and the site serves its docs and article.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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 present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/Cargo.tomlCHANGELOG.md
Not
unknown: the record declares no `non_scope`
Depends on
I2402I2404I2405I2406
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-10
Updated
2026-10-10
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.