Repository navigation
Description
Finding
pkgs/id/WEB.md and pkgs/id/ARCHITECTURE.md still describe the id web UI as HTMX-based, but HTMX was removed in the Datastar migration (verified at main HEAD e561ab58 by queue triage of #1073):
pkgs/id/WEB.mdline 24: "File Browser: HTMX-powered listing with search, filtering, bulk operations"; line 46: architecture diagram labels the web layer "HTMX"; line 247: "/api/files— File list (HTMX partial)".pkgs/id/ARCHITECTURE.mdline 14: diagram box "Axum + HTMX + ProseMirror".
Current reality at HEAD: no hx-* attributes or HX-Request handling anywhere in the repo; pkgs/id/web/package.json depends on @starfederation/datastar ^1.0.0-beta.11, Tailwind CSS v4 and DaisyUI v5; pkgs/id/web/src/main.ts imports the Datastar SDK and handles SSE-based navigation client-side.
Scope
Update the HTMX references in pkgs/id/WEB.md and pkgs/id/ARCHITECTURE.md to describe the current Datastar + Tailwind/DaisyUI architecture (client-side navigation in web/src/navigation.ts / main.ts; no Rust DatastarResponse builder was adopted). Docs only — no code changes.
Acceptance criteria
- No HTMX claims remain in
pkgs/id/WEB.mdorpkgs/id/ARCHITECTURE.md. - The replacement text matches the code at HEAD (Datastar SDK in the TS client, Tailwind/DaisyUI styling, WebSocket endpoints unchanged).
Found by: queue worker triage of #1073 (task 2358).
Activity
developing-today commentedon Oct 28, 2026
CODE-729
dezren39 commentedon Oct 28, 2026
Intake review
pkgs/id/WEB.mdlines 24/46/247 andpkgs/id/ARCHITECTURE.mdline 14 still say HTMX, while the repo has nohx-*attributes orHX-Requesthandling and the web app runs on Datastar + Tailwind/DaisyUI. No docs fix has landed since. Confirmed live.web/src/navigation.ts/main.ts, SSE-based updates); the triage note records that no RustDatastarResponsebuilder was adopted, so do not invent one in the docs.HTMX|hx-afterwards to prove zero remain.🤖 Agent note · filed
dezren39 commentedon Nov 3, 2026
Merge pull request #4908 from developing-today/queue/7716-1789-id-web…
dezren39 commentedon Nov 3, 2026
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/low). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03