I2402 — majordomus monitor follows the stream from a terminal and a script

○READY wave 2 · p1 · implementation profile · runs alone

Part of everything-is-followed-in-one-stream — Everything that happens in the repository is followed in one stream.

Objective

Add majordomus monitor with --follow, --for, --sources, --since, --count, --until and --format text|json|ndjson, rendering one line per signal with its source tag.

Why

The person and every agent need one command to follow the repository live and a way for a script to wait for one event and exit, instead of hand-rolled jq loops.

Current state

No command.

Desired state

majordomus monitor prints a page; --follow streams it; --count and --until terminate.

Scope

• apps/majordomus-cli/src/commands
• apps/majordomus-cli/src/cli
• test/cases/1050_the_monitor_folds_the_noise.sh
• test/cases/1051_a_followed_stream_can_be_waited_on.sh

Dependencies

• I2401✓DONE monitor is one read capability with three projections

What waits on this

• I2406✕BLOCKED The stream is documented where a reader looks
• I2407✕BLOCKED The monitor is released and deployed

Acceptance criteria

• One page prints one line per signal and the suppressed count
• --follow --count N exits after N signals
• --format ndjson prints one JSON document per line

Validation

• MJ_TEST_JOBS=4 bash test/run.sh 1050 1051

Evidence required

• monitor_cli_cases

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/I2402.yaml. Read it back with majordomus plan show I2402.