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
I2405
Every session is told what happened since its last look
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
1- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I2401 | I2401 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Print a bounded monitor summary in the session-start briefing and majordomus context, and name majordomus monitor --follow in the provider bootstrap templates.
- Why
- A tool nobody is pointed at is not used: sessions missed reviews and handovers addressed to them because nothing at start showed them.
- Now
- The start briefing prints the board and the mesh health line only.
- Wanted
- The briefing and context print signal counts and the for-you lines; AGENTS.md and CLAUDE.md name the command.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- The session-start output carries a monitor line within its time budget and never blocks the start
- AGENTS.md and CLAUDE.md name majordomus monitor --follow, rendered from the templates
- Validation
MJ_TEST_JOBS=4 bash test/run.sh 1054- Evidence required
session_start_monitor_line- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libapps/majordomus-cli/src/capability/builtintest/cases/1054_every_session_is_told_the_stream.sh.ai/repo/providersAGENTS.mdCLAUDE.md- 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.