skill-naming-drift-infra-orchestrator-vs-platform-orchestrator
master-orchestrator/SKILL.md phase status table referenced ‘infra-orchestrator’ but the actual skill is named ‘platform-orchestrator’. The lint script’s phantom-skill-ref check would have caught this; it was found manually during audit. Any renaming of a skill must cascade-grep all other skills for the old name immediately — rename without cascade = instant phantom reference.
Related
- 2026-04-04-oracle-001-self-architecture-analysis
- 400-line-hard-limit-enforced-via-lint-not-honor-system
- ghost-planned-skills-in-coherence-orchestrator-registry
- fusion-invariants-lint-was-structural-only-not-semantic
- docker
- subagent-grep-operations-leave-temp-files-in-tmp
- master-orchestrator-infra-orchestrator-stale-typo