[campaign #254] STEP 4 — BINDING-GAP DISCHARGE: ship AS bindings for "blocked on binding X" subset

[hyperpolymath]

Part of #254. Blocked by step 2.

Goal

Discharge the AffineScript binding gaps that block ports in STEP 2's blocked on binding X bucket. For each missing binding the triage tool emitted, ship the AS binding (or escalate the binding as a permanent JS-residue if the API surface is fundamentally non-bindable).

Cross-reference: AffineScript bindings top-50 roadmap

This step depends directly on the AffineScript bindings top-50 roadmap (memory note project_affinescript_bindings_top50_roadmap.md, gated by affinescript repo issues). T1 of that roadmap covers idaptik blockers (PixiJS, sound/UI, motion, WASM-exports calling, Phoenix, DOM-unblock, Canvas2D, IPC, Ajv); T2-T5 cover estate near-term + web universals + backend + tooling. Many bindings this step needs will overlap with that roadmap — coordinate, do not duplicate.

Seam — shared dependency with #252 STEP 4

The ReScript umbrella #252 has a parallel "stdlib fill from RS surface" step that depends on the same AffineScript bindings top-50 roadmap. Cross-coordinate: when a binding closes a gap that unblocks both .res and .js files, count both campaigns toward the binding's discharge priority. Avoid shipping the same binding twice or in inconsistent shapes.

Acceptance

• For every binding name STEP 2 emitted as blocking ports: either
  • The AS binding ships (PR merged in affinescript or affinescript-stdlib* repo), STEP 2's tool re-runs and reclassifies the affected files into portable now, OR
  • The binding is documented as a permanent JS-residue (added to STEP 1's carve-out class 1 with rationale)
• Each binding PR cross-references both [campaign] Unnecessarily-JavaScript → AffineScript estate migration (UMBRELLA) #254 (this step) and the AS top-50 roadmap issue it discharges
• Each binding PR cross-references [campaign] ReScript → AffineScript estate migration (UMBRELLA) #252 if the same gap also blocks RS ports
• Updated bucket-count comment on [campaign] Unnecessarily-JavaScript → AffineScript estate migration (UMBRELLA) #254 after each batch of binding lands (delta vs prior count)
• Per-PR ownership gate respected

Sequencing

Blocks: STEP 5 re-triage iteration depends on bindings landing here.
Blocked by: STEP 2 (need the blocked on binding X bucket to know what to ship). Practically also paced by the AS top-50 roadmap's own progress.

[hyperpolymath]

Layer-4 dependency now has a canonical home: hyperpolymath/affinescript#446 (top-50 framework bindings UMBRELLA, filed 2026-05-30). The 'blocked on binding X' bucket this STEP discharges will pull from #446's tier issues.

[hyperpolymath]

📚 Documentation landed in PR #314 — docs/migrations/js-to-affinescript/README.adoc §STEP 4 captures:

• Cross-references to affinescript#446 (AS bindings top-50 roadmap)
• Seam with [campaign] ReScript → AffineScript estate migration (UMBRELLA) #252 (ReScript campaign) STEP 4 — same top-50 dependency, avoid double-shipping
• Per-binding disposition: bind it OR carve it out (+ rationale)
• Cross-PR linking requirement

Still owed: actual binding PRs in affinescript / affinescript-stdlib*. Stays open until each binding STEP 2 emitted is either shipped or carved out.

[hyperpolymath]

Closing per the 2026-05-30 documentation pass — the canonical campaign doc landed in PR #314. Implementation work (Hypatia rule, classifier tool, ports, bindings, re-triage cycles) can be tracked in fresh issues or referenced from the doc as it proceeds.