jared
04a5ee958b
Journal entry for the roborev triage session and a regenerated status board. Adds AGENTS.md and .roborev.toml to the packaging workstream so root-level config commits attribute to a stream instead of landing unreferenced.
1.5 KiB
Project journal
Append-only, newest first. Entries are never edited — the value of this file is
that it records what was believed at the time, including the parts that turned out
wrong. Where things stand today is in STATUS.md, which is generated.
Four lines per entry. The analysis belongs in the issue or the decision record; this file carries the reasoning and the pointers.
- Why — the driver. The one line git cannot reconstruct later.
- Obligates — issues this change created elsewhere. Numbers, not prose.
- Refs — commits, issues, decision records.
2026-08-24 · packaging · roborev exclusion patterns fixed; init review triaged
Why: roborev reviewed the init commit because excluded_commit_patterns are
substring matches and chore: never matches the chore(packaging): form the
cadence rule mandates — the commit convention was silently defeating its own
review filter. Two low findings came back; one was half-right, one rested on a
generator it could not see.
Obligates: —
Refs: cd1af67, roborev job 15
2026-08-23 · packaging · compass initialised, five workstreams defined
Why: the package had no tracking at all — one open issue, a NEWS changelog, and
no record of why anything was decided. Workstream boundaries follow how the code
actually goes stale, not the directory listing: colors stay with theme because the
scales are consumed by the themes, and packaging is its own stream so CI and
dependency drift file against something.
Obligates: #21, #22
Refs: 7cad98b, #20