feat(codegen): embed affine-vscode adapter at compile time (root-cause fix for #139/#104) (#380)

## Summary

The \`--vscode-extension\` codegen previously emitted a runtime
\`require()\` of \`@hyperpolymath/affine-vscode\` to source the WASM's
\`Vscode\` and \`VscodeLanguageClient\` import modules. That package
isn't published to npm yet (gated on owner action in #104), so the
require failed, \`extraImports()\` returned \`{}\`, and WASM activation
failed every CI run with:

\`\`\`
WebAssembly.instantiate(): Import #1 \"Vscode\":
  module is not an object or function
\`\`\`

The previous CI workaround in PR #377 added a \`file:\` install of the
in-tree adapter as a smoke-test-step bridge — useful, but a workaround.
This PR is the **fundamental fix**: it eliminates the runtime npm
dependency entirely by embedding the adapter source at codegen time.

## What this changes

### 1. \`lib/dune\` — adapter source as compile-time string constant

New \`(rule …)\` generates \`lib/affine_vscode_adapter_source.ml\` from
\`packages/affine-vscode/mod.js\` at build time, exposing the JS source
as an OCaml string:

\`\`\`ocaml
(* AUTO-GENERATED from packages/affine-vscode/mod.js. Do not edit. *)
let source = {affine_vscode|/* …mod.js content… */|affine_vscode}
\`\`\`

### 2. \`lib/codegen_node.ml\` — inline at codegen time

\`vscode_extension_wiring\` now emits a CJS-style closure that wraps the
embedded adapter source. The runtime \`require()\` is still attempted
first so an installed package can override the embedded copy — but it's
no longer load-bearing:

\`\`\`js
try { _makeVscodeBindings = require(\"@hyperpolymath/affine-vscode\"); }
catch (_e) { /* fall through to embedded adapter */ }
if (typeof _makeVscodeBindings !== \"function\") {
  const _adapterModule = { exports: null };
  (function (module, exports) {
    /* …embedded packages/affine-vscode/mod.js source… */
  })(_adapterModule, _adapterModule.exports);
  _makeVscodeBindings = _adapterModule.exports;
}
\`\`\`

### 3. Regenerated \`editors/vscode/out/extension.cjs\`

618 lines, up from 121 — the delta is the inlined adapter source.

### 4. \`editors/vscode/package.json\` — drop \`optionalDependencies\`

The \`@hyperpolymath/affine-vscode\` optional-dep is no longer needed at
install time. The package keeps its in-tree home at
\`packages/affine-vscode/\` as the source of truth for JSR/npm
publishing and for \`--vscode-extension\` codegen consumption.

### 5. \`.github/workflows/ci.yml\` — drop \`continue-on-error: true\`

The vscode-smoke job is now expected to be reliable. A real regression
should turn it red and gate.

## Why this is the right fix

Q: \"Can the VS Code extension use Deno instead of npm?\"

A: No — the VS Code extension host is Electron-embedded Node. The host
loads extensions via Node's \`require()\` and the \`.vsix\` package
format expects CJS. CLAUDE.md \"Runtime Exemptions\" already documents
this as a forced carve-out.

But this PR **reduces** npm exposure by eliminating the runtime
dependency on \`@hyperpolymath/affine-vscode\` (one less npm package
needed at smoke time). The only remaining npm carve-outs at smoke time
are \`@vscode/test-electron\` (smoke runner; no alternative exists) and
\`vscode-languageclient\` (LSP client; npm-published).

## Verification

Local:
- Full build: \`opam exec -- dune build\` ✓
- Codegen WASM tests: \`opam exec -- ./tools/run_codegen_wasm_tests.sh\`
✓ (all pass)
- Regenerated .cjs loads under plain Node:
\`require('out/extension.cjs')\` exports \`activate\`, \`deactivate\`,
\`extraImports\` (function) ✓

CI:
- [ ] \`vscode-smoke\` green on this PR (the real test — was relying on
file:-install bridge from #377; now self-contained)
- [ ] Build / lint / format checks all pass

## Coordination with #377

#377 adds a \`file:\` install bridge in CI that solves the same symptom
at the workflow level. If #377 lands first, this PR's removal of
\`continue-on-error\` and the embedded adapter make the file: install
redundant (it's harmless — the require() inside extension.cjs picks up
the npm-installed version first and uses it; falls back to embedded only
when not installed). If this PR lands first, #377 becomes a no-op
pre-existing-step removal and can be closed.

Refs #139 (smoke harness), #104 (pending npm publish — no longer a
runtime blocker), gitbot-fleet#148.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

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

Author: hyperpolymath

.github/workflows/ci.yml

@@ -211,19 +211,13 @@ jobs:
     # (see CLAUDE.md "Runtime Exemptions") because the VS Code extension
     # host is npm/Node-native and no Deno/JSR equivalent exists.
     #
-    # Visibility-only until #104 lands (continue-on-error). The extension's
-    # wasm module imports the `Vscode` / `VscodeLanguageClient` module
-    # objects from the @hyperpolymath/affine-vscode adapter; without the
-    # adapter (gated on owner action — npm org create + NPM_TOKEN +
-    # affine-vscode-v0.1.0 tag push) the wasm cannot instantiate and
-    # activation fails. The defensive `optionalDependencies` move in
-    # editors/vscode/package.json and the try/catch around the adapter
-    # require in editors/vscode/out/extension.cjs already prevent the
-    # `npm install` step from 404ing — activation degradation is the
-    # remaining gap that #104 closes. Remove the `continue-on-error: true`
-    # line when #104 publishes the adapter to npm.
+    # Self-contained as of the codegen-embed fix: `--vscode-extension`
+    # codegen now inlines the affine-vscode adapter source into the
+    # generated .cjs at compile time, so activation no longer depends on
+    # the @hyperpolymath/affine-vscode npm package being installed
+    # (previously gated on #104's npm publish). A real regression should
+    # turn this job red and gate, so no `continue-on-error`.
     runs-on: ubuntu-latest
-    continue-on-error: true
 
     steps:
       - name: Checkout code
@@ -236,14 +230,12 @@ jobs:
 
       - name: Install test runner dependencies
         working-directory: editors/vscode
-        # The compiled out/extension.cjs is checked in (see #35 Phase 3),
-        # so the smoke test does not need the OCaml toolchain — only the
-        # Node-side test runner deps. peerDeps `vscode` is provided by
-        # @vscode/test-electron at launch; the extension's host-bindings
-        # adapter @hyperpolymath/affine-vscode is an `optionalDependency`
-        # — npm install succeeds when it is unpublished (issue #104), and
-        # the smoke suite below detects the missing adapter and reports
-        # SKIPPED rather than failing.
+        # The compiled out/extension.cjs is checked in (see #35 Phase 3)
+        # and now embeds the affine-vscode adapter inline (codegen-embed),
+        # so the smoke test only needs the @vscode/test-electron runner
+        # deps. `vscode` itself is provided by the test runner at launch.
+        # The #381 SKIP-when-missing guard remains downstream as a safety
+        # net but is now expected to find the adapter present.
         run: npm install --no-audit --no-fund
 
       - name: Report adapter availability