Merge step (i): reference sweep — fix stray old-convention refs

Applies triage doc 022. Most of the sweep was no-op because upstream already
renamed everything in place when we branched from origin/main. Remaining
fixes:

- ce-pr-comments-review/SKILL.md: replace compound-engineering:review:/
  workflow: prefixed agent refs with bare ce-<name> form (self-correction
  from step g where I accidentally used old convention)
- ce-essay-edit/SKILL.md: update /essay-outline reference to /ce-essay-outline

Prose references to generic words ("onboarding", "changelog") are left
alone — they are natural-language uses, not skill references.

Known follow-up: tests/review-skill-contract.test.ts and
tests/legacy-cleanup.test.ts still reference locally-removed agents
(ce-dhh-rails-reviewer, ce-kieran-rails-reviewer, ce-data-migration-expert,
ce-security-sentinel). These will need test updates + registration of
removed names in src/utils/legacy-cleanup.ts and
src/data/plugin-legacy-artifacts.ts — flagged for step (j).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

plugins/compound-engineering/skills/ce-essay-edit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ce-essay-edit
-description: Expert essay editor that polishes written work through granular line-level editing and structural review. Preserves the author's voice and intent — never softens or genericizes. Pairs with /essay-outline.
+description: Expert essay editor that polishes written work through granular line-level editing and structural review. Preserves the author's voice and intent — never softens or genericizes. Pairs with /ce-essay-outline.
 argument-hint: "[path to essay file, or paste the essay]"
 ---
 

plugins/compound-engineering/skills/ce-pr-comments-review/SKILL.md

@@ -53,7 +53,7 @@ Group comments by file + line + thread for context. Skip:
 For each remaining comment, dispatch a validator agent. In Claude Code:
 
 ```
-Agent(subagent_type: "compound-engineering:review:ce-zip-agent-validator",
+Agent(subagent_type: "ce-zip-agent-validator",
       description: "Validate PR comment",
       prompt: "<comment context + file + line + surrounding code>")
 ```
@@ -109,7 +109,7 @@ Order findings: `Clear & Correct` and `Likely Incorrect` first (they drive the b
 
 Apply decisions in parallel where possible.
 
-- **Fix now** → dispatch `compound-engineering:workflow:ce-pr-comment-resolver` per finding (or grouped set). Prefer parallel; fall back to sequential if dependencies exist. When the resolver is done, post a reply on the thread confirming the fix and include the commit SHA.
+- **Fix now** → dispatch `ce-pr-comment-resolver` per finding (or grouped set). Prefer parallel; fall back to sequential if dependencies exist. When the resolver is done, post a reply on the thread confirming the fix and include the commit SHA.
 - **Clarify** → post the clarifying reply on the thread via `gh api`. Do not mark the thread resolved.
 - **Push back** → post the disagreement (pulling the technical justification from the validator result) on the thread. Do not mark the thread resolved.
 - **Skip** → do nothing on the thread. Note the skip reason in the task summary.