Packet — R77.C .claude/skills/ mirror resync

Round: R77 · Task: R77.C · Tier: T3 Base: origin/main @ ea5055e0 · Date: 2026-04-18 Audit: docs/audits/r77-c-mirror-resync-audit.md Contract: docs/contracts/r77-c-mirror-resync-contract.md

1. Execution plan (one commit, three file overwrites)

R77.C is a single logical change. Because every mirror tree structurally matches its canon tree (audit §3, contract §4), the implementation collapses to three file overwrites — one SKILL.md per skill — and nothing else.

All non-SKILL.md files under each mirror tree (agents/openai.yaml, references/*.md, scripts/setup-claude.ps1) are already byte-identical to canon and will not be touched.

2. Operations

Execute from the worktree root E:/AMS/.worktrees/claude/r77-c-mirror-resync/.

2.1. Op-1 — resync colibri-mcp-server/SKILL.md

Overwrite .claude/skills/colibri-mcp-server/SKILL.md with the content of .agents/skills/colibri-mcp-server/SKILL.md (182 lines, canon).

Mechanism: Read canon then Write mirror with the exact same byte stream. (Preferred over shell cp on Windows to guarantee line-ending preservation.)

2.2. Op-2 — resync colibri-tier1-chains/SKILL.md

Overwrite .claude/skills/colibri-tier1-chains/SKILL.md with the content of .agents/skills/colibri-tier1-chains/SKILL.md (262 lines, canon).

Mechanism: identical to Op-1.

2.3. Op-3 — resync colibri-growth-strategy/SKILL.md

Overwrite .claude/skills/colibri-growth-strategy/SKILL.md with the content of .agents/skills/colibri-growth-strategy/SKILL.md (221 lines, canon).

Mechanism: identical to Op-1.

3. No-touch list (must remain unchanged)

Anything under .agents/ — canon is read-only in this task.
.claude/skills/colibri-mcp-server/agents/openai.yaml — already identical.
.claude/skills/colibri-mcp-server/references/errors.md — already identical.
.claude/skills/colibri-mcp-server/references/tools.md — already identical.
.claude/skills/colibri-mcp-server/references/workflow.md — already identical.
.claude/skills/colibri-mcp-server/scripts/setup-claude.ps1 — already identical.
.claude/skills/colibri-tier1-chains/agents/openai.yaml — already identical.
.claude/skills/colibri-growth-strategy/agents/openai.yaml — already identical.
Everything under src/ — R77 ships no src/ code.
Every other .claude/skills/colibri-* tree not listed in §2.
.claude/settings.local.json — pre-existing drift unrelated to this task.

4. Post-op verification (during Step 5)

4.1. Byte-diff check

for skill in colibri-mcp-server colibri-tier1-chains colibri-growth-strategy; do
  diff -qr ".agents/skills/$skill" ".claude/skills/$skill"
done

Expected output: empty (three silent passes).

4.2. Git scope check

git diff origin/main --name-only

Expected output: exactly the audit/contract/packet/verification docs plus the three SKILL.md files:

.claude/skills/colibri-growth-strategy/SKILL.md
.claude/skills/colibri-mcp-server/SKILL.md
.claude/skills/colibri-tier1-chains/SKILL.md
docs/audits/r77-c-mirror-resync-audit.md
docs/contracts/r77-c-mirror-resync-contract.md
docs/packets/r77-c-mirror-resync-packet.md
docs/verification/r77-c-mirror-resync-verification.md

(Commit SHAs for the 5-step chain are expected but listed separately.)

4.3. Build/lint/test gates

npm run build
npm run lint
npm test

All three must exit 0. Test count target: 1085/1085 passing (matches main at ea5055e0).

5. Commit plan

One implementation commit after Ops 1/2/3:

chore(r77-c-mirror-resync): resync 3 skills from .agents/ canon to .claude/ mirror

Followed by the verification commit (Step 5 of the chain):

verify(r77-c-mirror-resync): diff-clean evidence

6. Rollback plan

If any of the byte-diff checks fail post-resync:

git checkout origin/main -- .claude/skills/colibri-mcp-server/SKILL.md \
                            .claude/skills/colibri-tier1-chains/SKILL.md \
                            .claude/skills/colibri-growth-strategy/SKILL.md

This restores the pre-resync mirror state without touching canon, docs, or the 5-step commits.

If build/lint/test fail: this is extremely unlikely given the doc-only scope (no src/ change, no MCP registration change), but the same rollback applies and the branch can be abandoned without affecting main.

7. Gate — ready for Step 4

All audit §scope, contract §acceptance-criteria, and packet §operations are internally consistent. The operation is minimal, idempotent, and has a cheap rollback. Proceed to Step 4 (Implement).