docs(claude): TypeScript Exemptions table for documented TS files (#19)

Adds a documented `TypeScript Exemptions` section to
`.claude/CLAUDE.md`, mirroring the affinescript / standards / my-lang /
boj-server pattern.

The new RSR antipattern check (deployed estate-wide) reads this table at
CI time. Each row covers a path with rationale + unblock condition, so
the exemption is visible and audit-friendly.

This is the documented carve-out for files that legitimately can't be
AffineScript today (Node/Deno-runtime, no AffineScript binding,
port-in-progress, etc.). Migrating any individual file just removes the
corresponding row.

Author: hyperpolymath

.claude/CLAUDE.md

@@ -81,3 +81,12 @@ Both are FOSS with independent governance (no Big Tech).
 - SHA-pinned dependencies
 - SPDX license headers on all files
 
+### TypeScript Exemptions (Approved)
+
+The hyperpolymath "no new TypeScript" policy has the following approved exemptions in this repo. These are *not* policy violations — they are documented carve-outs.
+
+| Path | Files | Rationale | Unblock condition |
+|---|---|---|---|
+| `tools/**/*.ts` | 13 | tools/ subdirectory: monitoring-api (Express), stale scanner (Node CLI), github-action (Octokit). Each tool depends on a Node-native library that does not yet have an AffineScript binding. | AffineScript Node-target codegen (affinescript#35) + per-tool bindings (Octokit, Express, ArangoDB driver). |
+
+Adding to this list requires explicit user approval and an unblock condition. New TypeScript files outside this list are blocked by the RSR antipattern check.