chore(make): remove unused claude-rules bridge symlink

The bridge at ~/.claude/skills/claude-rules existed so a SKILL.md could resolve a relative path like ../claude-rules/testing.md from the install layout. No SKILL.md actually uses that pattern. Every reference I grepped — across debug, add-tests, and pairwise-tests — names the rule file by bare filename in prose, which doesn't go through any link. The symlink was defensive scaffolding for a use case that didn't land.

The four rule files keep loading via ~/.claude/rules/ unchanged. Claude Code's skill harness was silently ignoring the bridge anyway because the target directory has no SKILL.md, so no behavior moves except that make install stops creating the dead entry. If a future SKILL.md wants deep-linking, the bridge can come back deliberately.

1 files changed, 0 insertions, 18 deletions

diff --git a/Makefile b/Makefile
index c14f22b..e6f6f56 100644
--- a/Makefile
+++ b/Makefile
@@ -148,16 +148,6 @@ install: ## Symlink skills and rules into ~/.claude/
 		fi \
 	done
 	@echo ""
-	@echo "Bridge symlink (lets SKILL.md cross-refs to ../claude-rules/ resolve from the install layout):"
-	@if [ -L "$(SKILLS_DIR)/claude-rules" ]; then \
-		echo "  skip  claude-rules (already linked)"; \
-	elif [ -e "$(SKILLS_DIR)/claude-rules" ]; then \
-		echo "  WARN  claude-rules exists and is not a symlink — skipping"; \
-	else \
-		ln -s "$(CURDIR)/claude-rules" "$(SKILLS_DIR)/claude-rules"; \
-		echo "  link  claude-rules → $(SKILLS_DIR)/claude-rules"; \
-	fi
-	@echo ""
 	@echo "Claude config:"
 	@for f in $(CLAUDE_CONFIG); do \
 		name=$$(basename $$f); \
@@ -205,14 +195,6 @@ uninstall: ## Remove global symlinks from ~/.claude/
 		fi \
 	done
 	@echo ""
-	@echo "Bridge symlink:"
-	@if [ -L "$(SKILLS_DIR)/claude-rules" ]; then \
-		rm "$(SKILLS_DIR)/claude-rules"; \
-		echo "  rm    claude-rules"; \
-	else \
-		echo "  skip  claude-rules (not a symlink)"; \
-	fi
-	@echo ""
 	@echo "Claude config:"
 	@for f in $(CLAUDE_CONFIG); do \
 		name=$$(basename $$f); \