@titan-design/react-ui 0.12.1 → 0.14.0

package/src/components/custom/ActiveWork/initiative-fixture.ts

@@ -0,0 +1,104 @@
+import type { InitiativeBriefData } from './InitiativeBrief'
+import type { OpenLoop } from './OpenLoops'
+import type { TaskListItem } from './TaskRow'
+/**
+ * Real initiative state for the reader stories and tests, with fixed values
+ * (no `Date.now()`) so visual baselines stay deterministic; pair it with
+ * {@link INITIATIVE_NOW}. The brief is this initiative's own v0.1 brief, the
+ * open loops are the five it carried into 2026-09-03, and the tasks are the
+ * open ones at the time of the export.
+ */
+export const INITIATIVE_BRIEF_FIXTURE: InitiativeBriefData = {
+  slug: 'active-work',
+  title: 'active-work \u2014 durable workspace state',
+  state: 'focused',
+  rank: 1,
+  shipTarget: '2026-Q3',
+  updated: '2026-07-12',
+  body: "# active-work — durable workspace state\n\n## Why this exists\n\nEngineering work spans days; Claude Code sessions don't. Every handoff between sessions, machines, or agents loses context unless something durable holds it. `active-work` is that something — plain files per initiative (brief, handoff, tasks, sessions, artifacts) under `$XDG_DATA_HOME/active-work/<slug>/`, exposed through a CLI (`aw`), an MCP server, an HTTP daemon, and a Claude skill so any surface reads or writes the same source of truth.\n\n## v0.1 architecture (what shipped this session)\n\n- **Single npm package** `@hjewkes/active-work` (scoped, public, MIT)\n- **Shared zod-typed command registry** — CLI dispatcher (commander), MCP server (`@modelcontextprotocol/sdk`), and HTTP daemon (hono) all consume the same `src/registry/` module\n- **36 commands** across lifecycle / focus-pause / tasks / sessions / sources / artifacts / discover / open / edit / lint / mcp lifecycle / setup / uninstall\n- **Long-running daemon** (`aw mcp serve`) — REST `/rpc/:name`, MCP-over-HTTP `/mcp`, `/health`, `/version`, single-file React dashboard at `/ui` (203KB gzip 64KB), bound to `127.0.0.1:7400`\n- **Skill auto-installed** to `~/.claude/skills/active-work/` via `scripts/postinstall.js`\n- **Schemas** for brief / task / session / artifacts validated on every write; `coerceDates` at the gray-matter and yaml-io seams normalizes YAML 1.2 timestamp coercion\n\n## Major decisions made this session\n\n- **Drop INDEX.md** — picker enumerates `<activeRoot>/*/brief.md` directly; `aw list` formats on demand\n- **Split the old monolithic handoff** into brief.md (frontmatter + slow prose), handoff.md (current-state prose), tasks/*.yml (per-file structured), sessions/*.md (one per session), artifacts.yml (PRs/branches/stashes)\n- **Drop `kind`, `priority`, `health`, `depends_on`** — state enum collapsed to `focused (with rank) | backburner | paused | done`; severity is per-task; health surfaces via task notes; workstreams are independent\n- **Tasks are per-file YAML** with sequential per-initiative IDs (Jira-style: `AW-1`, `AW-2`)\n- **Sessions are per-file** in `sessions/`; bootstrap reads the most recent canonical\n- **Mixed edit policy** — prose docs editable directly; structured files (tasks, artifacts, brief frontmatter) CLI-only\n- **Discover non-interactive** — emits JSON list; Claude orchestrates triage via `aw fold/drop/track`\n- **Daemon supervision opt-in** — `--detach` for now; launchd plist deferred (AW-2)\n- **Concurrency** — atomic write + flock per-initiative; one Claude session per initiative\n\n## What got cut from v0.1\n\n- WebSocket file-event broadcasts to dashboard (AW-3)\n- launchd plist install/uninstall (AW-2)\n- Linux/Windows support (AW-1 covers Linux)\n- Auto-archive of done tasks (AW-8)\n\n## Stakeholders\n\n- @hjewkes — owner / sole user\n\n## Open questions / risks\n\n\n…",
+}
+
+export const INITIATIVE_LOOPS_FIXTURE: OpenLoop[] = [
+  {
+    ref: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep#n1',
+    kind: 'prose',
+    text: 'Decide the fate of the 7 independent unmerged titan-design lines of work: feat/TD-velocity-primitives (29 commits, subsumes 7 branches), feat/TD-unified-lab (47, subsumes surface-exploration-stories), lab/active-work-dashboard (10 / 39k lines, worktree-backed), chore/TD-arch-graph-refresh (1), feat/TD-velocity-strip-set-types (1), fix/TD-color-stories-current-system (1, PR #102 closed), agent/TD-07/design-pass (7, PR #135 closed). The 8 contained branches can be deleted losing nothing.',
+    sessionFile: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep',
+    openedAt: '2026-08-28T13:21:27Z',
+  },
+  {
+    ref: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep#n3',
+    kind: 'pr',
+    text: 'Four other titan-design PRs sit open and unreviewed: #100 TD-maturity-taxonomy, #101 TD-mobile-candidates, #103 TD-r2-s4s5-candidates, #116 live-wall-empty-states. All MERGEABLE, all REVIEW_REQUIRED.',
+    sessionFile: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep',
+    openedAt: '2026-08-28T13:21:27Z',
+  },
+  {
+    ref: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep#n4',
+    kind: 'task',
+    targetRef: 'AW-116',
+    text: 'AW-116: artifacts.yml still carries a worktree path that artifact status reports present:false and no CLI command can remove.',
+    sessionFile: '2026-08-28-1244-2026-08-28-loop-verification-and-branch-sweep',
+    openedAt: '2026-08-28T13:21:27Z',
+  },
+  {
+    ref: '2026-08-29-0850-2026-08-29-aw22-f1-pr157-merge#n1',
+    kind: 'task',
+    targetRef: 'AW-22',
+    text: 'AW-22 needs T2 Task List, M1 Session Reader and M2 Initiative Reader hardened into packages/ui before it can close — F1 and T1 have landed, the other three specimens are still lab-only.',
+    sessionFile: '2026-08-29-0850-2026-08-29-aw22-f1-pr157-merge',
+    openedAt: '2026-08-29T12:59:33Z',
+  },
+  {
+    ref: '2026-08-29-0850-2026-08-29-aw22-f1-pr157-merge#n2',
+    kind: 'task',
+    targetRef: 'AW-117',
+    text: 'AW-117: titan-design main is 194 files prettier-unclean and its ci.yml Format Check is continue-on-error:true. Sequence the reformat after the unmerged-branch triage, since it will collide with every open branch.',
+    sessionFile: '2026-08-29-0850-2026-08-29-aw22-f1-pr157-merge',
+    openedAt: '2026-08-29T12:59:33Z',
+  },
+]
+
+export const INITIATIVE_TASKS_FIXTURE: TaskListItem[] = [
+  {
+    slug: 'active-work',
+    id: 'AW-6',
+    title: 'Linear / Jira / Slack discovery sources',
+    priority: 6,
+    severity: 'low',
+    estimate: 13,
+    updated: '2026-05-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-7',
+    title: 'Read-write dashboard (mark tasks done from /ui, reorder via drag)',
+    priority: 7,
+    severity: 'low',
+    estimate: 8,
+    updated: '2026-05-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-13',
+    title:
+      'First npm publish: trigger release.yml; verify @hjewkes/active-work@0.1.0 installable via npm i -g',
+    priority: 13,
+    severity: 'high',
+    estimate: 1,
+    updated: '2026-07-02',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-22',
+    title:
+      'Read-only dashboard prototypes (titan specimens): portfolio, task list, session reader, initiative reader, file-history explorer',
+    priority: 20,
+    severity: 'low',
+    estimate: 8,
+    updated: '2026-07-12',
+  },
+]
+
+/** The reference instant the stories and tests measure ages from (2026-09-03 12:00Z). */
+export const INITIATIVE_NOW = new Date('2026-09-03T12:00:00Z').getTime()

