Files
computer-playbook/cli/build
kevinveenbirkenbachandClaude Opus 5.5 8215beabad perf(i18n): save the catalogue every 100 entries
one_catalog writes a catalogue back after every chunk. At about 0.34 s per entry a chunk of 500 held some three minutes of work in memory, and every interrupted run (a full disk, a pause for a quality gate) lost it. A chunk of 100 caps that at about half a minute per catalogue; the gateway batches stay at 20, and write_catalog stages and renames, so a write that fails leaves the previous catalogue intact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 10:38:47 +01:00
..
…

Build 🏗️

Build-time generators that materialise role include lists, dependency graphs, tree visualisations, and documentation pages from the role metadata in roles/. Nothing here talks to a running deployment; every command reads the repository and writes an artefact back into it.