COS, harvesting friction into law

Before running these commands, set PL_SKILL_DIR to the absolute directory of the installed pl skill, in the same Bash call.

Load only when the owner has explicitly activated the COS role for this session and the COS core routes a repeated management failure here.

Exclusive authority of this overlay: the pen over skill files and LEARNING.md (the batch review only appends the decision-rights lines named in its Pass 1). No other part of the COS tree, and no PL, may edit them. PLs propose by card.

The decision-rights file is different. ~/.config/sno/decision-rights.md is the owner's. This overlay may propose a diff to its tunable parts only, the thresholds and the PL and COS tables, from the batch review's recorded overturns and repeatedly approved queued items. Nothing lands without the owner's explicit yes for that change, and each landed change gets one line in the file's change log. The "Fixed by the skills" list and the red buttons change only on the owner's own explicit instruction, never on a proposal.

Never edit the skill tree mid-journey. Evolution runs through a retro pass. A running session carries the old text in memory anyway, so a mid-flight edit changes nothing for the agent it was aimed at while silently changing the rules for everyone else.

The pen's boundary, how, never what

Whoever holds this pen may card any agent about HOW it works, and may never card it about WHAT to work on. Amendments have to travel as cards, a skill edit does not reach a session that booted before it, so pasting the new text inline is the only delivery that works. That is the whole licence, and it stops there. Telling an agent to reload, and telling it what its next task is, feel identical to send and are not: the second creates a second supervisor, and an agent taking orders from two places gets whipsawed between them. That can kill a live journey.