feat!(build): cross-runtime pipeline with Node.js support, idempotent debug server, and CI hardening

[ofriw]

Note: This PR was generated by an AI agent. If you'd like to talk with other humans, drop by our Discord!

---

Summary

Closes #44.

Redesigns the build pipeline with a strict esbuild plugin stack and two-phase CSS pipeline, adds Node.js support across createBuildContext() and startDebugServer(), hardens the debug server lifecycle, fixes file-watcher reliability on Windows, and overhauls CI + test infrastructure.

---

Breaking Changes

Change	Before	After
startDebugServer return	Promise<never> (never resolves)	Promise<void> (resolves on shutdown)
AppConfig.cssPath	Sole CSS source	Vendor/prepend CSS only; app CSS via import './index.css' in JS entry
Config auto-detection	Heuristic across runtimes	Runtime-specific: deno.json / package.json, no cross-runtime fallback
config.debug	Leaked after server stop	Saved on entry, restored on exit
NoMatchError filtering	String-matching in test runner	Proper NoMatchError class with exit code 2

---

What's New

• Node.js support — createBuildContext(), startDebugServer(), and all server templates now work on Node.js
• esbuildPlugins option on compile() and startDebugServer() — custom esbuild plugins in the client bundle pipeline
• DebugServerSession exposed via onReady callback: { server, url, stop }
• onReady / openBrowser options on startDebugServer
• Concurrent-call guard on startDebugServer — rejects if another instance is running
• Idempotent Server.stop() — promise-cached, safe to call concurrently
• Windows polling watcher — fallback when libuv fs.watch crashes (Node 24.16.0)
• CI matrix workflow — static analysis, formatting checks, caching across all jobs
• RuntimeAdapter pattern — getRuntime() with .exit(), .getCWD(), .setupSignalHandler(), .openBrowser()
• Injection-based test hooks — withTestCWD, withTestBrowserOpenCommand, withLogCapture, injectTestTransport, injectAppendFailure

---

What Changed

• Build plugin stack — strict ordering: adapter stubs → node stubs → user plugins → CSS loader → Deno loader
• CSS pipeline — buildCombinedCSS() merges vendor CSS (cssPath) + esbuild-bundled app CSS into /index.css with composite source maps
• File watcher — Chokidar waits for ready before attaching handlers; native watcher resolves 8.3 short names on Windows; polling watcher capped to prevent unbounded memory
• Debug server — lifecycle rewritten with DebugServerResources, signal handler dedup, debugServerOrigin() for URL calculation
• Browser test runner — console.* → structured log() from logging/log.ts; window casts made type-safe
• Multi-runner — validateFilteredRuntimeOutcomes() ensures matched/no-match consistency; progress tracks started (not completed) suites
• AGENTS.md — trimmed stale sections; added runtime-specific test registration pattern
• Docusaurus 3.10 with @docusaurus/faster (SWC/Rspack)
• All server templates route through getRuntime() — no direct Deno.*/process.* calls
• Playwright version centralized in base/playwright-version.ts; CI cache key hashes that file
• Node.js pinned to 24.15.0 across CI to avoid libuv regression

---

What Was Removed

• @docusaurus/remark-plugin-npm2yarn, @docusaurus/theme-mermaid, core-js-pure, marked, stale glob, memfs, all @types/d3-*
• Docs workspace from deno.json
• Legacy openBrowser / getCwd internal functions from debug-server
• isBrowser(), isDeno(), isNode() replaced by getRuntime().id in ~60+ call sites
• Silent no-ops → explicit throw in runtime adapters
• Redundant await on synchronous exit() calls
• Stale AGENTS.md sections (schema registration, naming conventions, common failures, CI)

---

Value: Unified Deno/Node.js build pipeline, production-ready file watching on Windows, reproducible CI with static analysis, structured logging for debugging, and injection-based test infrastructure that eliminates mocks.

---

Attached is an agent optimized description of the changes in this PR - AGENT_REVIEW.md