rescue: INT-02 / INT-09 / INT-11 — recover stranded feature work from a deleted checkout

[hyperpolymath]

Why

These three commits existed only in a local checkout that an estate reorg
renamed to affinescript.DUPLICATE-superseded-2026-07-27 and then deleted.
They were never on origin. Recovered from a git bundle taken before the
deletion.

The "superseded" label was wrong — see
dev-notes/affinescript-sitrep-2026-07-27.md. The rename judged duplicates by
directory identity rather than by git rev-list, so a checkout holding 9
unpushed commits was marked redundant against one holding 0.

What

Exactly the three hand-authored feature commits, at their original SHAs,
authorship and dates:

• 220d7ca docs: resolve INT-02 satellite scope deferral (ClosesINT-02 follow-up: affinescript-dom-loader satellite shell — scope question (split repo vs fold-into affine-js) #489)
• 70ca15e feat(dom): browser host parity execution harness (INT-11)
• e959636 feat(cadre): scaffold router navigation runtime wrapper (INT-09)

No cherry-pick was required: the three form a contiguous linear chain whose base
commit's parent is origin/main (1c169c0), so the branch was created at
e959636.

8 files, +258/−22 — affinescript-cadre/ (router runtime + e2e),
affinescript-dom/e2e/ (browser parity harness), docs/ECOSYSTEM.adoc.

Deliberately excluded

The other 6 commits in that stack were sweep-authored, including a merge of an
unexplained "rogue duplicate repository" and an uncommitted change that
deletes*.affine text eol=lf linguist-language=AffineScript from
.gitattributes — the line making GitHub recognise 493 source files as
AffineScript. They remain parked in the bundle, unreviewed.

Checks

• No sweep debris: .gitattributes, .gitignore, docs/patch_ecosystem.py all absent from the diff
• Licences: 5 × MPL-2.0, no stray AGPL
• Secrets: none
• REUSE: the two headerless files match existing repo convention (no .reuse//REUSE.toml; none of the 5 existing package.json carry headers)

Draft — CI has not run on these commits before.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate failed

Failed conditions
E Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[gitar-bot]

Note

Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime.
Learn more

Code Review✅ Approved1 resolved / 1 findings

Recovers stranded feature work adding router navigation, browser host parity, and docs resolution, but nesting wasi_snapshot_preview1 under env breaks WASM linking.

✅ 1 resolved

✅ Bug: wasi_snapshot_preview1 nested under env, breaking WASM link

📄 affinescript-dom/e2e/dom_host.mjs:50-54
buildImportObject(env, { imports: { wasi_snapshot_preview1: { fd_write } } }) merges options.imports into the env namespace, so wasi_snapshot_preview1.fd_write becomes importObject.env.wasi_snapshot_preview1 instead of a top-level wasi_snapshot_preview1 namespace. The WASM module imports fd_write from module wasi_snapshot_preview1, so WebAssembly.instantiate throws a LinkError and the reconciler never runs — defeating the INT-11 harness this PR adds. Use the modules option (which loader.js adds verbatim as separate namespaces) instead of imports.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}