feat(compliance): add content compliance detection across tenant, ops, and clients
Implements the Revision 8/9 compliance design: tenant + ops backends, ops-web content-safety pages, admin-web editor/publish gate integration, desktop publish block surfacing, and supporting migrations / shared types / config plumbing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -20,7 +20,8 @@ const publishStatusMap: Record<string, { label: string; color: string }> = {
|
||||
published: { label: 'status.publish.published', color: 'success' },
|
||||
publish_success: { label: 'status.publish.publish_success', color: 'success' },
|
||||
publish_failed: { label: 'status.publish.publish_failed', color: 'error' },
|
||||
pending_review: { label: 'status.publish.failed', color: 'error' },
|
||||
pending_review: { label: 'status.publish.pending_review', color: 'warning' },
|
||||
blocked_by_compliance: { label: 'status.publish.blocked_by_compliance', color: 'error' },
|
||||
}
|
||||
|
||||
export function formatDateTime(value?: string | null, pattern = 'YYYY-MM-DD HH:mm'): string {
|
||||
|
||||
Reference in New Issue
Block a user