# _hyperscript Feature Audit Comprehensive audit of our SX _hyperscript implementation vs the upstream reference. **Implementation files:** - `lib/hyperscript/tokenizer.sx` — lexer (129 keywords, 17 token types) - `lib/hyperscript/parser.sx` — parser (67 internal functions, ~3450 lines) - `lib/hyperscript/compiler.sx` — compiler (AST to SX, ~100 dispatch cases) - `lib/hyperscript/runtime.sx` — runtime shims (49 functions) **Test files:** - `spec/tests/test-hyperscript-behavioral.sx` — 381 conformance tests (from upstream) - `spec/tests/test-hyperscript-conformance.sx` — 184 additional conformance tests - `spec/tests/test-hyperscript-tokenizer.sx` — 43 tokenizer tests - `spec/tests/test-hyperscript-parser.sx` — 93 parser tests - `spec/tests/test-hyperscript-compiler.sx` — 44 compiler tests - `spec/tests/test-hyperscript-runtime.sx` — 26 runtime tests - `spec/tests/test-hyperscript-integration.sx` — 12 integration tests **Upstream reference:** `spec/tests/hyperscript-upstream-tests.json` — 831 tests from upstream master+dev --- ## Upstream Test Breakdown | Complexity | Count | Description | |-----------|-------|-------------| | simple | 469 | DOM-based tests, simplest to translate | | run-eval | 83 | Eval-only tests (no DOM setup) | | evaluate | 125 | Full browser eval with DOM interaction | | promise | 57 | Async/promise-based tests | | eval-only | 39 | Pure expression evaluation | | script-tag | 36 | Tests using `