feat: add skill to author and maintain Compass manifests for agentic packs

[rhartuv]

Summary

Add compass-manifest-maintenance Claude skill to author and maintain Compass catalog-info.yaml manifests for agentic packs.

• Workflow for new/updated skills, new packs, and structural drift audits
• MCP mapping reference (mcps.json keys → owned vs canonical Compass refs)
• Relationship rules reference (COMPASS-1288, file touch matrix)
• YAML templates for skill, plugin, and pack Location manifests
• File-based validation only (no Compass MCP)
• Cross-links from CLAUDE.md and agentic-contribution-skill

---

Add missing Compass manifest for ocp-admin/skills/network-policy-architect, closing a pre-existing catalog gap identified during PR #154 review.

• Create catalog-info.yaml (AiResource, namespace: ai5-marketplace, type: skill)
• Register in pack Location and declare bidirectional relations (skill ↔ plugin, skill ↔ openshift-mcp-server) per COMPASS-1288

---

Test plan

• uv run python scripts/validate_skills_tier1.py .claude/skills/compass-manifest-maintenance/SKILL.md passes
• Roster audit: rh-sre, rh-virt, rh-basic - no skills missing from Location targets
• Invoke skill: “Audit rh-sre Compass manifest drift” - expect zero violations
• Invoke skill: “What files would change if remediation added dependsOn on a new skill?” - expect orchestrator + target skill dependencyOf (+ MCP if applicable)
• make validate passes

Closes APPENG-6131
Closes APPENG-6002
Implements #151

[rhartuv]

Note: ocp-admin/skills/network-policy-architect has no catalog-info.yaml (pre-existing gap; out of scope for this PR). @r2dedios

[r2dedios]

True! Good Catch. I'm creating another task for solving this gap and assigning it to you. Good chance for testing the skill you're working on :)

[rhartuv]

True! Good Catch. I'm creating another task for solving this gap and assigning it to you. Good chance for testing the skill you're working on :)

https://redhat.atlassian.net/browse/APPENG-6131

[dmartinol]

isn't the list too restrictive? shouldn't we just provide instruction on how to derive the dependant MCPs w/o listing them?

[rhartuv]

Updated.

[dmartinol]

isn't there any drift that we can prevent adding a CI validation script? (we already have many iof them in the scripts/ folder)

[rhartuv]

Makes sense. I figured this was out of scope for this PR since it's just the skill and docs, but I can add a scripts/validate_compass_manifests.py script for it. Let me know if you'd rather I include it here or open a separate ticket.