package/src/components/custom/ActiveWork/session-fixture.ts

@@ -0,0 +1,267 @@
+import type { SessionSummary } from './SessionListItem'
+import type { TaskListItem } from './TaskRow'
+/**
+ * A hand-trimmed slice of real active-work session logs, used by the session
+ * reader stories and tests. Fixed values (no `Date.now()`) so visual baselines
+ * stay deterministic; pair it with {@link SESSION_NOW}.
+ *
+ * Five canonical sessions of varied length (six minutes to fifteen hours), plus
+ * one synthesized ad-hoc session (second in the list) so the track's other
+ * state renders. Ids
+ * are the 8-character prefixes the session files use. The bodies are the real
+ * markdown, so the auto-linker meets real `AW-nn`, `[[name]]`, `#123`, bold and
+ * code spans.
+ */
+export const SESSION_FIXTURE: SessionSummary[] = [
+  {
+    id: '34db5555',
+    filename: '2026-07-12-1347-34db5555-1.md',
+    started: '2026-07-12T13:47:56Z',
+    ended: '2026-07-12T14:52:21Z',
+    track: 'canonical',
+    title:
+      'Shipped AW-17 + AW-18 + AW-19 + AW-20 — cwd→initiative resolution, worktree registration, mid-session prompt re-seed, and ad-hoc session framing',
+    body: "# Shipped AW-17 + AW-18 + AW-19 + AW-20 — cwd→initiative resolution, worktree registration, mid-session prompt re-seed, and ad-hoc session framing\n\nUser redirected from the owner-gated backlog (AW-1 Ubuntu smoke-test, AW-13 npm\npublish) to a new feature: make `aw` / `active-work open` figure out which\ninitiative to bootstrap from the current directory instead of always showing the\npicker. Built, reviewed, fixed, merged (#49). Then closed the follow-up gap it\nexposed (no CLI to register a worktree on an existing initiative) with AW-18\n(#50), and dogfooded it on this initiative. `main` green (535/535), no open PRs.\n\n## What shipped (AW-17, PR #49)\nThe inverse of the existing `resolveCwdHint` (initiative → cwd): now cwd →\ninitiative. With no slug, `open` matches the caller's cwd against every brief's\n`worktrees[*].path` and bootstraps the containing initiative; nested worktrees\nresolve to the deepest match; no match or a cross-initiative tie falls back to\nthe picker.\n\n- `open --cwd <dir>` sets the resolution dir; `--pick` (on both `open` and `aw`)\n  forces the picker. Result carries `resolved_from: \"slug\" | \"cwd\"`; `aw` prints\n  a dim \"matched current directory\" note.\n\n## Review-driven fixes (2nd commit, before merge)\nAn Explore-agent review of the diff caught four real issues, all fixed:\n1. **`aw --pick` was documented but errored** — the launcher rejects any\n   `-`-prefixed arg and `runOpen` never forwarded flags. Launcher now parses\n   `--pick` and forwards it.\n2. **Daemon/MCP footgun** — the command read ambient `process.cwd()`, so a no-arg\n   MCP `open` would match against the *daemon's* cwd. Moved the cwd source to\n   `CommandContext.cwd`, populated only by the CLI dispatcher and `aw` launcher\n   (the user's shell cwd). Daemon/http leave it undefined → no-arg reverts to\n   picker; MCP callers opt in by passing `cwd`.\n3. **Symlinks** — `process.cwd()` returns the realpath on macOS (`/var` →\n   `/private/var`) while briefs store the un-resolved form, so lexical matching\n   missed (caught in my own E2E). Now `canonicalize()` (realpath, lexical\n   fallback for nonexistent paths) runs on both sides.\n4. **Wrong launch dir** — a cwd-resolved open still used the brief's *default*\n   worktree as `cwd_hint`. Now it launches in the matched worktree.\n   Also: relative worktree paths are skipped (can't compare to an absolute cwd).\n\nConfirmed sound by the review: deepest-match/tie logic (`canonical.length` depth\nproxy is valid since all matches are ancestors of cwd), `isInside` (no\n`/foo/bar` vs `/foo/barbaz` false positive), `'picker' in result` narrowing.\n\n## Tests / verification\n9 new `open` tests (auto-resolve, ctx-cwd path, nested subdir, symlink, no-match\n+ daemon-no-cwd fallbacks, `--pick`, slug tagging, deepest-match, ambiguous-tie).\nFull suite 531 green. Verified E2E against the built CLI: cwd-through-symlink\nresolves, unrelated cwd → picker, `--pick` → picker.\n\n## AW-18 (PR #50) — `active-work worktree set`\nThe dogfood exposed a real gap: worktrees could only be recorded at creation\n(`new --worktree`) or via `track --worktree` — no way to add one to an existing\ninitiative. New command: `worktree set <slug> <path> [--label <label>]\n[--default]`. First worktree → default automatically; updating a\nalready-default label keeps it default (no silent demote); `--default` promotes\nand clears others. 4 tests, E2E-verified. Registered as `worktreeSet` in the\ncommand index; dotted name → `active-work worktree set` on the CLI.\n\n## Dogfood done\nRegistered this initiative's worktree:\n`active-work worktree set active-work /Users/hjewkes/Documents/projects/active-work`.\nVerified: `active-work open` (no slug) from inside the repo (even a subdir) now\nresolves `slug: active-work, resolved_from: cwd`. So `aw` from anywhere in\n`~/Documents/projects/active-work` auto-opens this initiative. The installed\n`~/.local/bin/active-work` is a symlink to the repo `dist/cli.js`, so a local\n`npm run build` is enough to pick up new commands.\n\n## AW-19 (PR #51) — `active-work prompt` + `/aw-prompt` slash command\nUser asked for a short command to print the startup prompt inside a running\nsession. `open` was unfit (JSON envelope + archive side effect). New:\n- `active-work prompt [slug]` — prints the bootstrap prompt as PLAIN TEXT,\n  cwd-resolved, side-effect-free (no archiveStaleTasks). Needed a `cli.ts` tweak:\n  a bare-string command result prints raw in human mode (only `prompt` returns a\n  string, verified). `--json` wraps it in the envelope.\n- `/aw-prompt` slash command (`claude-commands/aw-prompt.md`, `!`active-work\n  prompt $ARGUMENTS`` + `disable-model-invocation`) installs to\n  `~/.claude/commands/` via postinstall + `setup` (stepInstallCommand), removed\n  by `uninstall` (uninstallCommand). Bundled in package `files`.\n- Refactor: extracted resolveSlug/resolveSlugFromCwd/listInitiativeSlugs from\n  open.ts into `src/commands/_open-helpers.ts` so open + prompt share one impl.\n7 tests (incl. side-effect guard). Explore review: sound; fixed the flagged\npostinstall skill-source gate that also blocked command install, commented the\ndeliberate overwrite policy. Dogfood: ran postinstall → `/aw-prompt` live at\n`~/.claude/commands/aw-prompt.md`, skill refreshed. NOTE: a new slash command\nmay need a session reload to appear.\n\nSlash-command spec (for future reference): `.claude/commands/<name>.md` →\n`/<name>`; frontmatter `allowed-tools: Bash(cmd:*)`, `disable-model-invocation`;\n`` !`cmd` `` injects stdout at expansion time.\n\n## AW-20 (PR #52) — `--adhoc` session framing\n\n…",
+  },
+  {
+    id: 'adhoc-9f3c2a10',
+    filename: '2026-07-10-1602-9f3c2a10-adhoc-doc-pass.md',
+    started: '2026-07-10T16:02:00Z',
+    ended: '2026-07-10T16:31:00Z',
+    track: 'adhoc',
+    title: 'Ad-hoc: README pass while AW-17 was in review',
+    body: '# Ad-hoc: README pass while AW-17 was in review\n\nTightened the install section and re-linked [[setup-walkthrough]]. No task moved; AW-17 stays with its reviewer.\n\n- `active-work setup` copy now names the launchd step\n- Dropped a stale reference to #42',
+  },
+  {
+    id: '1c51749e',
+    filename: '2026-07-02-0453-1c51749e-1.md',
+    started: '2026-07-02T04:53:48Z',
+    ended: '2026-07-02T20:09:05Z',
+    track: 'canonical',
+    title: 'Shipped AW-3 + AW-5, aligned repo config, reworked merge permissions',
+    body: '# Shipped AW-3 + AW-5, aligned repo config, reworked merge permissions\n\nA long session: two backlog features merged, plus a chunk of GitHub/harness\nworkflow setup. `main` clean, 521/521 green, no open PRs.\n\n## Features shipped\n- **AW-3 (#47) — live-reload dashboard.** SSE (`GET /events`) over raw WebSockets\n  — one-way push, zero new deps, native `EventSource` reconnect (keeps AW-11\'s\n  dep trim). Daemon `EventHub` fans `watchTree` (portable manual-recursive\n  `fs.watch`, sync initial attach) file events to `/ui`, which refetches within\n  ~1s; sidebar live dot. **Bonus fix:** `dashboardDir` assumed a `dist/server/`\n  layout `tsup` never emits, so packaged installs had *always* served the "not\n  built" placeholder — `/ui` never rendered the real dashboard. Now probes\n  bundled/legacy/dev layouts. Verified via integration test + manual prod run.\n- **AW-5 (#48) — `active-work sync`.** Auto-commit dirty tree → `git pull\n  --rebase` → `git push`. Guards not-a-repo/no-upstream/detached-HEAD; conflicts\n  surface with file list + continue/abort commands, left in place (local work\n  committed first). `rebased` derived from HEAD movement, not git wording.\n  Verified end-to-end with a bare remote + two clones (commit+push, clean\n  rebase-integrate, conflict + `rebase --abort` recovery). Also de-flaked the\n  AW-3 file-watch late-created-dir test (fixed sleeps → poll-until-observed; 8\n  clean full-suite runs after).\n\nBoth merged via `gh pr merge --squash --admin --delete-branch` (owner authorized;\n#47 was blocked by the auto-mode classifier first, then merged on explicit ask).\n\n## GitHub repo config aligned to `brain`\nBranch protection on `active-work` main now matches the house policy: required\nstrict `check`, no required reviews, admins overridable, no force-push (only diff\nwas a redundant 0-approval review block, removed). Workflow perms were already\nuniform (read / no-PR-creation) across all repos. Saved\n`github-repo-config-standard` memory (template repo: brain).\n\n## Merge permissions + mode rework\n- Root-caused the self-merge block: `permissions.allow` already had `Bash(*)`, so\n  the block was the **auto-mode classifier** (`defaultMode: auto`), not the\n  permission layer.\n- Owner then chose to **turn auto mode OFF**: `~/.claude/settings.json` now\n  `defaultMode: "default"` with a broadened allow list (`Bash(*)`, Edit, Write,\n  Read, WebFetch, WebSearch, active-work + brain MCP). Removed the dead\n  snake_case `default_mode: bypassPermissions` key.\n- **"Only when green" is now structural** — branch protection\'s required strict\n  `check` means a plain `gh pr merge --squash --delete-branch` is rejected unless\n  CI is green, independent of mode. `--admin` bypasses it → behavioral restraint\n  only (use on explicit request). Tradeoff flagged: with the classifier off,\n  `Bash(*)` is fully unguarded.\n- `autoMode.allow` merge rules kept but now only apply in plan mode\n  (`useAutoModeDuringPlan` defaults true).\n\n## AW-13 decision\nOwner chose to keep Actions perms at the house default (no auto-PR-creation), so\nthe changesets Version PR won\'t auto-create. Publish path = **local one-time\nbootstrap** (`npm login` → `pnpm build` → `npm publish`), then configure the\nnpmjs.com trusted publisher for future OIDC. Task note + handoff updated.\n\n## State for next session\n- AW-3, AW-5 **done**. main clean, 521 green.\n- Open: AW-13 (owner bootstrap publish), AW-1 (Ubuntu smoke-test — can\'t do on\n  macOS), AW-7 (read-write dashboard), AW-6 (external discovery, needs tokens).\n- Reload Claude Code (or `/config`) for the permission-mode change to fully take.',
+  },
+  {
+    id: '151ef7a2',
+    filename: '2026-07-01-1833-151ef7a2.md',
+    started: '2026-07-01T18:33:01Z',
+    ended: '2026-07-02T04:45:35Z',
+    track: 'canonical',
+    title: 'Backlog blitz — shipped 10 tasks, cleared PR backlog, prepped npm publish',
+    body: '# Backlog blitz — shipped 10 tasks, cleared PR backlog, prepped npm publish\n\nA long, high-throughput session: cleared the open-PR backlog, then shipped the\nbulk of the backlog. 13 PRs merged (#34–#46); main is clean, no open PRs or\nstray branches. Tests grew 440 → 498.\n\n## Merged / closed this session\n- **Backlog PRs**: #34 (session.record --body-file) and #35 (channels flag) reviewed + merged.\n- **AW-16** closed — resolved by #34 (reject-both instead of the spec\'s "body-file wins"; deliberate).\n- **AW-15** (#36) — live PR/branch artifact state; dropped stale `prs[]`; v1→v2 migrator logs dropped PRs to `.migrations.log` (does NOT fold into notes — deliberate divergence from done_when, flagged).\n- **AW-1** (#37) — Linux systemd user-unit supervision. Engineering LANDED but task stays OPEN pending Ubuntu 24.04 smoke-test (can\'t run on macOS). CI caught a Linux-only bug: supervision failure was aborting `setup`; fixed to degrade to a non-fatal warning.\n- **AW-9** (#38) — HOME sandbox setupFile + CI sandbox so no test can touch the real home. Key gotcha: under Vitest\'s threads pool a runtime `process.env.HOME` write does NOT reach libuv\'s `os.homedir()`; fixed by overriding `os.homedir()` to read `process.env.HOME` dynamically.\n- **AW-2** (#39) — macOS launchd supervision, mirroring AW-1. Added a `getSupervisor(platform)` dispatcher (systemd | launchd). Smoke-tested end-to-end on this Mac (launchctl loads agent → daemon serves /health → uninstall clean). NOTE: the HOME sandbox does NOT cover the per-user launchd domain, so all launchd tests inject a fake spawn and the setup E2E is pinned to a supervisor-less platform.\n- **AW-4** (#40) — `active-work doctor` health-check (node/active-root/daemon/mcp-registration/skill/supervision). Smoke test caught a false "not registered" — the check now accepts both `@hjewkes/active-work` and `active-work` mcpServers keys.\n- **AW-11** (#41) — trimmed runtime deps 23 → 13 (moved react/react-dom/react-native-web to devDeps; removed @titan-design/react-ui, lucide-react, mustache, uuid, chokidar, @commander-js/extra-typings, zod-to-json-schema). Verified via `--omit=dev` tarball install.\n- **AW-14** (#43) — `gen:cli-reference` npm script.\n- **AW-12** (#44) — root-caused the "cli.test.ts flaky on first CI run" as tsx cold-start (CI ran Test before Build → pickRunner fell back to tsx). Fixed: build the CLI before the integration suite in CI so it uses dist deterministically.\n- **AW-8** (#45) — bootstrap auto-archives done tasks older than 30 days into `tasks/archive/` (preserved, out of active list); ids surfaced as a housekeeping note. Inert until tasks age.\n- **AW-10** (#46) — removed redundant `normalizeDates`/`normalizeDateFields` workarounds (readRawFrontmatter already coerces); migrated audit/_focus-helpers/worktree-set-default to `readFrontmatter`. `readRawFrontmatter` kept for lint/set/touch/task-add.\n\n## AW-13 (npm publish) — PREPPED, owner actions remain\nSwitched to **npm OIDC trusted publishing** (PR #42) instead of an NPM_TOKEN secret. `release.yml` now drops NPM_TOKEN, adds `npm install -g npm@latest` (needs npm ≥ 11.5.1), and `publishConfig.provenance` removed (automatic under trusted publishing; also unblocks local bootstrap). Artifact verified: build clean, tarball 17 files/240kB, clean `--omit=dev` install runs the CLI.\n\nOwner actions (in AW-13 notes):\n1. Bootstrap once — a trusted publisher can\'t be registered for a package that doesn\'t exist yet: `npm login` → `pnpm build` → `npm publish`.\n2. Configure trusted publisher on npmjs.com (org HJewkes, repo active-work, workflow release.yml, action `npm publish`).\n3. Enable Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests" (the changesets Version PR step currently fails without it — independent of publishing).\nThen push to main → auto "Version Packages" PR → merge publishes via OIDC. Version will be 0.2.0 (three pending changesets from 0.1.0), unless a local bootstrap publishes 0.1.0 first.\n\n## Open tasks remaining\n- AW-1 (smoke-test gate), AW-13 (owner actions), and four large low-priority features: AW-3 (WebSocket broadcasts), AW-5 (aw sync), AW-6 (Linear/Jira/Slack discovery), AW-7 (read-write dashboard).\n\n## Method note\nManual review + smoke tests repeatedly caught defects that green CI alone missed: the AW-15 migration mismatch, the AW-1 Linux-only setup abort, launchd test-hygiene (real launchd domain), the doctor false-negative, and the dependency bloat.',
+  },
+  {
+    id: '874f2d4e',
+    filename: '2026-07-01-1617-874f2d4e.md',
+    started: '2026-07-01T16:17:40.917Z',
+    ended: '2026-07-01T16:51:35Z',
+    track: 'canonical',
+    title: 'Fix: channels flag swallowing the bootstrap prompt',
+    body: '# Fix: channels flag swallowing the bootstrap prompt\n\nDebugged and fixed the broken "channels" support in the `aw` launcher.\n\n## Symptom\n`aw voltras-workspace` collided the channel name with the bootstrap prompt and\nfailed to start Claude Code.\n\n## Root cause\n`aw` spawned `claude --dangerously-load-development-channels <target> <prompt>`.\nThe flag is real but hidden from `--help`; its value is **variadic**\n(`<servers...>`), confirmed in the v2.1.197 binary strings. A variadic option\ngreedily consumes every following non-`-` token, so it ate the channel target\n*and the trailing prompt* as channel targets — leaving the real `[prompt]`\npositional empty and treating the prompt text as a bogus channel name.\n\nAn earlier `-p` probe appeared to "work" only because `-p` (leading `-`) halted\nthe variadic before the prompt; real interactive launches have no such stop.\n\n## Fix (branch `fix/aw-channels-prompt-collision`, commit 3ab6d4e → rebased to fcca639; PR #35)\n- Assemble argv as `[<flag> ...targets, \'--\', prompt]` — the `--` terminator\n  stops the variadic so the prompt is parsed as the positional `[prompt]`.\n- Collapse to a single variadic flag carrying all targets.\n- Extracted argv assembly into side-effect-free `src/launcher-args.ts`\n  (`buildChannelArgs`, `buildClaudeArgs`) — `aw.ts` runs `main()` on import, so\n  importing it in a test would fire the launcher.\n- Committed the previously-uncommitted channels wiring too: brief schema\n  `channelTarget` + `open` command emitting `channels`.\n\n## Verification\n- New regression test `__tests__/aw-launcher.test.ts` (7 cases, incl. the\n  `--`-terminator regression).\n- `typecheck` clean; `eslint` clean on changed files; full unit suite 420 passed.\n- `build:cli` rebuilt `dist/aw.js` (installed binary) — fix confirmed present.\n- Verified `claude ... -- "<prompt>"` honors `--` as an option terminator.\n\n## Session-record bugs — already fixed elsewhere\nWhile recording this session, `active-work session record` rejected `--body-file`\n(advertised but never wired; schema required `body`) and required an explicit\n`--track` (help claimed a `canonical` default the schema lacked). I re-derived a\nfix, then found the identical fix already existed on branch\n`fix/session-record-body-file-and-track-default` (commit 83e1fa1) with more tests\n— so I **discarded my duplicate** rather than commit it.\n\n## PR reshuffle (Approach B — drop-gate)\nDiscovered local `main` was 2 commits ahead of `origin/main`, unpushed:\n`80634b0` (aw launcher split — a real dependency of the channels fix) and\n`9cf1165` (always invoke main / drop isDirectRun gate). `9cf1165` was a\n*competing* resolution of the direct-run problem vs open PR #33\n(`fix/cli-direct-run-symlinks`, `2bcb071`, bin-shim symlink detection) — both\ntouch `src/cli.ts`; only one can land. Owner chose **Approach B (drop-gate)**.\n\nActions taken:\n- Owner pushed local `main` → `origin/main` (`b727b6b..9cf1165`). Safety\n  classifier blocks me from pushing the default branch, so this was manual.\n- **PR #35** — channels fix. Rebased off the AW-15 stack onto `main`\n  (`3ab6d4e` → `fcca639`); cherry-picked cleanly (open.ts auto-merged). Now a\n  single clean commit, no AW-15 baggage. base=main, MERGEABLE.\n- **PR #34** — session-record fix. Rebased onto `main`, dropping the superseded\n  `2bcb071` symlink commit (`83e1fa1` → `9a65e31`), force-pushed, base switched\n  from the #33 branch to `main`. Single commit, MERGEABLE. 12 session tests green.\n- **PR #33** — closed as superseded by `9cf1165` (drop-gate), with a comment.\n\n## Not done / follow-up\n- **Live smoke-test:** after #35 merges, owner should run `aw voltras-workspace`\n  — I can\'t execute `--dangerously-load-development-channels` (safety classifier).\n- **CI gate:** required status check `check` must go green on #34 and #35 before\n  merge (branch protection).\n- The AW-15 launcher commits `80634b0`/`9cf1165` are now on `main` outside of a\n  PR (pushed directly, bypassing review) — noted for the record.',
+  },
+  {
+    id: 'aw-1-sys',
+    filename: '2026-05-13-1927-aw-1-sys.md',
+    started: '2026-05-13T19:27:21Z',
+    ended: '2026-05-13T19:33:13Z',
+    track: 'canonical',
+    title: 'AW-1 — Linux systemd supervision (engineering complete)',
+    body: '# AW-1 — Linux systemd supervision (engineering complete)\n\nImplemented user-level systemd supervision for the `active-work` daemon. All\nunit tests pass; Ubuntu 24.04 smoke-test is the only remaining gate before\nclosing AW-1.\n\n## What changed\n\n- **New module `src/setup/supervision-systemd.ts`** — single home for the\n  unit template, install/uninstall steps, and the `isUnitActive` probe.\n  - `renderUnit({ cliEntry, port?, nodeBin? })` emits a `Type=simple` unit\n    (`[Unit]/[Service]/[Install]`) with `Restart=on-failure`,\n    `RestartSec=5`, `WantedBy=default.target`, and `ExecStart=<node>\n    <cli> mcp serve [--port N]`. Paths with whitespace get quoted.\n  - `stepInstallSupervision` writes the unit to\n    `~/.config/systemd/user/active-work.service`, then runs\n    `systemctl --user daemon-reload` + `systemctl --user enable --now\n    active-work.service`. Idempotent: same content → `done:false /\n    refreshed`. systemctl-missing returns a soft-skip with manual\n    instructions; daemon-reload exit ≠ 0 is a hard failure.\n  - `uninstallSupervision` runs `disable --now`, removes the unit file,\n    then `daemon-reload`. Tolerates systemctl missing.\n  - `isUnitActive` probes `systemctl --user is-active --quiet`. Returns\n    false on non-Linux without spawning anything.\n\n- **Wired into `src/setup/steps.ts`**:\n  - New `stepSupervision` wraps the install with the `--yes`/confirm\n    prompt pattern other setup steps use; on non-Linux returns a\n    platform-aware skip.\n  - Inserted into `runSetup` between MCP register and daemon start.\n  - `stepStartDaemon` now first checks `isUnitActive(deps)` on Linux and\n    skips the `--detach` spawn when systemd already owns the daemon.\n  - `runUninstall` calls `uninstallSupervision` (Linux-gated) before the\n    daemon-stop step, with its own confirm prompt.\n  - `STEP_NAMES.SUPERVISION` exported alongside the other step names.\n\n- **Tests**:\n  - New `__tests__/setup/supervision-systemd.test.ts` (16 tests):\n    `renderUnit` shape + port + space-quoting, `getUnitPath`,\n    `stepInstallSupervision` darwin no-op / linux write+reload+enable /\n    idempotent refresh / systemctl-missing fallback / daemon-reload\n    failure, `uninstallSupervision` darwin no-op / absent / disable+remove,\n    `isUnitActive` non-linux / 0 / non-zero.\n  - Extended `__tests__/setup-steps.test.ts` with `stepSupervision` darwin\n    no-op + linux cancel paths, and a `stepStartDaemon` test confirming\n    it issues only the `systemctl is-active` probe (and no execPath spawn)\n    when the unit is active.\n\n- **Run shape**: full suite 448/448 pass, lint clean, typecheck clean\n  (`pnpm test`, `pnpm lint`, `pnpm typecheck`).\n\n## What\'s still gating AW-1\n\n- **Ubuntu 24.04 smoke-test of `active-work setup` end-to-end.** AW-1\'s\n  `done_when` calls for "smoke-tested on Ubuntu 24.04"; that requires a\n  Linux box and was not exercised from this macOS dev host. The unit\n  template was modelled after the standard user-unit spec but should be\n  verified with `systemd-analyze verify ~/.config/systemd/user/active-work.service`\n  on a real Ubuntu 24.04 install before closing the task.\n\n## Design notes worth remembering\n\n- The unit runs the daemon in the **foreground** (`mcp serve`, not\n  `mcp serve --detach`) because `Type=simple` expects the main process\n  to stay alive — `--detach` would immediately exit and systemd would\n  mark the service failed.\n- Decision: keep AW-2 (launchd plist for macOS) as a separate task even\n  though the install/uninstall shape is symmetric. AW-1 doesn\'t drag in\n  the plist work; the supervision module is namespaced\n  `supervision-systemd.ts` so a future `supervision-launchd.ts` slots in\n  alongside.\n- `stepStartDaemon` checking `isUnitActive` is the right seam (rather\n  than threading a flag through `runSetup`) because the question\n  "should we manually spawn?" is exactly "is the daemon already\n  managed?" — the probe answers it regardless of which step earlier\n  in the wizard installed the supervision.\n\n## Files touched\n\n- `src/setup/supervision-systemd.ts` (new)\n- `src/setup/steps.ts` (added `stepSupervision`, wired into\n  `runSetup`/`runUninstall`, taught `stepStartDaemon` about systemd)\n- `__tests__/setup/supervision-systemd.test.ts` (new)\n- `__tests__/setup-steps.test.ts` (added supervision + daemon-detection\n  describes)',
+  },
+]
+
+/** The reference instant the stories and tests measure ages from (2026-07-14 09:00Z). */
+export const SESSION_NOW = new Date('2026-07-14T09:00:00Z').getTime()
+
+/**
+ * The real task rows behind every id the fixture sessions mention, for the
+ * detail pane's tasks-touched table. A host resolves these from its task store;
+ * the story does the same lookup against this list.
+ */
+export const SESSION_TASK_FIXTURE: TaskListItem[] = [
+  {
+    slug: 'active-work',
+    id: 'AW-1',
+    title: 'Add Linux support: systemd unit for daemon supervision',
+    priority: 1,
+    severity: 'medium',
+    estimate: 5,
+    updated: '2026-07-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-2',
+    title: 'Add launchd plist install/uninstall to setup wizard (macOS)',
+    priority: 2,
+    severity: 'medium',
+    estimate: 3,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-3',
+    title: 'WebSocket file-event broadcasts from daemon to dashboard',
+    priority: 3,
+    severity: 'low',
+    estimate: 5,
+    updated: '2026-07-02',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-4',
+    title: 'aw doctor: health-check command (verify deps, daemon, MCP registration, skill install)',
+    priority: 4,
+    severity: 'medium',
+    estimate: 3,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-5',
+    title: 'Multi-machine git-backed sync wrapper (aw sync)',
+    priority: 5,
+    severity: 'low',
+    estimate: 8,
+    updated: '2026-07-02',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-6',
+    title: 'Linear / Jira / Slack discovery sources',
+    priority: 6,
+    severity: 'low',
+    estimate: 13,
+    updated: '2026-05-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-7',
+    title: 'Read-write dashboard (mark tasks done from /ui, reorder via drag)',
+    priority: 7,
+    severity: 'low',
+    estimate: 8,
+    updated: '2026-05-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-8',
+    title: 'Auto-archive done tasks older than N days during bootstrap',
+    priority: 8,
+    severity: 'low',
+    estimate: 2,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-9',
+    title: "Audit tests for unsafe HOME/filesystem mocking; ensure all use vi.spyOn(os, 'homedir')",
+    priority: 9,
+    severity: 'high',
+    estimate: 2,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-10',
+    title:
+      'Clean up readRawFrontmatter workarounds in commands now that gray-matter-io coerces dates',
+    priority: 10,
+    severity: 'low',
+    estimate: 2,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-11',
+    title: 'Remove @titan-design/react-ui dep — dashboard agent ended up not using it',
+    priority: 11,
+    severity: 'low',
+    estimate: 1,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-12',
+    title:
+      'Investigate occasional integration-test flakes (cli.test.ts had 5 failures on first merged run, clean on retry)',
+    priority: 12,
+    severity: 'medium',
+    estimate: 3,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-13',
+    title:
+      'First npm publish: trigger release.yml; verify @hjewkes/active-work@0.1.0 installable via npm i -g',
+    priority: 13,
+    severity: 'high',
+    estimate: 1,
+    updated: '2026-07-02',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-14',
+    title:
+      'Add gen:cli-reference script entry to package.json (generator script exists; just needs npm-run wiring)',
+    priority: 14,
+    severity: 'low',
+    estimate: 1,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-15',
+    title: 'Simplify artifacts.yml: branches/stashes only; live-pull PR + branch state',
+    priority: 1,
+    severity: 'medium',
+    estimate: 8,
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-16',
+    title: 'session record --body-file passes validation when --body is omitted',
+    priority: 6,
+    severity: 'low',
+    estimate: 1,
+    tags: ['polish', 'cli'],
+    updated: '2026-07-01',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-17',
+    title: 'open/aw: resolve initiative from cwd when no slug given',
+    priority: 15,
+    severity: 'medium',
+    estimate: 3,
+    updated: '2026-07-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-18',
+    title: 'worktree.set: register/update a worktree on an existing initiative',
+    priority: 16,
+    severity: 'low',
+    estimate: 2,
+    updated: '2026-07-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-19',
+    title: 'active-work prompt + /aw-prompt slash command for mid-session context re-seed',
+    priority: 17,
+    severity: 'low',
+    estimate: 3,
+    updated: '2026-07-12',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-20',
+    title: 'aw/open --adhoc: frame bootstrap prompt as ad-hoc work, not handoff continuation',
+    priority: 18,
+    severity: 'low',
+    estimate: 2,
+    updated: '2026-07-12',
+  },
+]

