sage: window carry step for any pin past row 64, install and activate the seven role skills from the pinned copy (mos-0863 D3, #1557)

2026-10-19 16:18:46 -05:00
parent ebfc23c431
commit 46de608936
1 changed files with 51 additions and 0 deletions
@@ -0,0 +1,51 @@
+# Carry step for any window whose pinned tree includes row 64
+
+Sage, 2026-10-19, on Mos's ruling mos-0863 D3. There is no window plan template, and no plan yet pins a tree
+with row 64 (Window A pins 5fa9cc8f2 and Window B pins ca15d73e9, both before it). So this file holds the step,
+and the first plan whose pinned tree includes the row 64 landing copies it in. Windows A and B stay as they are.
+
+## Why
+
+From row 64 on, `packages/cli/src/launcher.mjs` reads each skill a role lists from `<dataRoot>/skills-enabled`
+before anything starts, and refuses `skill-not-enabled` when one is missing (Darkwing N5, #1557 comment 29219).
+The lists are in `roles/*.json`: coder ms-unslop, ms-sdlc, ms-file-read, ms-file-write; reviewer ms-unslop,
+ms-sdlc, ms-file-read; cto ms-unslop, ms-sdlc, ms-archify, ms-grill-me; pm ms-unslop, ms-goal,
+ms-communications. The chief lists none. The live data root has only ms-communications enabled and only
+ms-tools available (mos-0863 F2). Without this step, every coder, reviewer, cto and pm start refuses after the
+re-pin.
+
+## The step (before the first role start on the new pin)
+
+Run from the pinned copy, so the skill bytes come from that copy's `skills/` directory (mos-0863 F3). The seven
+skills not yet enabled:
+
+```
+cd <copies>/<pinned sha>
+for s in ms-unslop ms-sdlc ms-file-read ms-file-write ms-archify ms-grill-me ms-goal; do
+  scripts/skill.sh install "$s" && scripts/skill.sh activate "$s" || { echo "STOP skill $s"; break; }
+done
+scripts/skill.sh list
+```
+
+The check: `list` shows all eight under `enabled:` (the seven plus ms-communications), and ms-tools stays under
+`available:`. Before running, the plan re-reads the role lists at the pinned sha (`git show <sha>:roles/<r>.json`)
+and updates the seven if they changed.
+
+## Rollback
+
+Deactivate and uninstall the same seven, in that order, then `scripts/skill.sh list` shows ms-communications
+alone under `enabled:` again:
+
+```
+for s in ms-unslop ms-sdlc ms-file-read ms-file-write ms-archify ms-grill-me ms-goal; do
+  scripts/skill.sh deactivate "$s" && scripts/skill.sh uninstall "$s"
+done
+```
+
+A rollback to a pin before row 64 doesn't need this, since that launcher doesn't read skills, but the plan
+runs it so the data root matches the pin.
+
+## The window's checks add
+
+One start of a role that lists skills (sage-1064 R4, mos-0863 D3), for example one short coder session, and the
+run's bundle `manifest.json` showing the role's skills with their sha256 values. A refusal here is a stop.