Stop unrelated post-merge workflow failures in Rules V3

[Copilot]

1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

YakShaver-raised issue: two workflows were failing after normal merges in Rules V3, creating noisy false-failure notifications (Content Snapshot Cleanup (Agent 3b) and Validate-Frontmatter-in-All-Rules).

2. What was changed?

The failures were caused by (1) a guard step treating expected non-match as hard failure, and (2) a legacy validator workflow targeting a removed path.

• Content Snapshot Cleanup (Agent 3b)

  • Moved issue guard behavior into pre-activation semantics (skip path) instead of failing runtime execution.
  • Added is_contenthawk_judge_issue output in pre-activation and gated activation on it for issues events.
  • Removed the in-agent exit 1 guard step that produced false failures.

• Validate front matter in all rules

  • Removed .github/workflows/validate-frontmatter-all.yml (obsolete for Rules V3 layout; it searched rules/ which no longer exists).

# New activation gate (lock workflow)
if: needs.pre_activation.outputs.activated == 'true' &&
    (github.event_name != 'issues' ||
     needs.pre_activation.outputs.is_contenthawk_judge_issue == 'true')

3. I paired or mob programmed with:
   N/A

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/github/gh-aw/releases/latest
  • Triggering command: /usr/bin/gh gh extension install github/gh-aw (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Calinator444]

Closing this - I'm going to ship the fix as a CotnentHawk fix. Thanks Copilot 👍