Wire hyperscript activation into browser boot pipeline

- orchestration.sx: add hs-boot-subtree! call to process-elements
- integration.sx: remove load-library! calls (browser loads via manifest)
- sx_vm.ml: add __resolve-symbol hook to OP_GLOBAL_GET for lazy loading
- compile-modules.js: add HS modules as lazy_deps in manifest

HS compilation works in browser (tokenize→parse→compile verified).
Activation pipeline partially working — hs-activate! needs debugging
(dom-get-data/dom-set-data interaction with WASM host-get on functions).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

hosts/ocaml/browser/compile-modules.js

@@ -399,6 +399,12 @@ if (entryFile) {
   ]);
   const eagerDeps = entryFile.deps.filter(d => !LAZY_ENTRY_DEPS.has(d));
   const lazyDeps = entryFile.deps.filter(d => LAZY_ENTRY_DEPS.has(d));
+  // Hyperscript modules aren't define-library, so not auto-detected as deps.
+  // Load them lazily after boot — eager loading breaks the boot sequence.
+  const HS_LAZY = ['hs-tokenizer', 'hs-parser', 'hs-compiler', 'hs-runtime', 'hs-integration'];
+  for (const m of HS_LAZY) {
+    if (manifest[m] && !lazyDeps.includes(m)) lazyDeps.push(m);
+  }
   manifest['_entry'] = {
     file: entryFile.file,
     deps: eagerDeps,