R76.H3 Heritage Tagging — Execution Packet

Round: R76 (Phase 0 → 1 bridge) Task: R76.H3 — inline Phase 0 reality stamps on 4 active skills Branch: feature/r76-h3-heritage-tagging Date: 2026-04-19

1. Target files

1. .agents/skills/colibri-tier1-chains/SKILL.md
2. .agents/skills/colibri-mcp-server/SKILL.md
3. .agents/skills/colibri-docs-check/SKILL.md
4. .agents/skills/colibri-growth-strategy/SKILL.md

Tool: Edit (not Write) on each file. All 4 are live active skills, not HERITAGE.

2. Edit-by-edit plan

2.1. colibri-tier1-chains/SKILL.md — 5 edits

#	Location	Action
1	Line 11 (existing reality-stamp paragraph, ending with “…no router_* MCP tools).”)	Append R76.H3 marker line inside the existing callout (new sentence)
2	Line 13 body paragraph listing unified_*, gsd_*, roadmap_*, analysis_*, memory_*, context_*, observe_*	Append > **Phase 0 note:** callout after the paragraph
3	Line 62 context_create, analysis_rag_search	Inline strike on each name
4	Line 79 task_eisenhower, analysis_recommend, gsd_plan, task_depends_on	Inline strike on each name
5	Line 98 gsd_validate	Inline strike
6	Line 217 gsd_agent_spawn	Inline strike
7	Heading “Donor references — do not use” (around line 230)	Insert single > **Phase 0 note:** callout directly under the heading, covering the entire unified_*, gsd_*, roadmap_*, analysis_*, memory_*, context_*, donor task_* name bullets

Rationale: 25+ specific tool names appear on lines 234–239. Striking each would generate ~25 ~~...~~ wrappers in a 6-line bullet block — unreadable. The heading “Donor references — do not use” already telegraphs intent; one callout right beneath it, plus a short sentence at the top of the bullet block, cleanly stamps the whole section.

2.2. colibri-mcp-server/SKILL.md — 3 edits

#	Location	Action
1	§1 (line 13 reality stamp)	Append R76.H3 marker line (new sentence)
2	Line 32 §2 scope bullet gsd_*, ams_autonomous_*, roadmap_*, workflow_*, analysis_rag_*, memory_pack, memory_bundle, observe_*, watcher_*, unified_*	Append > **Phase 0 note:** callout after the bullet
3	Line 138 §9 “Tool not found” paragraph gsd_*, ams_*, roadmap_*, analysis_rag_*, unified_*, workflow_*	Append > **Phase 0 note:** callout after the paragraph

Rationale: both lines are bullet / paragraph forms packed with 6–10 wildcards + specific names. A single adjacent callout per location is cleanest.

2.3. colibri-docs-check/SKILL.md — 2 edits

#	Location	Action
1	Line 11 (existing reality stamp)	Append R76.H3 marker line (new sentence)
2	Step 5 stale-donor-patterns table (around line 100)	Append > **Phase 0 note:** callout directly after the table closer

Rationale: line 100 is a table row with 7 family wildcards. A callout immediately below the closing row of the table stamps every wildcard at once.

2.4. colibri-growth-strategy/SKILL.md — 5 edits

#	Location	Action
1	Line 10 existing “Phase 0 note” top paragraph	Append R76.H3 marker line at end of the paragraph, plus inline strikes on each specific donor tool name inside it (task_create_batch, task_link_roadmap, task_deps)
2	Line 10 family wildcards (unified_*, roadmap_*, analysis_*)	Leave as-is inside the paragraph — the paragraph is already the reality-stamp; the R76.H3 marker appended after covers the wildcards
3	Line 67 unified_set_project	Inline strike
4	Line 175 task_link_roadmap, roadmap_nodes	Inline strike on each name
5	Line 211 roadmap_nodes	Inline strike

Rationale: line 10 is itself a Phase 0 note paragraph — adding a second callout after it would double-stamp. Inline strikes on the specific names inside the paragraph + a single R76.H3 marker sentence appended to the end is the correct treatment per §2.1 rule 4 in the contract.

3. Format reference (copy-paste templates)

3.1. Inline strike template

~~`<tool_name>`~~ <sup>(Phase 0: deferred to Phase 1.5+ per ADR-005; not in the 14-tool surface)</sup>

3.2. Phase 0 note callout template

> **Phase 0 note:** The `gsd_*`, `unified_*`, `roadmap_*`, `memory_*`, `context_*`, `analysis_*`, `observe_*`, and `watcher_*` families are donor-era and not in the Phase 0 14-tool surface — see [ADR-004 R75 Wave H amendment](../../../docs/architecture/decisions/ADR-004-tool-surface.md).

3.3. Top-of-file R76.H3 marker template

> **Post-Phase-0 reality stamp (2026-04-19, R76.H3).** Some tool names below mark donor-era deferred capabilities; the Phase 0 shipped 14-tool surface is authoritative — see [ADR-004](../../../docs/architecture/decisions/ADR-004-tool-surface.md).

4. Verification plan

1. Re-grep each of the 4 files for (gsd|unified|roadmap|memory|context|analysis|observe|watcher|workflow)_ family names. Every hit must either be inside ~~ OR inside / immediately adjacent to a > **Phase 0 note:** block.
2. Check each file has the R76.H3 marker line (grep R76.H3).
3. git status shows zero files changed under .claude/skills/.
4. Run npm run build && npm run lint && npm test in the worktree.

5. Commit

Single commit covering the 4 edits + 4 chain docs. Message template is in the R76.H3 dispatch prompt.

6. Counts (expected totals)

• colibri-tier1-chains: 6 inline strikes + 3 callouts (1 after line 13, 1 after donor-ref heading, 1 at ADR-stamp marker) + 1 top-of-file marker append
• colibri-mcp-server: 0 inline strikes + 2 callouts + 1 top-of-file marker
• colibri-docs-check: 0 inline strikes + 1 callout + 1 top-of-file marker
• colibri-growth-strategy: 6 inline strikes + 0 additional callouts (line 10 is already the callout) + 1 top-of-file marker sentence in line 10

Total: 12 inline strikes, 6 callouts, 4 top-of-file markers across the 4 skills.

---

R76.H3 packet — concrete edit plan. Upstream: audit + contract. Downstream: implement → verify.