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

I0836

A synthetic repository generator for scaling cases

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
2
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
1 of 1
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 I0836

majordomus plan verify I0836

majordomus plan done I0836

What it is

Objective
Add a test helper that builds a repository with N issues, N milestones, N rules and N context documents from the skeleton, and a case that runs doctor and plan validate at three sizes and asserts the yaml_flatten count grows linearly.
Why
Quadratic behaviour hides in small repositories; the counters expose it before wall clock does.
Now
Fixtures are hand-built per case.
Wanted
One generator in test/lib.sh, one scaling case, counters linear in N.
Done when
unknown: the record declares no `completion`
Risk
The generated records must pass plan validate; the helper builds them from the same templates the skeleton ships.

Acceptance

  • Counters at N, 2N and 4N are within a linear bound
  • The generator is reused by at least one other case
Validation
bash test/run.sh 3053_a_repository_of_n_records_costs_n
Evidence required
batch_reads
Evidence present
batch_reads

Scope

Touches
test/lib.shtest/cases
Not
Wall-clock assertions in the scaling case
Depends on
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-10-15T07:36:57Z
Started
2026-10-15T07:36:51Z
Verified
unknown: the record declares no `verified_at`
Completed
2026-10-15T07:36:57Z

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.