# TOMBSTONE — buddy/ dead-code (2026-05-27)

Council convening #5 (`_council/2026-05-27-dead-code-buddy/`) archived 5 files after 5-seat audit (balance/performance/race/lore/compliance). 4/5 seats independently flagged the dispatcher pre-taxonomy was wrong — these are v1 ghosts, self-tombstones, and orphaned half-builds, not unwired-but-live code.

## Files archived

### `buddy/points/combat.mcfunction`

V1 ghost. File header says "Called from hook in existing kill tracking" — that hook was implemented as the delta-snapshot pattern instead, and this file is the leftover. The live v2 `buddy/points/combat_delta.mcfunction` reads the vanilla `adv.mob_kills` stat objective and computes a delta inside `points/tick_player.mcfunction:40`, awarding +1 per kill with the player's own buddy within 16 blocks. Wiring `combat.mcfunction` on a kill-event advancement would double-count every kill. 0 callers in the entire datapack.

### `buddy/points/explore.mcfunction`

V1 ghost (identical story to combat). Header says "Called from hook in structure discovery system" — implemented as delta-snapshot instead. Live v2 `buddy/points/explore_delta.mcfunction` reads `adv.stat_struct` and deltas, wired at `points/tick_player.mcfunction:43` awarding +15 per new structure with buddy nearby. Wiring `explore.mcfunction` would double-count every new structure. 0 callers.

### `buddy/gui/spawn_tabs.mcfunction`

Self-tombstoned 3-line no-op. File header says "DEPRECATED — Tab navigation now handled by companion hub buttons (companions/handler/menu_v2/spawn_hub.mcfunction). Kept as no-op for backwards compatibility." 0 callers. Same v1→v2 archive-and-go pattern shipped in codex/ council convening #3.

### `buddy/revive/check_conditions.mcfunction`

Orphaned ceremony entry. Header gates a midnight revive (`#visual_time matches 18000..18100`) and dispatches to `buddy/revive/buddy_revive`. But `buddy_revive` is a particle-only stub (see below), and the niche is already served by tamed_bond's Moonbloom Ceremony (full-moon + Torchflower) and the buddy `best/revive` 10-min auto-revive. 0 callers. Adding a third midnight-ceremony path would muddy the three-tier "graded recovery" design.

### `buddy/revive/buddy_revive.mcfunction`

Particle-only stub. Plays soul/enchant particles + tellraw "The midnight air shimmers... Your buddy's spirit stirs and returns to the world." But the file body comment says "actual entity respawn will be handled by the existing tomb system" — and no such hook exists. The tomb system is tamed_bond's full-moon path, NOT midnight. Half-built v1 idea. The whole `buddy/revive/` folder was deleted along with this file.

## Followups in 10-pending

- `tamed_bond/` Council #6 may light some of these revive concepts up again with proper layering — re-audit if Joseph commissions that convening.
