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

I2404

The Cockpit shows the stream live

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
2
Waiting on
Holds back
Behind it in all
2
Evidence
0 of 1
In the waySubjectDetail
issueI2401I2401 is not DONE
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 I2404

majordomus plan verify I2404

majordomus plan done I2404

What it is

Objective
Add /cockpit/monitor: the live feed polling the HTTP projection with its cursor, source filters, for-you pinned, the suppressed count, linked from the home and mesh pages.
Why
The owner follows the repository in a browser as often as in a terminal; the Cockpit has no page that shows what is happening now.
Now
No page.
Wanted
/cockpit/monitor renders the first page server-side and appends new signals live.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • The page renders with the first page of signals and a cursor
  • The home page and the mesh page link it
  • It works at phone width
Validation
MJ_TEST_JOBS=4 bash test/run.sh 1053
Evidence required
cockpit_monitor_page
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/cockpittest/cases/1053_the_cockpit_follows_the_stream.sh
Not
unknown: the record declares no `non_scope`
Depends on
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.