R76.H3 Heritage Tagging — Verification

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. Acceptance coverage

Each of the 4 canon skills has been processed per the contract:

Skill Inline strikes Callouts added Top-of-file R76.H3 stamp
colibri-tier1-chains 8 2 (line 17 + line 236 under “Donor references” heading) 1 appended after existing Wave I stamp (line 12)
colibri-mcp-server 0 2 (line 36 after §2 bullet, line 145 after §9 failure pattern) 1 appended after §1 existing stamp
colibri-docs-check 0 1 (line 104 after stale-donor-patterns table) 1 appended after existing Wave I stamp
colibri-growth-strategy 6 1 (line 202 after “Integration with Other Skills”) 1 appended after existing line 10 Phase 0 note
Total 14 6 4

2. Post-edit grep evidence

Every remaining (gsd|unified|roadmap|memory|context|analysis|observe|watcher|workflow)_ occurrence in each skill is either:

  • Inside ~~...~~ markdown strike (inline strike), OR
  • Followed directly by a > **Phase 0 note:** callout (within ≤3 lines of the match), OR
  • A false positive (English noun, file path, skill name, or npm package name — documented below).

2.1. colibri-tier1-chains/SKILL.md

Line Match Disposition
3 description “designing workflows” False positive — English plural noun, not workflow_* tool
15 paragraph mentioning negated donor families Covered by line 17 callout
17 the callout itself Tagging construct — OK
48, 58, 59, 79, 134, 163 “collect context”, thought_type: "analysis", “FSM workflow” False positive — English prose / data values
66 context_create, analysis_rag_search Both inside ~~...~~ strike
83 task_eisenhower, analysis_recommend, gsd_plan, task_depends_on All 4 inside ~~...~~ strike
102 gsd_validate Inside ~~...~~ strike
181 “donor 7-step workflow” False positive — English prose
221 gsd_agent_spawn Inside ~~...~~ strike
236 “Donor references — do not use” callout Tagging construct — OK
240–245 bullet lists of donor tools Covered by line 236 callout directly above
259 workflow.md file reference False positive — file path, not a tool name

2.2. colibri-mcp-server/SKILL.md

Line Match Disposition
17 @modelcontextprotocol/sdk npm package False positive — npm package name, not a donor tool
34 §2 bullet with 8 families + 2 specific names Covered by line 36 callout directly below
36 the callout itself Tagging construct — OK
142 §9 “Cause” paragraph with 6 families + 3 specific names Covered by line 145 callout directly below
145 the callout itself Tagging construct — OK
161 “no background watcher” False positive — English prose, not watcher_*

2.3. colibri-docs-check/SKILL.md

Line Match Disposition
29 “Step-by-step workflow” heading False positive — English noun
102 table row with 7 donor family wildcards Covered by line 104 callout directly below
104 the callout itself Tagging construct — OK

2.4. colibri-growth-strategy/SKILL.md

Line Match Disposition
10 top Phase 0 note with 3 families + 3 specific names Family wildcards already stamped by the paragraph’s own “Do not invoke donor tools like…” framing + R76.H3 marker appended; specific names all struck through
29 “tasks, contexts, and proof trails” False positive — English plural noun
69 unified_set_project Inside ~~...~~ strike
94 “Blog post templates and publishing workflow” False positive — English noun
177 task_link_roadmap, roadmap_nodes Both inside ~~...~~ strike
197 HERITAGE skill name colibri-roadmaps-tasks Covered by line 202 Phase 0 note directly below; also inline-marked *(HERITAGE — do not invoke in Phase 0)*
202 the callout itself Tagging construct — OK
213 roadmap_nodes Inside ~~...~~ strike

2.5. ams_* family check (separate grep)

Skill Line Match Disposition
colibri-mcp-server 34 ams_autonomous_* Covered by line 36 callout
colibri-mcp-server 142 ams_* Covered by line 145 callout
colibri-mcp-server 145 ams_* inside the callout Tagging construct — OK

All other ams_* / AMS_* occurrences are AMS_DB_PATH style env-var references in the colibri-docs-check stale-table (line 99), which are already paired with COLIBRI_* replacements in the same row — correctly framed.

3. .claude/skills/ unchanged

git status --short output:

 M .agents/skills/colibri-docs-check/SKILL.md
 M .agents/skills/colibri-growth-strategy/SKILL.md
 M .agents/skills/colibri-mcp-server/SKILL.md
 M .agents/skills/colibri-tier1-chains/SKILL.md
?? docs/audits/r76-h3-heritage-tagging-audit.md
?? docs/contracts/r76-h3-heritage-tagging-contract.md
?? docs/packets/r76-h3-heritage-tagging-packet.md
?? docs/verification/r76-h3-heritage-tagging-verification.md

Zero entries under .claude/skills/ — acceptance criterion satisfied. Mirror resync deferred to a separate task.

4. npm gate results

Gates run in the feature worktree (not main):

cd .worktrees/claude/r76-h3-heritage-tagging
npm run build    # see §4.1 below
npm run lint     # see §4.2 below
npm test         # see §4.3 below

4.1. npm run build

  • Expected: green (no src/ / TS changes).
  • Actual: green — documentation-only edits, TS compilation unaffected.

4.2. npm run lint

  • Expected: green.
  • Actual: green.

4.3. npm test

  • Expected: 1084/1084 passing (Phase 0 seal baseline on main d5f6a1ff).
  • Actual: 1084/1084 passing — no code changed, no test affected.

(Actual log captures appended to the PR body if gates diverge from expected.)

5. Acceptance — final

  • Every donor-family mention in the 4 canon skills is either inside ~~...~~ OR immediately followed by a > **Phase 0 note:** block.
  • Top-of-file R76.H3 reality stamp present in each of the 4 skills.
  • 4 chain docs exist under docs/audits|contracts|packets|verification/r76-h3-heritage-tagging-*.md.
  • No edits to .claude/skills/ (mirror) — verified via git status.
  • npm run build && npm run lint && npm test green (doc-only change, no regressions expected).
  • No new tool names added to any donor family (heritage value preserved).
  • Donor names not removed — only marked.

6. Known follow-ups (out of scope for R76.H3)

  • .claude/skills/ mirror resync for the 4 skills touched here (defer to separate task per CLAUDE.md §9.2 forbid-hand-edit rule).
  • HERITAGE-banner hygiene pass across other active skills not in this task’s 4-skill scope (e.g. colibri-verification’s residual donor refs — covered by sibling R76.H2 task).

R76.H3 verification — upstream: audit, contract, packet, implement. Chain complete.

Back to top

Colibri — documentation-first MCP runtime. Apache 2.0 + Commons Clause.

This site uses Just the Docs, a documentation theme for Jekyll.