Remove legacy TLC 4.5 governance metadata

[MichaelSaucier]

TLC 5 will be packaged differently. This narrowly removes the three repository-local files under .governance/tlc/.

Scope: metadata deletion only. The TLC 4.5 audit workflow, CODEOWNERS entries, product code, runtime behavior, and repository settings are intentionally unchanged.

Validation: exact three-file deletion; no executable bytes changed. This PR does not authorize TLC 5 adoption or enforcement.

[MichaelSaucier]

Cross-Family Adversarial Review — PASS

• Exact subject: transpara-ai/agent PR Remove legacy TLC 4.5 governance metadata #35; base a3cc4a3c0822c3c5e875c274835c81a09bbed275; head 4efdde7e190865362c674a7540a10af44bf3b635; diff SHA-256 f8f7819110d542009b4aee813f5e2ae62477bfc0d1828b459303c59521344e07.
• Author lineage: MichaelSaucier (Human order/commit identity) + Codex/OpenAI (implementation operator).
• Independent reviewer: Anthropic claude-opus-5, effort max; route openai-author-cross-family-gates → anthropic-ordinary-gate-review.
• Invocation: terminal success, no tools/network, session 7f900547-1e70-45c5-9990-c97a16b33a85, result f5aba085-8d3f-48c7-9b91-51154561bd03.
• Result: PASS; blocker count: 0.

Validation: the complete diff deletes only the three legacy files under .governance/tlc/; there are no additions, modifications, executable bytes, or paths outside that directory. Exact-head readback confirms .governance/tlc/ is absent. Ordinary required CI is terminal-success; the remaining pending context is this exact-head CFAR result.

Findings: no diff change is required. Retained TLC 4.5 audit workflow and stale CODEOWNERS path are non-blocking for the Human-ordered folder-only scope. The legacy workflow remains audit-only, and the deleted profile granted no authority.

Residual risks: future changes to the retained legacy workflow could make a missing profile operationally relevant; historical metadata remains recoverable from Git. Any head change invalidates this result.

Non-authorizations: this review does not itself authorize merge, TLC 5 adoption/enforcement, branch-protection changes, workflow/CODEOWNERS changes, deployment, or runtime effects. Merge remains subject to the authenticated Human order and repository protection.