jx: Instructions file for Codex

Jx Monorepo — Agent Notes

We're crafting a comprehensive web-based application suite that aims to encompass all available web platform APIs within a JSON Schema and provides a runtime, compiler, visual builder, and extension layer (content collections, search, authentication, database connectors) to facilitate website and full-application builds with this schema. Jx targets apps with accounts and data, not only brochure sites: pages are always prerendered at build time and hydrate as islands, while sessions and application data come from extension server mounts which — together with any timing: "server" state entries — compile into one generated Hono worker serving /_jx/* next to the static output whenever build.adapter is set. A project with an active mount (a non-empty data or auth section) must set one, or the build fails; with no adapter, timing: "server" entries fall back to a standalone per-page _server.js handler.

• Prefer WHATWG and ECMA standard alignment (current or emerging) for all nomenclature and architectural paradigms.
• Code in strongly typed Typescript. Ensure all linting, typechecking, and tests pass following all changes.
• Implement tests in parallel with features—use native Bun + Happy DOM and other mock API providers, as appropriate.
• Reference the general and package-specific specs (./specs) prior to planning and implementing features, update specs to reflect user requests prior to adding new features. Edit spec sections in place — never renumber headings (user docs anchor them).
• Every substantive spec edit is a release, user docs (./docs) track shipped behavior in the same change set, and plans live in plans/ and are deleted when they land. "Specs & User-Documentation Policy" below has the commands and the gates; run bun run docs:sync and bun run docs:check before finishing.
• Do not wrap Markdown source: write one paragraph per line, and make a line break that carries meaning an explicit \ hard break. bun run format:md fixes a file. Much of the tree is still wrapped from before the rule and the sweep is pending, so match the rule in what you write rather than reflowing what you touch. The full rule, and why it is not enforced yet, is in scripts/AGENTS.md.
• Use Chrome MCP to test new UI/UX changes prior to finishing the task.
• These notes are harness-neutral. Every CLAUDE.md is a one-line @AGENTS.md import of the file beside it, so Claude Code loads these notes; edit the AGENTS.md, never the stub. Claude Code additionally runs the hooks in .claude/hooks (edit validation, a Bash guard, and a docs-sync check when it stops); in any other harness, run bun run docs:sync and format what you touched with oxfmt before finishing.