[T-Crypt]

A router can now hand each stage the skills its job needs at spawn time. Until now a stage got only what its agent definition or router stage named in advance, so a UI refresh ran without the UI skill unless the role always carried it.

What changed

• subagent spawn takes skills: [...]: up to four installed skills, by name. The subagent reads each in full before it starts, after the skills its definition or stage already names.
• A name that is not installed, or a fifth skill, fails the call before anything starts. The router fixes the list and spawns again.
• skillsToRead in routers.ts builds the "read these first" lines for editor-router stages and for spawn skills, so a stage sees the same instruction whichever asked for it.
• docs/features.md and the README list the new option.

Proof

• npm run check: clean.
• npm test: 644 of 644 pass.
• npm run format:check: clean.
• The new test in test/routers.test.ts fails with the src/ change reverted and passes with it.

Why

The homelab hq router picks skills per stage from a table (UI work gets ui-ux-pro-max in plan, frontend-design and web-shot in implement). Without this option it could only write a Skills: line in the brief and hope a low-thinking stage opened them.