Repository navigation
INT-10: affinescript-lsp distribution (consume the ADR-019 compiler shim) #282
Description
Ledger INT-10 (was blocked by INT-04). Unblocked by ADR-019 / #260 (compiler distribution: GitHub Releases binaries + thin Deno/JSR shim @hyperpolymath/affinescript).
Scope
affinescript-lsp is distributed/installed such that it resolves a working compiler via the ADR-019 shim (deno add @hyperpolymath/affinescript → shim downloads+verifies the pinned Release binary). No bespoke compiler-bundling in the LSP.
Sequencing
- Blocked on INT-04: compiler distribution strategy (native OCaml binary — not JSR/npm) #260 S2 (release.yml per-platform binary + SHA256SUMS) and S3 (the shim package).
- Then S4 of INT-04: compiler distribution strategy (native OCaml binary — not JSR/npm) #260 == this issue: wire
affinescript-lsponto the shim + a smoke that the LSP can locate/exec the compiler.
Refs #260, #181. ADR-019 in docs/specs/SETTLED-DECISIONS.adoc + .machine_readable/6a2/META.a2ml.
Activity
docs(adr): ADR-019 — compiler distribution: Releases + thin Deno/JSR …
ci(release): #260 S2 — per-platform compiler binaries + SHA256SUMS (A…
feat(cli): #260 S3 — @hyperpolymath/affinescript compiler shim (ADR-019)
feat(cli): #260 S3 — @hyperpolymath/affinescript compiler shim (ADR-019…
feat(lsp): INT-10 — affinescript-lsp resolves compiler via ADR-019 sh…
hyperpolymath commentedon May 19, 2026
Reopened: this was auto-closed when PR #285 (#260 S3 shim) was merged via the gitbot's Refs-auto-close behaviour. The actual INT-10 wiring (
affinescript-lspconsuming the@hyperpolymath/affinescriptshim) is not yet done — gated on thev0.1.0Release workflow (run 26124042846, still queued) producing assets sopins.jscan be filled and the shim version bumped (#260 S4). Restoring the true state.feat(shim): #260 S4 — finalise pins.js for v0.1.0 (partial), bump shi…
hyperpolymath commentedon May 20, 2026
Update — diagnosed why the v0.1.0 Release workflow's
macos-x64leg has been queued ~10 h: it's not CI concurrency, it's thatmacos-13GitHub-hosted runners were fully retired on 2025-12-04 (actions/runner-images#13046, #13402, #13634). The release.yml matrix was pinning a runner image that no longer exists; the job was never going to start.Actions taken just now:
os: macos-13→os: macos-15-intel(the current Intel x64 standard runner per the actions/runner-images README; stable GA, in contrast to the still-stabilisingmacos-26-intel).linux-x64+macos-arm64); it leavesmacos-x64fail-closed as documented.Once #292 merges and the next
v*tag is cut, the workflow will produce the missingmacos-x64binary + a completeSHA256SUMS. The follow-up shim release fills the last pin in pins.js, and #282 can finally close.ci(release): swap retired macos-13 runner for macos-15-intel (#292)
fix(release): scope checksums-job gh calls with --repo to avoid the g…
feat(shim): close INT-10 — pin v0.1.1 (full coverage), bump shim 0.1.2 (
fix(version): single source of truth via lib/version.ml + tag-time ba…
docs: catch up TECH-DEBT, PACKAGING + STATE.a2ml with the 2026-05-20 …