chore: re-check claude-* plugin names if any skill ships to the API Skills surface

[kyle-sexton]

Platform-side skill-name validation rejects reserved words 'anthropic'/'claude'. Plugin names (claude-config, claude-memory, claude-ops) are out of that rule's scope in Claude Code today (verified live 2026-07-17). Trigger: first API-surface shipment.

Origin: skill-name audit + interview, contract at docs/topics/shadowed-skill-renames/PLAN.md (PR #256).

[kyle-sexton]

This was generated by AI (triage lane, gate-audit pass — cycle 2 retry, instance melo-lap-001-triage-20260727T125559Z).

Gate-audit verdict: STAYS GATED. Dormant, explicitly trigger-gated ("Trigger: first API-surface shipment"); confirms nothing is actionable today ("out of that rule's scope in Claude Code today, verified live 2026-07-17"). Also a cross-cutting plugin-rename decision if it ever fires.

Decision needed — RECOMMENDED: no action this cycle; re-check when any skill first ships to the API Skills surface.

Consensus: fable-lens panel + independent fresh-context second lens + this lane's own read. Labels unchanged (needs-human stays). This lane triages/gate-audits only.

[kyle-sexton]

Frontier disposition (drain session)

Ruling: watch item with an unfired trigger. No skill has shipped (or is scheduled to ship) to the API Skills surface, so the claude-* name re-check has nothing to check against. A standing open issue is the wrong storage for a dormant trigger.

Reopen trigger: the first time any skill from this marketplace is prepared for the API Skills surface, reopen and run the name re-check before shipping.