Runs

Where agenda-creation and agenda-status test runs write. In the project folder, committed.

How does a run use it?

One folder per run, named for what it was testing.

mkdir -p docs/projects/agent-workflow-hierarchy/runs/<label>
cp docs/projects/agent-workflow-hierarchy/fixtures/agenda/*.md \
   docs/projects/agent-workflow-hierarchy/runs/<label>/

args: repoRoot   = <your checkout>
      agendaDir  = <your checkout>/docs/projects/agent-workflow-hierarchy/runs/<label>
      focus      = <whatever you are calibrating against>
      trigger    = operator-status-request   (agenda-status only)

A run folder holds both its copied inputs and its output, and that is correct. An agenda directory is a directory of dated files where today's file is written beside the last few days, so a run folder IS an agenda directory.

Copy out of fixtures/, never write into it. That folder is the canonical input set. Output landing there means the next run finds today's file already present and appends to the previous run's output instead of creating a fresh one, which is exactly what happened once already.

What is kept here?

Runs worth reading again. Delete the rest: a folder nobody prunes stops being a record and becomes noise.

Folder	Run	What it shows
2026-08-22-format-after/	wf_af98c56f-14e	The current format. PDT read from the clock, checkbox focus blocks, bold log titles, one-line Context fields, four-line prompts, and Cut Today and Gaps with their emoji
2026-08-22-format-before/	wf_fe55300a-565	The same job one run earlier. PST stamped on an August date, and Cut today / Gaps as bare headings, because the format had not defined them yet

The content is invented. The tasks come from the mock fixture days plus the real launch plan, so no work item here is real. What is real is the shape.

The scenarios these runs filled are in testing.md.