feat(implementing-tickets): the skill IS the implement-worker protocol — bootstrap spawn, operation manual

[SSFSKIM]

Restructures skills/implementing-tickets so the skill IS the Implement Worker Protocol, mirroring the reviewing-prs shape from PR #14: in a pipeline with no orchestrator, the skill file is the worker's constitution, not a central session's operation manual. Work item 2 of the 2026-07-17 roadmap (work item 1, the clodex migration, merged as PR #17).

ExecPlan (grill-approved, executed autonomously): docs/doperpowers/execplans/2026-07-18-implementing-tickets-worker-protocol.md.

What changed

• skills/implementing-tickets/SKILL.md is now the Implement Worker Protocol itself — the old references/implement-worker-protocol.md body carried over clause-for-clause (verified against git history by an independent reviewer; zero semantic drift beyond two documented "brief rides the prompt as bindings" wording changes), with an operator-routing line up top and ## section headers.
• The old operator-facing SKILL.md content moved to references/operation-manual.md.
• New references/worker-bootstrap.md: one parameterized spawn bootstrap for BOTH lanes ({{ROLE}} IMPLEMENT/SPIKE, {{PROTOCOL_FILE}} = dispatcher-owned absolute path of the lane's protocol, runtime bindings, and EXECUTION_BLOCK / ISSUE_BODY / REPO_FACTS binding sections). Rendered spawn prompts drop from ~10.6k to ~4.1k characters.
• skills/issue-tracker/SKILL.md dispatch ritual renders the bootstrap; its "Worker protocols" section now describes both loops as skill-file protocols with bootstrap spawn.
• skills/reviewing-prs/scripts/review-dispatch.sh binds IMPLEMENT_PROTOCOL_FILE to the implementing-tickets SKILL.md (one line; test updated).
• The spike protocol sheds its raw-token brief tail and adopts the same bindings language (exit-review finding — a worker opening the file raw would have seen a "brief" heading holding unrendered tokens).
• tests/implementing-tickets/test-protocol-content.sh: protocol assertions retargeted to SKILL.md with every pre-existing clause assertion unchanged; exact placeholder sets pinned for protocol/spike/bootstrap; new operation-manual and bootstrap assertions.

Validation evidence

• Hermetic: all seven suites green (protocol content, daemon, codex-legacy, board, codex-plugin sync, review-dispatch, land-dispatch), RED shown before each milestone's edits; shell lint and git diff --check clean. One transient cross-suite flake in the back-to-back sweep loop reproduced the same environment-interference pattern seen on the prior branch and passed standalone repeatedly (recorded in the ExecPlan).
• Live shakedown (scratch board): a bootstrap-dispatched gateway worker opened the dispatcher-owned SKILL.md (the exact path self-recorded in its PR's Validation Evidence), gate-PASSED as its first board write ([gate] pass — codex/DIRECT — the pass branch, complementing PR feat: migrate implement/spike/land workers to the clodex gateway route (one worker species) #17's park-branch shakedown), built test-first, stayed on the gateway (echo "${ANTHROPIC_BASE_URL:-unset}" → http://localhost:8317), and closed with Closes #1 + full closing artifact.
• Exit reviews: codex native review was unavailable (two fresh-clone runs died on upstream "model at capacity"; recorded in the Decision Log) — the execplan track's documented fallback applied: an independent fresh-context Claude reviewer verified the full diff (clause-by-clause move fidelity against git history, byte-identity constraints, placeholder consistency across ritual/bootstrap/protocols for both lanes, suites) and returned Ready; its one P3 was fixed and delta re-verified by the same reviewer.

Out of scope (deliberate)

The plugin release carrying both roadmap items to consumers (once, after this merges); the legacy codex machinery deletion follow-up from PR #17.

Authored and executed by Claude Fable 5 (claude-fable-5) on Claude Code with the doperpowers plugin, from a human-approved brainstorming grill; the human partner reviews this PR.