package/src/components/custom/ActiveWork/session-linkers.ts

@@ -0,0 +1,56 @@
+import type { ProseLinker } from '../Prose'
+
+/** A per-initiative task id such as `AW-22` or `TD-07.14`. */
+export const TASK_REF_PATTERN = /\b[A-Z]{2,}-\d+(?:\.\d+)?\b/
+/** An Obsidian-style `[[name]]` link into notes or memory. */
+export const WIKI_LINK_PATTERN = /\[\[[^\]]+\]\]/
+/** A bare `#123` pull-request or issue number. */
+export const PR_REF_PATTERN = /#\d+\b/
+
+/** Every distinct task id in a body, in first-seen order. */
+export function extractTaskRefs(body: string): string[] {
+  const all = body.match(new RegExp(TASK_REF_PATTERN.source, 'g')) ?? []
+  return Array.from(new Set(all))
+}
+
+/** Task ids read in the brand colour and, when a handler is given, open the task. */
+export function taskRefLinker(onPress?: (id: string) => void): ProseLinker {
+  return { id: 'task', pattern: TASK_REF_PATTERN, tone: 'brand', onPress }
+}
+
+/** `[[name]]` links drop their brackets and read as links; the handler receives the bare name. */
+export function wikiLinkLinker(onPress?: (name: string) => void): ProseLinker {
+  const strip = (ref: string) => ref.slice(2, -2)
+  return {
+    id: 'wiki',
+    pattern: WIKI_LINK_PATTERN,
+    tone: 'link',
+    label: strip,
+    onPress: onPress ? (ref) => onPress(strip(ref)) : undefined,
+  }
+}
+
+/** PR numbers recede rather than compete with task ids; the handler receives the number. */
+export function prRefLinker(onPress?: (number: number) => void): ProseLinker {
+  return {
+    id: 'pr',
+    pattern: PR_REF_PATTERN,
+    tone: 'muted',
+    onPress: onPress ? (ref) => onPress(Number(ref.slice(1))) : undefined,
+  }
+}
+
+export interface SessionLinkHandlers {
+  onPressTask?: (id: string) => void
+  onPressLink?: (name: string) => void
+  onPressPr?: (number: number) => void
+}
+
+/** The three linkers a session log needs, in the order they should win a match. */
+export function sessionLinkers(handlers: SessionLinkHandlers = {}): ProseLinker[] {
+  return [
+    taskRefLinker(handlers.onPressTask),
+    wikiLinkLinker(handlers.onPressLink),
+    prRefLinker(handlers.onPressPr),
+  ]
+}

