Skip to content

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

Description

@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

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.

Activity

  1. hyperpolymath commented on May 30, 2026

    @hyperpolymath
    OwnerAuthor

    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.

  2. hyperpolymath commented on May 30, 2026

    @hyperpolymath
    OwnerAuthor

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

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

  3. hyperpolymath commented on May 30, 2026

    @hyperpolymath
    OwnerAuthor

    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.

  4. added
    migrationPorting between languages or toolchains (e.g. -> AffineScript)
    and removed on Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    meta:campaignCoordinated multi-repo push with a defined end statemigrationPorting between languages or toolchains (e.g. -> AffineScript)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions