hotfix(codegen/js): handle Pattern::Or, Expr::Todo, Expr::Panic

[danieljohnmorris]

Summary

Main is broken — cargo build fails on E0004 non-exhaustive match in src/codegen/js.rs. PRs #706 (todo/panic, ILO-410) and #709 (| match alternatives, ILO-411) added new AST variants; #713 added src/codegen/js.rs without arms for them. Every PR's CI build job has been red since.

Diff

• src/codegen/js.rs — match arms for the new variants
• src/parser/mod.rs — drive-by clippy fixes
• tests/capability_flags.rs — backfill missing env field on 4 Caps::Restricted literals
• tests/regression_js_emit_new_variants.rs (new) — exercises all 3 variants
• ai.txt — regenerated

Test plan

• cargo build green
• cargo clippy -- -D warnings clean
• cargo fmt --check clean
• new + capability_flags tests pass
• CI green

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
688	1	687	0

View the full list of 1 ❄️ flaky test(s)

ilo::interpreter::tests::interpret_braced_guard_in_loop_no_early_return

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.011s run time

thread 'interpreter::tests::interpret_braced_guard_in_loop_no_early_return' (32889) panicked at src/interpreter/mod.rs:10202:9:
parse errors: [ParseError { code: "ILO-P003", position: 27, span: Span { start: 35, end: 36 }, message: "expected `{`, got `;`", hint: Some("ilo bodies are single-line, `;`-separated — not python/swift-style indented. Use either the brace-block form `name p:t>r;{body1;body2}` or the single-line form `name p:t>r;body1;body2`. For statements that require a block (`@k xs{...}`, `wh cond{...}`, `?subj{...}`), the `{...}` must be on the same line as the head.") }]
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}