Document the Deno and Web Components platform direction

[hnordt]

Summary

• add design record 0010 proposing Deno as the primary runtime and workspace toolchain
• define Web Components as the public UI boundary and keep Preact limited to rendering
• document explicit state ownership, Declarative Shadow DOM constraints, package compatibility, security, and migration evidence
• link the proposal from design record 0003 and add it to the design-record index

Why

The package-oriented monorepo direction exposed that Svelte components are easiest to reuse from Svelte applications. The proposal moves public UI contracts toward browser standards so they can be consumed from plain HTML, TypeScript, and other frameworks.

It also records why Deno is preferred over the current SvelteKit, Node.js, and npm development stack: Web Platform alignment, default-deny permissions, workspaces, and integrated TypeScript, formatting, linting, testing, and task tooling.

Impact

This is a Draft design record. It does not change runtime behavior or claim that the Deno and Web Components migration is implemented. README.md, AGENTS.md, and CONTRIBUTING.md remain canonical until the proposal is approved and corresponding implementation work is verified.

The change is classified as:

• Kernel, because the runtime migration affects public SDK contracts and must preserve SQLite, transaction, replay, recovery, and compatibility invariants
• Experience, because it changes the intended frontend, application runtime, package, and developer-tooling boundaries

AI involvement

• Tool: OpenAI Codex
• Usage: planning and documentation implementation
• Tests written by AI: none
• Overall usage level: automated

AI involvement does not replace the experienced human maintainer review required for a Kernel-classified decision.

Verification

• npm run lint
• git diff --check
• commit hook formatting through Prettier

Application tests were not run because this change is documentation-only.

Uncertainty and risks

• component composition remains intentionally unresolved pending representative implementation evidence
• Declarative Shadow DOM does not itself define hydration, event attachment, or state reconciliation
• the exact npm artifact and publication pipeline remains to be selected and tested from produced tarballs
• the Deno SQLite implementation must prove existing transaction, authorizer, failure, recovery, and compatibility behavior before Node.js is removed
• Deno permissions are process-level controls and do not replace Hyperkernel actor, capability, authorization, or extension-isolation contracts
• npm ci reported three low-severity findings in the current dependency graph; this documentation change does not alter those dependencies

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4b00141b3d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update setup guidance alongside tooling removal

In this ordered migration, step 6 removes the npm/Node/Svelte tooling before step 7 updates CI, setup instructions, and the canonical guidance. The current repository still defines npm commands and requires the SvelteKit/Node/npm stack, so the step-6 state would neither provide the promised runnable and testable path nor permit the migrated implementation under the applicable rules. Move the corresponding CI, documentation, and migration-policy updates into the same step as each tooling change.

AGENTS.md reference: AGENTS.md:L174-L185

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Define a record-level supersession path for 0003

Under the lifecycle in docs/design/README.md, a replacement moves the previous record to Legacy, but this proposal replaces only the Svelte and SvelteKit portions of 0003. That record also owns independent Web Platform, headless-UI, accessibility, and Zod decisions that 0009 neither supersedes nor restates, so marking 0003 Legacy would retire active decisions while leaving it Development would preserve contracts that directly contradict 0009. Make this a complete replacement that carries forward the unaffected decisions, or split the superseded decisions and specify the exact status transition before advancement.

Useful? React with 👍 / 👎.