The original reason for the civitai-side policy override system was that
the orchestrator wasn't surfacing a policy hash, so we couldn't record a
meaningful policyVersion in the audit log. The latest @civitai/client now
includes results[number].policyHash, so we can read it directly and let
the orchestrator stay the source of truth for policy text + thresholds.
- Delete /moderator/xguard-policies page + tRPC router + service + schema
- Remove XGUARD.POLICIES_TEXT / POLICIES_PROMPT Redis key constants
- createXGuardModerationRequest no longer fetches policies from Redis or
builds labelOverrides; just passes the caller's labels filter through
- recordXGuardScan reads policyHash from each result instead of from
a metadata-stamped policyVersions map
- @civitai/client bump (typing brings the new field along)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Briant Diehl
69fa598974