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

I0840

context and its subcommands under a second

Where it stands

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

majordomus plan verify I0840

majordomus plan done I0840

What it is

Objective
Time context resolve, validate, affected and check-sync, and remove the per-document git and awk calls so each runs under a second on this repository.
Why
context is what every session runs first, and resolve is what every worker runs before touching a path.
Now
Each takes about one second, dominated by per-document git ls-files.
Wanted
One git ls-files per invocation, one flatten per document, output unchanged.
Done when
unknown: the record declares no `completion`
Risk
The tracked-only rule must survive: one ls-files listing is filtered per document instead of asked per document.

Acceptance

  • Cases 23, 69, 70 and 71 pass unchanged
  • git count for context validate is at most two
Validation
MJ_TIMING=1 bin/majordomus context validate
Evidence required
batch_reads
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
lib/context_docs.shlib/context.shtest/cases/69_context_documents.shtest/cases/70_context_impact.shtest/cases/71_context_sync.sh
Not
none
Depends on
I0820I0821
Priority
p0
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-09-05
Updated
2026-09-05
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.