Skills trees have pre-existing drift: afx/porch differ repo-vs-skeleton; forge, skill-creator, team absent from the skeleton entirely

[waleedkadous]

Problem (found during project 1280's plan phase, deliberately kept out of its scope)

Skills exist in four trees — .claude/skills (10), .codex/skills (10, byte-identical to .claude), and the two codev-skeleton copies (7 each) — and the trees have drifted:

1. Content drift: the afx and porch skills differ between the repo copies and the skeleton copies.
2. Skeleton absence: forge, skill-creator, and team exist in the repo trees but not in the skeleton at all — adopters never receive them.

Why it's not part of #1280

Project 1280 (prompt-surface rewrite) relocates content INTO skills and now enforces four-tree parity for every skill it touches (its T17). The pre-existing drift on skills it does NOT touch, and the product question of whether forge/skill-creator/team should ship to adopters, are separate concerns with their own review needs — recorded there as known state, ruled out of scope by the architect at plan-approval.

Asks

1. Reconcile afx and porch skill content across all four trees (decide which side is current first — the drift direction hasn't been audited).
2. Product decision: should forge, skill-creator, team ship in the skeleton? Each yes means adding to both skeleton trees; each no deserves a recorded reason so the absence stops looking like an oversight.
3. A parity check (codev doctor or CI) across the four trees so drift is detected rather than discovered — same spirit as the template-reachability test from [Bugfix #1279] Deliver every protocol template via a {{> }} include, and enforce it #1283 and 1280's T17, generalized to all skills.