Run the ticket skills through T3 Code, with a review council before pre-mr-review

Agents now start pre-mr-review on the work account themselves, through a Klaude
delegate, and continue from its verdict. A council of models on my own accounts
replaces the single reviewer before it, and adding a seat is one table row.

Proof comes from T3's browser, with mp4 recordings, and capture-proof stays as
the fallback. Ticket pages carry their own data, so index.html renders alone in
T3's file viewer, and worktree threads share the main checkout's docs.

A PreToolUse hook sends subagents in T3 threads to delegate_task. Blocker, proof,
review and MR summary rules come from ideas in t3dotgg/tstack.

user/agents/skills/create-ticket/SKILL.md

@@ -90,6 +90,9 @@ Same conventions as the `/ticket` skill:
    `.claude/docs/epics/<EPIC-KEY>/<TICKET-KEY>/story.md` (or `spike.md` /
    `task.md`), creating directories as needed. These are personal docs, never
    committed.
+9. **Report.** Give the Jira link, the title, and any numbered Notes that still name an
+   open owner, and link the local copy by absolute path so it opens rendered in T3's
+   file viewer.
 
 ## House rules for all content