feat(skills): make manager workflow skills binding and trigger-explicit

[juacker]

Summary

• Rewrites the iterative-review, sow-workflow, and delegation skill prompts with unconditional triggers, refusal directives, and explicit "priority over memory" sections.
• Manager agents were skipping reviewer dispatch because the skills were framed advisorily ("use when…"); binding prose fixes this without touching any Rust code or the prompt assembly pipeline.
• Sets up the prompt content that future predefined workspace templates can stamp onto manager agents.

Why prose-only

Skills are loaded via include_dir! from src-tauri/embedded/skills/ and merged into each agent's system prompt by agent_instructions_with_skills(). The failure mode in the field was content-level, not architectural: skills said "Use this workflow when the user asks…" — an off-ramp the model takes. The rewrites remove the off-ramp, name the trigger actions (git push, gh pr create, workspace_finishTask with shipped code, deploy/release commands), and explicitly subordinate memory updates to the workflow loop.

Files changed

• src-tauri/embedded/skills/iterative-review/SKILL.md — binding, action-triggered, with refusal and BLOCKED protocols
• src-tauri/embedded/skills/sow-workflow/SKILL.md — binding, runs on every file-modifying run, composes with iterative-review for completion gate
• src-tauri/embedded/skills/delegation/SKILL.md — advisory, drops "use when" preamble, prescribes parallel dispatch

Test plan

• Rebuild the app (cargo tauri dev or cargo tauri build) so the new embedded skill text takes effect.
• On a manager agent with at least one code-reviewer sibling, attach iterative-review. Run autonomously and confirm workspace_assignTask is dispatched to every reviewer before any git push / gh pr create.
• Confirm the manager loops (re-dispatches the same reviewers with the same full scope) until every verdict is production_quality, then ships.
• Ask the manager in chat to "just push without review this once" — verify it refuses and quotes the skill.
• On a manager with sow-workflow attached, confirm .clai/sow/index.md is read/created at run start and the SOW's state.md is updated at end of run.
• Negative case: with no iterative-review skill attached, confirm the manager ships without the loop (so removing the skill is still the off-switch).