Move perf-review skill to .agents/skills to match repo convention (#11950)

Move perf-review skill to .agents/skills to match repo convention

Skills live canonically under .agents/skills/<name>, with a
.claude/skills/<name> symlink so Claude Code still discovers them.
perf-review (landed in #11912) was the outlier -- stored as real files
under .claude/skills. Move it to .agents/skills/perf-review, add the
compatibility symlink matching the other five skills, and point the
AGENTS.md reference at the canonical path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Co-authored-by: devflow.devflow-routing-intake <devflow.devflow-routing-intake@kubernetes.us1.ddbuild.io>

Author: dougqh

.claude/skills/perf-review/SKILL.md .agents/skills/perf-review/SKILL.md.claude/skills/perf-review/SKILL.md renamed to .agents/skills/perf-review/SKILL.md

@@ -0,0 +1 @@
+../../.agents/skills/perf-review

…skills/perf-review/references/.gitignore …skills/perf-review/references/.gitignore.claude/skills/perf-review/references/.gitignore renamed to .agents/skills/perf-review/references/.gitignore .claude/skills/perf-review/references/.gitignore renamed to .agents/skills/perf-review/references/.gitignore

@@ -77,7 +77,7 @@ Before marking a PR ready, run the applicable reviews below over the branch chan
 
 ### Performance Review
 
-Follow the performance-review guidelines in [.claude/skills/perf-review/SKILL.md](.claude/skills/perf-review/SKILL.md) — the do-no-harm / assume-hot posture, the hot-path checks (universal + Java J1–J11 + ByteBuddy-Advice idioms), and the confidence/severity model, with the detailed rubric in its `references/`. Scope: hot-path allocation, unbounded memory, repeated work, escaping objects, native-boundary crossings, and JVM-specific pitfalls.
+Follow the performance-review guidelines in [.agents/skills/perf-review/SKILL.md](.agents/skills/perf-review/SKILL.md) — the do-no-harm / assume-hot posture, the hot-path checks (universal + Java J1–J11 + ByteBuddy-Advice idioms), and the confidence/severity model, with the detailed rubric in its `references/`. Scope: hot-path allocation, unbounded memory, repeated work, escaping objects, native-boundary crossings, and JVM-specific pitfalls.
 
 ## Bootstrap constraints (critical)