chore(packages): remove affine-ts; close #66 won't-do (#95)

TypeScript is not a first-class consumer in the AffineScript ecosystem.
Per the estate's no-new-TypeScript policy, hand-maintaining (or auto-
generating) a dedicated TS package surfaces TS where it shouldn't be.

Changes:
- Delete packages/affine-ts/ entirely (4 files: README.adoc, deno.json,
  mod.js, types.d.ts).
- Update .claude/CLAUDE.md TypeScript Exemptions table — drop the
  affine-ts row (now 7 active exemptions, down from 8). Add closed-
  exemption note documenting the removal.
- Update packages/affine-js/README.adoc — replace the "companion
  affine-ts" pointer with a sentence saying TS is not a first-class
  consumer; TS callers should use affine-js directly with their own
  typings.

The remaining packages/affine-js/types.d.ts exemption is preserved as
the single interop surface for JS callers (most of whom happen to use
TS tooling). That exemption stands or falls separately.

Closes #66 — won't-do. Issue #66 proposed auto-generating .d.ts files
for affine-js AND affine-ts. With affine-ts removed, the scope of #66
shrinks to "just affine-js", and that's a separate, smaller decision
that should be its own issue if pursued.

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

Author: hyperpolymath

.claude/CLAUDE.md

@@ -70,20 +70,20 @@ Both are FOSS with independent governance (no Big Tech).
 
 ### TypeScript Exemptions (Approved)
 
-The "no new TypeScript" rule has eight approved exemptions in this repo. These paths are *not* policy violations — they are documented carve-outs because the file format or downstream consumer requires TypeScript:
+The "no new TypeScript" rule has seven approved exemptions in this repo. These paths are *not* policy violations — they are documented carve-outs because the file format or downstream consumer requires TypeScript:
 
 | Path | Files | Rationale | Unblock condition |
 |---|---|---|---|
 | `packages/affine-js/types.d.ts` | 1 | TypeScript declaration file — the public API contract by which JS callers consume AffineScript-compiled artefacts. `.d.ts` is TS by definition. | Generate from canonical compiler output (issue: see ROADMAP). |
-| `packages/affine-ts/types.d.ts` | 1 | Same, for TS callers. | Same as above. |
 | `affinescript-deno-test/*.ts` | 6 | Deno-based test harness for AffineScript itself: `cli.ts`, `mod.ts`, `lib/{compile,discover,runner}.ts`, `example/smoke_driver.ts`. Deno test runner is TS-native. | AffineScript stdlib + Deno bindings (no scheduled issue). |
 
 Adding to this list requires explicit user approval and an unblock condition. New TypeScript files outside this list are still banned per the policy table above.
 
 **Closed exemptions:**
 - `editors/vscode/src/extension.ts` — closed 2026-05-03 by issue #35 Phase 3 (Node-target codegen + Vscode bindings landed). Source of truth is now `editors/vscode/src/extension.affine`, compiled to `out/extension.cjs`. Re-introducing the .ts file is blocked by `tools/check-no-extension-ts.sh` (wired into `just check` and `.github/workflows/ci.yml`).
+- `packages/affine-ts/` — removed 2026-05-11 (issue #66 closed won't-do). TypeScript is not a first-class consumer; TS callers should use `@hyperpolymath/affine-js` directly and supply their own typings.
 
-The 5 external references to `affinescript-deno-test/` (CI workflow, status docs, history docs) and the 3 references to `packages/affine-{js,ts}/` (status docs, Deno config) are why physical relocation into a `vendor/` subtree was rejected — the relocation cost exceeded the visibility benefit when the directories are already named clearly.
+The 5 external references to `affinescript-deno-test/` (CI workflow, status docs, history docs) and the references to `packages/affine-js/` (status docs, Deno config) are why physical relocation into a `vendor/` subtree was rejected — the relocation cost exceeded the visibility benefit when the directories are already named clearly.
 
 ### Package Management
 

packages/affine-js/README.adoc

@@ -137,8 +137,10 @@ All JS ↔ WASM value exchanges use the `AffineValue` tagged-union type:
 package without any additional steps — the type definitions are automatically
 picked up by `tsc` and editors.
 
-For TypeScript projects, the companion `@hyperpolymath/affine-ts` package
-provides enhanced declarations with stricter generics.
+TypeScript is not a first-class consumer in the AffineScript ecosystem. There
+is no `@hyperpolymath/affine-ts` package; TS callers should consume
+`@hyperpolymath/affine-js` directly via the shipped `.d.ts` and supply any
+project-specific typings themselves.
 
 == Return type hints