package/src/components/custom/ActiveWork/task-list-fixture.ts

@@ -0,0 +1,97 @@
+import type { TaskListItem } from './TaskRow'
+
+/**
+ * A hand-trimmed slice of a real active-work backlog, used by the task-list
+ * stories and tests. Fixed values (no `Date.now()`, no randomness) so visual
+ * baselines stay deterministic — pair it with {@link TASK_LIST_NOW}.
+ *
+ * Deliberately covers the awkward rows, not just the tidy ones: an unset
+ * severity, an unset estimate, a task with more tags than the row shows, a
+ * title long enough to clip, and two tasks sharing a priority so tie-breaks are
+ * exercised.
+ */
+export const TASK_LIST_FIXTURE: TaskListItem[] = [
+  {
+    slug: 'active-work',
+    id: 'AW-22',
+    title: 'Read-only dashboard prototypes (titan specimens): portfolio, task list, session reader',
+    severity: 'low',
+    priority: 20,
+    estimate: 8,
+    tags: ['dashboard', 'titan'],
+    updated: '2026-08-29T10:00:00Z',
+  },
+  {
+    slug: 'active-work',
+    id: 'AW-86',
+    title: 'Design spike: notes-supersession (rescoped)',
+    severity: 'low',
+    priority: 20,
+    tags: ['spike'],
+    updated: '2026-08-11T09:00:00Z',
+  },
+  {
+    slug: 'relay',
+    id: 'RL-14',
+    title: 'Voice dispatch drops the initiative when the daemon restarts mid-utterance',
+    severity: 'critical',
+    priority: 3,
+    estimate: 5,
+    tags: ['voice', 'daemon', 'reliability', 'p0'],
+    updated: '2026-08-30T07:30:00Z',
+  },
+  {
+    slug: 'codewatch',
+    id: 'C-92',
+    title: 'Plugin injection delivery, evidence-framed by the injection eval',
+    severity: 'high',
+    priority: 7,
+    estimate: 13,
+    tags: ['plugin'],
+    updated: '2026-07-30T12:00:00Z',
+  },
+  {
+    slug: 'codewatch',
+    id: 'C-6',
+    title: 'npm publish the packaged distribution',
+    severity: 'medium',
+    priority: 11,
+    estimate: 2,
+    updated: '2026-06-18T16:20:00Z',
+  },
+  {
+    slug: 'titan-platform',
+    id: 'TP-16',
+    title: 'Nativewind-free token-only export subpath',
+    priority: 14,
+    estimate: 3,
+    tags: ['tokens'],
+    updated: '2026-08-01T04:01:00Z',
+  },
+  {
+    slug: 'home-assistant',
+    id: 'HA-3',
+    title: 'Rebuild the bedroom automation after the Zigbee coordinator swap',
+    severity: 'medium',
+    priority: 25,
+    estimate: 5,
+    tags: ['zigbee'],
+    updated: '2026-05-12T00:00:00Z',
+  },
+  {
+    slug: 'brain',
+    id: 'BR-41',
+    title: 'Collapse the duplicate embedding path',
+    severity: 'high',
+    priority: 9,
+    estimate: 8,
+    tags: ['perf', 'index'],
+    updated: '2026-08-27T18:45:00Z',
+  },
+]
+
+/**
+ * Fixed reference "now" for the fixture (2026-08-30T12:00:00Z). Pass to
+ * `TaskTable`'s `now` so every age label is stable across runs.
+ */
+export const TASK_LIST_NOW = new Date('2026-08-30T12:00:00Z').getTime()

