councilroot.py resolves one durable council root for every script and migrates the old /tmp root under the held locks: a preflight conflict moves nothing, each legacy file is renamed to a staging name before it is copied so a late writer is merged by the catch-up, id-less journals merge by line multiset, a differing whole file is kept beside its namesake, and a crash marker makes install copy the skills and report. One settings-file list, managed drop-ins included, serves councilroot.py and queue.py. Tests run once on unify/skills-20261114 after the merge (operator order 2026-11-14).
🎯 Fix: 88 %
💥 Break: 7 %
💸 Tokens: 100 %
⏱️ Velocity: 100 %
🛡️ Security: 100 %
🏆 Score: 82
🚦 Gate: ⛔ fix 88 % < 90, break 7 % > 5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Requirement 006 grew SKILL.md to 853 words, over the 600-word cap test_lock enforces. The tables and message block details move to tables.md and the score journal with its backfill to journal.md; SKILL.md keeps the commit-block rule and points to both. The journal reader set in test_score_journal follows the text to journal.md.
🎯 Fix: 95 %
💥 Break: 2 %
💸 Cost: 110 %
⏱️ Time: –
🛡️ Security: ~100 %
🏆 Score: 85
🚦 Gate: ⚠️ cost 110 % > 100: ask the operator before the commit
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
006's label test scanned docs/requirements too, but the 006 requirement has to name Cost and Time to describe their rename, so the test failed once the requirement and the code met on the unify branch. The test now skips docs/requirements, and the 006 acceptance line says so.
🎯 Fix: 96 %
💥 Break: 1 %
💸 Cost: 100 %
⏱️ Time: 100 %
🛡️ Security: 100 %
🏆 Score: 95
🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 %
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
score.py names the Cost and Time metrics Tokens and Velocity from one label file and appends every scored block to a score journal in the council root. backfill.py rebuilds that journal from commit messages with its own label mapping, deterministic and idempotent, so another host can import its history. The hub serves the journal, and the Gantt burndown draws each metric as its own overlay on a right 0-100 % axis, every overlay off by default and switched by legend chips whose state the view store keeps.
🎯 Fix: 90 %
💥 Break: 5 %
💸 Cost: 100 %
⏱️ Time: 100 %
🛡️ Security: 100 %
🏆 Score: 86
🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 %
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>