docs(language-policy): codify TS→AffineScript migration state + carve-outs

TS→AffineScript migration is in-flight, not complete (unlike V→Zig which
closed 2026-05-28). Doc state had drifted: TS row in LANGUAGE-POLICY.adoc
listed replacement as ReScript (itself banned 2026-04-30), Migration
Priority §2 said "Convert TS to ReScript", and the standards/.claude
exemption table only listed avow-telegram-bot — missing the structural
carve-outs (.d.ts, */bindings/{deno,ts,typescript}/, tooling configs,
upstream forks, archives).

Mirrors the V→Zig sweep structure (standards#227): codifies five
carve-out classes, references the hypatia detection rule
(cicd_rules/typescript_detected) with path_allow_prefixes parallel to
:vlang_detected, adds v1.3.0 amendment, extends language-policy.yml
workflow to block new TS outside carve-outs.

Inventory recorded in project tracker
project_estate_ts_to_affinescript_2026_05_28.md: 909 total TS files,
~288 estate-authored after carve-out, top targets idaptik (52) +
wordpress-tools (43) + developer-ecosystem (18).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.claude/CLAUDE.md

@@ -128,10 +128,18 @@ Both are FOSS with independent governance (no Big Tech).
 
 ### 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.
+The hyperpolymath "no new TypeScript" policy has the following approved exemptions, encoded as `path_allow_prefixes` on the hypatia rule `cicd_rules/typescript_detected` (matches `*.ts`). These are *not* policy violations — they are documented carve-outs.
 
-| Path | Files | Rationale | Unblock condition |
-|---|---|---|---|
-| `avow-protocol/telegram-bot/avow-telegram-bot/**` | 4 | Telegram bot — Telegraf / node-telegram-bot-api are the canonical TS-native libraries for the Bot API; no AffineScript binding planned. | AffineScript Telegram-bot bindings (no scheduled issue). |
+Existing pre-2026-04-30 `.ts`/`.tsx` outside these carve-outs is grandfathered while in-flight migration proceeds (~288 estate-authored files across ~40 repos as of 2026-05-28; see project tracker `project_estate_ts_to_affinescript_2026_05_28.md`). New TS files in non-carve-out paths are blocked.
 
-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.
+| Path / Pattern | Class | Rationale | Unblock condition |
+|---|---|---|---|
+| `**/*.d.ts` | declaration | FFI/library type definitions (headers, not implementation). | Never — declaration files are the boundary, not the code. |
+| `**/bindings/deno/**`, `**/bindings/typescript/**`, `**/bindings/ts/**` | interop target | We expose work to TS/Deno consumers without authoring TS as primary code path. Exemplar: `proven/bindings/deno/` (72 files — Idris2 ABI exposed as Deno-native module). Parallel to V-lang `v-cartridge`/`v-adapter`/`v-bindings`/`v-client` carve-out. | Never — these are consumer-facing bindings. |
+| `avow-protocol/telegram-bot/avow-telegram-bot/**` | PERMANENT | Telegraf / node-telegram-bot-api are the canonical TS-native libraries for the Bot API; no AffineScript binding planned. | AffineScript Telegram-bot bindings (no scheduled issue). |
+| `**/vite.config.ts`, `**/vitest.config.ts`, `**/tsup.config.ts`, `**/tsconfig.json` | tooling | Build orchestration, not application code. | When AffineScript ships native equivalents. |
+| `affinescript-deno-test/**`, `affinescript-cli/**` | bootstrap shim | TS/JS shims used to bootstrap the AffineScript test runner / CLI. | When AffineScript self-hosts these. |
+| `rescript/**`, `servers/**`, `repos-monorepo/**` | upstream fork | Not estate-authored — vendored upstream code (ReScript compiler, third-party MCP servers, mass aggregator). | Never — upstream fork. |
+| `hyperpolymath-archive/**` | archived | GitHub-archived repos cannot accept PRs; TS is dormant. | Never — archived. |
+
+Adding to this list requires explicit user approval and an unblock condition (except the structural classes above, which are estate-wide policy). The detection rule and its `path_allow_prefixes` field are the single source of truth; this table mirrors that for human readability.

rhodium-standard-repositories/.github/workflows/language-policy.yml

@@ -44,5 +44,34 @@ jobs:
               exit 1
             fi
           fi
-          
+
+          # Block new TypeScript files (banned 2026-04-30, replacement: AffineScript).
+          # Carve-outs (parallel to hypatia cicd_rules/typescript_detected path_allow_prefixes):
+          #   *.d.ts                          declaration files (headers, not impl)
+          #   */bindings/{deno,ts,typescript}/  interop targets (consumers of our work)
+          #   avow-protocol/telegram-bot/avow-telegram-bot/  Telegraf PERMANENT exemption
+          #   *.config.ts / vite.config.ts / vitest.config.ts / tsup.config.ts  tooling
+          #   affinescript-deno-test/ + affinescript-cli/  bootstrap shims
+          #   rescript/ + servers/ + repos-monorepo/  upstream forks
+          #   hyperpolymath-archive/  archived repos
+          NEW_TS=$(git diff --name-only --diff-filter=A HEAD~1 2>/dev/null \
+            | grep -E '\.tsx?$' \
+            | grep -vE '\.d\.ts$' \
+            | grep -vE '/bindings/(deno|typescript|ts)/' \
+            | grep -vE '^avow-protocol/telegram-bot/avow-telegram-bot/' \
+            | grep -vE '(^|/)(vite|vitest|tsup)\.config\.ts$' \
+            | grep -vE '\.config\.ts$' \
+            | grep -vE '^(affinescript-deno-test|affinescript-cli)/' \
+            | grep -vE '^(rescript|servers|repos-monorepo|hyperpolymath-archive)/' \
+            || true)
+          if [ -n "$NEW_TS" ]; then
+            echo "❌ New TypeScript files detected (banned 2026-04-30). Use AffineScript instead."
+            echo "$NEW_TS"
+            echo ""
+            echo "If this file genuinely belongs to a carve-out class, add it via"
+            echo "the hypatia rule's path_allow_prefixes — see standards/.claude/CLAUDE.md"
+            echo "§TypeScript Exemptions (Approved)."
+            exit 1
+          fi
+
           echo "✅ Language policy check passed"

rhodium-standard-repositories/spec/LANGUAGE-POLICY.adoc

@@ -122,8 +122,29 @@ NOTE: For full rationale and migration guides, see the link:{source-repo}[CCCP r
 | Banned | Replacement | Rationale
 
 | *TypeScript*
-| ReScript
-| Unsound gradual typing
+| AffineScript
+| Banned in NEW code 2026-04-30 (estate-language-policy refresh
+  `feedback_estate_lang_policy_2026_05_25.md`). Existing `.ts`/`.tsx`
+  is grandfathered while in-flight migration to AffineScript proceeds
+  (see project tracker
+  `project_estate_ts_to_affinescript_2026_05_28.md`). Detection is
+  the hypatia rule `cicd_rules/typescript_detected` (matches `*.ts`)
+  with `path_allow_prefixes` covering five carve-out classes:
+  (1) `*.d.ts` declaration files (FFI/library type definitions —
+  these are headers, not implementation); (2) `*/bindings/deno/`,
+  `*/bindings/typescript/`, `*/bindings/ts/` interop targets where
+  we expose work to TS/Deno consumers without authoring TS as our
+  primary code path (exemplar: `proven/bindings/deno/`);
+  (3) `avow-protocol/telegram-bot/avow-telegram-bot/**` — Telegraf
+  is the canonical TS-native Bot-API library, no AffineScript
+  binding planned (PERMANENT exemption); (4) tooling configs
+  (`vite.config.ts`, `vitest.config.ts`, `tsup.config.ts`,
+  `tsconfig.json`) — these are build orchestration, not application
+  code; (5) upstream forks not estate-authored (`rescript/`,
+  `servers/`, `repos-monorepo/`) and `hyperpolymath-archive/**`
+  (archived repos with dormant TS). Unsound gradual typing is the
+  underlying technical objection; AffineScript provides affine/linear
+  types plus typed-wasm output.
 
 | *Node.js*
 | Deno
@@ -235,7 +256,16 @@ everywhere" rule.
 When encountering banned languages:
 
 1. *Immediate*: Block new code in banned languages
-2. *Short-term*: Convert TypeScript to ReScript (now AffineScript) → typed-wasm
+2. *In-flight 2026-04-30 → ongoing*: Convert existing TypeScript/ReScript/JS
+   → AffineScript → typed-wasm. ReScript is also banned in new code as of
+   2026-04-30; existing `.res` migrates to `.affine` directly (do NOT pass
+   through ReScript). Tracker:
+   `project_estate_ts_to_affinescript_2026_05_28.md` records inventory
+   (~288 estate-authored `.ts`/`.tsx` files post-carve-out across ~40
+   repos), carve-out classes, and per-repo migration order. New TS files
+   are blocked by hypatia `cicd_rules/typescript_detected` (with
+   `path_allow_prefixes` for documented carve-outs) and the
+   `language-policy.yml` reusable.
 3. *Medium-term*: Replace Node/npm with Deno
 4. ✅ *Done 2026-05-28*: V-lang → Zig migration complete across the estate
    (16 admin-merged PRs; hypatia detection rule armed)
@@ -411,6 +441,21 @@ not prose alone.
 
 == Amendments
 
+=== v1.3.0 — 2026-05-28 (Jonathan D.A. Jewell)
+
+Codified the *TypeScript → AffineScript migration state*: in-flight, not
+complete. Existing `.ts`/`.tsx` is grandfathered while migration to
+AffineScript proceeds; new TS in non-carve-out paths is blocked.
+Documented five carve-out classes (`.d.ts`, `*/bindings/{deno,ts,typescript}/`,
+`avow-protocol/telegram-bot/avow-telegram-bot/**`, tooling configs,
+upstream forks + archives). Detection rule: hypatia
+`cicd_rules/typescript_detected` extended with `path_allow_prefixes`
+mirroring the V-lang rule's structure (hypatia#372/#373 precedent).
+Tracker: `project_estate_ts_to_affinescript_2026_05_28.md`. This
+amendment closes the doc-vs-policy drift where TS was listed with
+replacement "ReScript" rather than "AffineScript" (post-2026-04-30
+ReScript is itself banned in new code).
+
 === v1.2.2 — 2026-05-16 (Jonathan D.A. Jewell)
 
 Generalised the scoped convention override into the *Explicit-Escape