package/src/components/custom/CircularTimer/CircularTimer.stories.tsx

@@ -1,11 +1,16 @@
 import type { Decorator, Meta, StoryObj } from '@storybook/react-vite'
 import { View, Text, Pressable } from 'react-native'
 import { CircularTimer } from './CircularTimer'
+import { greyRamp, primitiveColors } from '../../../theme/tokens/primitives'
+import { getSemanticColors } from '../../../theme/tokens/semantic'
+import { alpha } from '../../../utils/colors'
+
+const t = getSemanticColors('dark')
 
 const meta: Meta<typeof CircularTimer> = {
-  title: 'Custom/CircularTimer',
+  title: 'Components/Molecules/CircularTimer',
   component: CircularTimer,
-  tags: ['autodocs'],
+  tags: ['autodocs', 'status:candidate', '!status:review'],
   parameters: {
     docs: {
       description: {
@@ -15,7 +20,8 @@ const meta: Meta<typeof CircularTimer> = {
           '`durationMs` + `elapsedMs`) and composes `CircularProgress` for the arc (`down` drains, ' +
           '`up` fills). On completion a `down` timer with a `doneLabel` fills fully in `doneColor` ' +
           'and reads the label (e.g. "GO"). Pass `controls` to render buttons below the ring, or ' +
-          "`fill` to make it responsive to its container. `RestTimer`'s `ring` variant wraps this.",
+          "`fill` to make it responsive to its container. `RestTimer`'s `ring` variant wraps this." +
+          '\n\nComposes **CircularProgress** over the `useTimer` hook.',
       },
     },
   },
@@ -31,7 +37,7 @@ export default meta
 type Story = StoryObj<typeof CircularTimer>
 
 const dark: Decorator = (Story) => (
-  <View style={{ padding: 32, alignItems: 'center', backgroundColor: '#0E0E0E' }}>
+  <View style={{ padding: 32, alignItems: 'center', backgroundColor: t['background-frame'] }}>
     <Story />
   </View>
 )
@@ -63,13 +69,13 @@ export const DoneWithLabel: Story = {
 const DemoButton = ({ label }: { label: string }) => (
   <Pressable
     style={{
-      backgroundColor: 'rgba(255,255,255,0.06)',
+      backgroundColor: alpha(primitiveColors.white, 0.06),
       paddingVertical: 8,
       paddingHorizontal: 20,
       borderRadius: 8,
     }}
   >
-    <Text style={{ color: '#DADADA', fontSize: 11, fontWeight: '600' }}>{label}</Text>
+    <Text style={{ color: greyRamp[200], fontSize: 11, fontWeight: '600' }}>{label}</Text>
   </Pressable>
 )
 

package/src/components/custom/DateTime/DateTime.stories.tsx

@@ -5,7 +5,8 @@ import { DateTime, type DateTimeFormat } from './DateTime'
 const meta: Meta<typeof DateTime> = {
   title: 'Components/Molecules/DateTime',
   component: DateTime,
-  tags: ['autodocs'],
+  parameters: { docs: { description: { component: 'Composes **Typography**.' } } },
+  tags: ['autodocs', 'status:candidate', '!status:review'],
   argTypes: {
     format: {
       control: 'select',

package/src/components/custom/DateTime/DateTime.test.tsx

@@ -56,7 +56,9 @@ describe('DateTime', () => {
   })
 
   it('includes seconds when seconds is set', () => {
-    render(<DateTime value={new Date(2024, 0, 1, 16, 12, 7)} format="time" hour12={false} seconds />)
+    render(
+      <DateTime value={new Date(2024, 0, 1, 16, 12, 7)} format="time" hour12={false} seconds />
+    )
     expect(screen.getByText('16:12:07')).toBeInTheDocument()
   })