{title}

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_545":546,"_547":548},"routes/_app.x.$handle.$name",{"_99":98,"_32":44,"_107":89,"_27":108,"_13":14,"_109":-5,"_11":110,"_111":112,"_113":114,"_115":116,"_117":118,"_20":-5,"_119":-5,"_120":-5,"_121":25,"_122":123,"_124":58,"_125":-5,"_126":-5,"_127":128},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_42":43,"_32":44,"_37":45,"_46":-5,"_47":25,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":58,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":82,"_83":84,"_85":86,"_87":25},"version",208,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":25,"_27":28,"_29":28},"file",{"_30":31,"_32":28,"_33":20,"_34":36,"_37":38,"_39":14,"_40":41,"_24":25},"previous",{"_30":31,"_32":28,"_33":20,"_34":35},"deleted",false,"deletedHere","path","CONTEXT.md","latestPath","fileId","eee9abe2-7bf2-11f1-803f-1607ee4eb77e","name","fileType","content","# Context — Val Issue Tracker\n\nA GitHub-flavored issue tracker, designed as a **drop-in library**: it is\nimported into any Val Town project and uses that host val's scoped SQLite\ndatabase. Table names are prefixed (`issue_tracker_*`) to avoid colliding with\nthe host's tables.\n\n## Glossary\n\n### Issue\n\nThe core unit of work. Has a title, a markdown **body** (renamed from\n`description` to match Comment and GitHub — one word, \"body\", for \"the markdown\nprose of this thing\"), a status, and metadata (creator, timestamps). Modeled\nafter a GitHub issue.\n\n### Body\n\nThe markdown prose of an Issue or a Comment. Stored as plain `TEXT`; \"it is\nmarkdown\" is a rendering contract, not a storage concern (see docs/backlog.md).\n\n### Status\n\nAn issue's lifecycle state. Exactly two values: **`open`** and **`closed`**.\nThere is no `in_progress` (removed). This mirrors GitHub, where \"not planned\" is\n_not_ a third state — see State Reason.\n\n### State Reason\n\nA nullable qualifier explaining _why_ an issue holds its current status,\nmirroring GitHub's `state_reason`. Values: `completed`, `not_planned`,\n`duplicate` (pair with `closed`), `reopened` (pairs with `open`), or `null`.\nThis is what distinguishes \"closed because done\" from \"closed because\nabandoned\". It is **auto-managed**, never set freely: creating leaves it `null`;\nclosing sets the chosen reason (`completed` default); reopening forces\n`reopened` (which distinguishes a reopened issue from a never-closed one). Valid\npairings — `open` with `null`/`reopened`, `closed` with\n`completed`/`not_planned`/`duplicate` — are guarded by a SQLite `CHECK`\nconstraint.\n\n### User (identity)\n\nAny actor — creator, comment author, assignee — is a **Val Town user**. There is\nno local users table; anyone who can make changes is logged in via Val Town\nauth. Identity is carried as the Val Town **handle** (username), not a stable id\n— renames are rare and human-readable handles need no lookup. Handles should\neventually render as links to the user's Val Town profile (see docs/backlog.md).\n\n### Assignee\n\nThe Val Town user(s) responsible for an issue. Multi-valued (a set), not single\n— an issue may have zero or more assignees. An assignee is _not_ an entity, just\na link between an issue and an existing Val Town user, stored as a bare join\ntuple (`issue_tracker_issue_assignees(issue_id, user_handle)`). Who assigned\nwhom, and when, lives in the events log — not on the row.\n\n### Comment\n\nA markdown note attached to an issue. An entity — editable, and keeps\n`created_at` + `updated_at` columns. Who authored/edited it is _not_ a column;\nthe actor is derived from the events log (the old `author` column is gone). See\nADR 0003 and ADR 0004.\n\n### Entity vs Link\n\nAn **entity** (Issue, Comment, Label) is user-authored and editable. It keeps\n`created_at` + `updated_at` as denormalized columns (needed for hot-path listing\nand \"last activity\" sorting); the **actor** behind each create/update (`*_by`)\nis _not_ stored — it is derived from the events log. A **link** (the assignee\nand block join rows) is a **bare relationship tuple** — `(issue_id, label_id)`,\n`(issue_id,\nuser_handle)`, `(blocker_id, blocked_id)` — with no audit columns at\nall; its full provenance lives in events. See ADR 0003 (amended) and ADR 0004.\n\n### Label\n\nA reusable, curated tag — a first-class entity with a unique `name` and a\n`color`, living in `issue_tracker_labels`. Applied to issues via a join\n(`issue_tracker_issue_labels`); applying means picking an existing label, not\ntyping free-form text. Deleting a label is allowed even when in use — the join\nrows cascade away and the tagged issues simply lose that label. A default set\n(`bug`, `enhancement`, `documentation`, `question`, `duplicate`) is seeded\n**once, when the labels table is first created** — never re-seeded, so user\ndeletions survive (see ADR 0001).\n\n### Blocking relationship\n\nA directed dependency between two issues in the same tracker: \"A blocks B\" means\nB depends on A. Stored as one directed edge in\n`issue_tracker_issue_blocks(blocker_id,\nblocked_id)`; \"blocks\" and \"blocked by\"\nare the same edge read from opposite ends. The block graph is a strict DAG:\n**any** edge that would create a cycle is rejected — self-edges, direct\nreciprocals (A↔B), and longer loops (A→B→C→A) alike. This is stricter than\nGitHub (which permits longer cycles) and is enforced with a reachability check\non insert (see ADR 0002).\n\n### Touch (updated_at)\n\nMutating an issue's associations — adding/removing a label, an assignee, or a\nblock edge, or adding a comment — updates that issue's `updated_at`, exactly as\nediting the issue itself does. `updated_at` reflects \"last activity on this\nissue\", not just edits to its own columns.\n\n### Blocked (derived)\n\nAn issue is _blocked_ iff at least one of its blockers is still `open`. This is\nnever stored — it is computed from the edges and the blockers' status, so\nclosing a blocker automatically unblocks its dependents. Blocked-ness is\ninformational: it does **not** prevent an issue from being closed.\n\n### Event\n\nAn append-only record of one change, in a single polymorphic table\n(`issue_tracker_events`): `id`, `event_type`, `entity_id`, `actor`, `data`,\n`event_timestamp`. `event_type` is `.` where entity ∈ {issue,\ncomment, label} and verb ∈ {created, updated, deleted}. The events log is the\n**source of truth for provenance and history**; live tables hold only current\nstate. Grammar:\n\n- **Boundary events snapshot full state.** `*.created` → the entity's full\n initial state; `*.deleted` → its full final state (so a hard-deleted row\n leaves a complete tombstone).\n- **`*.updated` carries a field delta:** `{ update_target, from, to }`.\n Associations are modelled as `issue.updated` with `update_target` ∈ {label,\n assignee, blocks, blocked_by} and `from`/`to` using **`null ↔ value`** (null→X\n = added, X→null = removed). A block edge writes **one** event, on the acting\n issue.\n\nOne event per changed field: closing an issue emits two events (`status` and\n`state_reason`), sharing one actor and timestamp. See ADR 0004.\n\n### Actor\n\nThe Val Town handle that performed a change, stored on each event. This is the\nonly place actor/provenance lives — entities and links do not carry `*_by`\ncolumns.\n\n## Removed / rejected\n\n- **Priority** — removed entirely. Faithful to GitHub, which has no first-class\n priority field (labels/Projects only).\n- **`in_progress` status** — removed; existing rows migrate to `open`.\n","# Context — Val Issue Tracker\n\nA GitHub-flavored issue tracker, designed as a **drop-in library**: it is\nimported into any Val Town project and uses that host val's scoped SQLite\ndatabase. Table names are prefixed (`issue_tracker_*`) to avoid colliding with\nthe host's tables.\n\nIt mounts two ways: **standalone** (`export default createIssueTracker({...})`\nas a val's HTTP export, running its own OAuth) or **routed** (registered with\nan [integrations](https://www.val.town/x/nbbaier/integrations/code/) router,\nwhich owns authentication and passes the verified user and mount prefix as an\n`IntegrationContext`). The factory returns a callable Integration that serves\nboth; in routed mode the role model is fed by `ctx.user`, and a null `ctx.user`\n(ungated router) yields a read-only viewer.\n\n## Glossary\n\n### Issue\n\nThe core unit of work. Has a title, a markdown **body** (renamed from\n`description` to match Comment and GitHub — one word, \"body\", for \"the markdown\nprose of this thing\"), a status, and metadata (creator, timestamps). Modeled\nafter a GitHub issue.\n\n### Body\n\nThe markdown prose of an Issue or a Comment. Stored as plain `TEXT`; \"it is\nmarkdown\" is a rendering contract, not a storage concern (see docs/backlog.md).\n\n### Status\n\nAn issue's lifecycle state. Exactly two values: **`open`** and **`closed`**.\nThere is no `in_progress` (removed). This mirrors GitHub, where \"not planned\" is\n_not_ a third state — see State Reason.\n\n### State Reason\n\nA nullable qualifier explaining _why_ an issue holds its current status,\nmirroring GitHub's `state_reason`. Values: `completed`, `not_planned`,\n`duplicate` (pair with `closed`), `reopened` (pairs with `open`), or `null`.\nThis is what distinguishes \"closed because done\" from \"closed because\nabandoned\". It is **auto-managed**, never set freely: creating leaves it `null`;\nclosing sets the chosen reason (`completed` default); reopening forces\n`reopened` (which distinguishes a reopened issue from a never-closed one). Valid\npairings — `open` with `null`/`reopened`, `closed` with\n`completed`/`not_planned`/`duplicate` — are guarded by a SQLite `CHECK`\nconstraint.\n\n### User (identity)\n\nAny actor — creator, comment author, assignee — is a **Val Town user**. There is\nno local users table; anyone who can make changes is logged in via Val Town\nauth. Identity is carried as the Val Town **handle** (username), not a stable id\n— renames are rare and human-readable handles need no lookup. Handles should\neventually render as links to the user's Val Town profile (see docs/backlog.md).\n\n### Assignee\n\nThe Val Town user(s) responsible for an issue. Multi-valued (a set), not single\n— an issue may have zero or more assignees. An assignee is _not_ an entity, just\na link between an issue and an existing Val Town user, stored as a bare join\ntuple (`issue_tracker_issue_assignees(issue_id, user_handle)`). Who assigned\nwhom, and when, lives in the events log — not on the row.\n\n### Comment\n\nA markdown note attached to an issue. An entity — editable, and keeps\n`created_at` + `updated_at` columns. Who authored/edited it is _not_ a column;\nthe actor is derived from the events log (the old `author` column is gone). See\nADR 0003 and ADR 0004.\n\n### Entity vs Link\n\nAn **entity** (Issue, Comment, Label) is user-authored and editable. It keeps\n`created_at` + `updated_at` as denormalized columns (needed for hot-path listing\nand \"last activity\" sorting); the **actor** behind each create/update (`*_by`)\nis _not_ stored — it is derived from the events log. A **link** (the assignee\nand block join rows) is a **bare relationship tuple** — `(issue_id, label_id)`,\n`(issue_id,\nuser_handle)`, `(blocker_id, blocked_id)` — with no audit columns at\nall; its full provenance lives in events. See ADR 0003 (amended) and ADR 0004.\n\n### Label\n\nA reusable, curated tag — a first-class entity with a unique `name` and a\n`color`, living in `issue_tracker_labels`. Applied to issues via a join\n(`issue_tracker_issue_labels`); applying means picking an existing label, not\ntyping free-form text. Deleting a label is allowed even when in use — the join\nrows cascade away and the tagged issues simply lose that label. A default set\n(`bug`, `enhancement`, `documentation`, `question`, `duplicate`) is seeded\n**once, when the labels table is first created** — never re-seeded, so user\ndeletions survive (see ADR 0001).\n\n### Blocking relationship\n\nA directed dependency between two issues in the same tracker: \"A blocks B\" means\nB depends on A. Stored as one directed edge in\n`issue_tracker_issue_blocks(blocker_id,\nblocked_id)`; \"blocks\" and \"blocked by\"\nare the same edge read from opposite ends. The block graph is a strict DAG:\n**any** edge that would create a cycle is rejected — self-edges, direct\nreciprocals (A↔B), and longer loops (A→B→C→A) alike. This is stricter than\nGitHub (which permits longer cycles) and is enforced with a reachability check\non insert (see ADR 0002).\n\n### Touch (updated_at)\n\nMutating an issue's associations — adding/removing a label, an assignee, or a\nblock edge, or adding a comment — updates that issue's `updated_at`, exactly as\nediting the issue itself does. `updated_at` reflects \"last activity on this\nissue\", not just edits to its own columns.\n\n### Blocked (derived)\n\nAn issue is _blocked_ iff at least one of its blockers is still `open`. This is\nnever stored — it is computed from the edges and the blockers' status, so\nclosing a blocker automatically unblocks its dependents. Blocked-ness is\ninformational: it does **not** prevent an issue from being closed.\n\n### Event\n\nAn append-only record of one change, in a single polymorphic table\n(`issue_tracker_events`): `id`, `event_type`, `entity_id`, `actor`, `data`,\n`event_timestamp`. `event_type` is `.` where entity ∈ {issue,\ncomment, label} and verb ∈ {created, updated, deleted}. The events log is the\n**source of truth for provenance and history**; live tables hold only current\nstate. Grammar:\n\n- **Boundary events snapshot full state.** `*.created` → the entity's full\n initial state; `*.deleted` → its full final state (so a hard-deleted row\n leaves a complete tombstone).\n- **`*.updated` carries a field delta:** `{ update_target, from, to }`.\n Associations are modelled as `issue.updated` with `update_target` ∈ {label,\n assignee, blocks, blocked_by} and `from`/`to` using **`null ↔ value`** (null→X\n = added, X→null = removed). A block edge writes **one** event, on the acting\n issue.\n\nOne event per changed field: closing an issue emits two events (`status` and\n`state_reason`), sharing one actor and timestamp. See ADR 0004.\n\n### Actor\n\nThe Val Town handle that performed a change, stored on each event. This is the\nonly place actor/provenance lives — entities and links do not carry `*_by`\ncolumns.\n\n## Removed / rejected\n\n- **Priority** — removed entirely. Faithful to GitHub, which has no first-class\n priority field (labels/Projects only).\n- **`in_progress` status** — removed; existing rows migrate to `open`.\n","createdAt",["D",1783785765631],"branchVersion","branchId","b6817ee5-03f4-41f2-901e-1bb2efa16e9e","id","abe99189-4851-4aab-ae08-280f66283cac","val-issue-tracker",["D",1783563523910],"deletedAt","legacyEnvVars","privacy","public","httpPrivacy","description","Per-val issue tracker — import into any val for scoped issues","imageUrl","5d1042a9-7b0b-499d-8a72-3a8ac7a4e185","pinnedFileId","d1d90306-7b3c-11f1-b527-1607ee4eb77e","pinPreview",true,"pinMigrated","screenshotVersion","likeCount",0,"orgId","5f80108f-7ca4-4327-b77b-089dbe4b5a82","tursoName","abe9918948514aabae08280f66283cac","tursoHostname","abe9918948514aabae08280f66283cac-val-town.aws-us-east-2.turso.io","tursoMeasuredAt",["D",1789525245864],"pinned","userPerm","r","valPerm","blobPerm","rw","emailPerm","sqlitePerm","projectPerm","telemetryPerm","user",{"_99":98,"_106":102},"org",{"_99":98,"_100":-5,"_101":102,"_18":54,"_103":104,"_105":25},"branch",{"_13":88,"_32":89,"_42":41,"_90":43,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":-5,"_96":44,"_97":98},"isOwned",369,"main","projectId","forkedBranchId","forkedBranchVersion","forkedProjectPrivacy","forkedProjectId","forkedProjectOrgId","projectName","userHandle","nbbaier","handle","displayName","avatar","https://secure.gravatar.com/avatar/0129a541b7b3574e92c4afd06c5e32da&d=identicon","tier","pro","canRestrictVals","profileImageUrl","branchName","","adoptOrgId",{"_42":43,"_32":44,"_37":540,"_46":-5,"_47":25,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":58,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":541,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":542,"_83":543,"_85":544,"_87":25},"tree",[315,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351],"files",[315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351],"counts",{"_305":62,"_306":282,"_307":62,"_308":309,"_310":311},"contents",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_42":298,"_32":299,"_30":300,"_153":-5,"_40":41,"_39":301,"_155":58,"_37":302,"_13":62,"_33":303,"_34":-5,"_24":25,"_160":-5,"_27":304},{"_42":291,"_32":292,"_30":293,"_153":-5,"_40":41,"_39":294,"_155":58,"_37":295,"_13":62,"_33":20,"_34":296,"_24":25,"_160":-5,"_27":297},{"_42":285,"_32":286,"_30":287,"_153":-5,"_40":41,"_39":288,"_155":25,"_37":289,"_13":282,"_33":20,"_34":283,"_24":25,"_160":-5,"_27":290},{"_42":277,"_32":278,"_30":279,"_153":-5,"_40":41,"_39":280,"_155":25,"_37":281,"_13":282,"_33":20,"_34":283,"_24":25,"_160":-5,"_27":284},{"_42":274,"_32":28,"_30":31,"_153":-5,"_40":41,"_39":14,"_155":25,"_37":275,"_13":167,"_33":20,"_34":36,"_24":25,"_160":-5,"_27":276},{"_42":266,"_32":267,"_30":268,"_153":-5,"_40":41,"_39":269,"_155":25,"_37":270,"_13":271,"_33":20,"_34":272,"_24":25,"_160":-5,"_27":273},{"_42":259,"_32":260,"_30":261,"_153":-5,"_40":41,"_39":262,"_155":25,"_37":263,"_13":205,"_33":158,"_34":264,"_24":25,"_160":-5,"_27":265},{"_42":252,"_32":253,"_30":254,"_153":-5,"_40":41,"_39":255,"_155":25,"_37":256,"_13":205,"_33":158,"_34":257,"_24":25,"_160":-5,"_27":258},{"_42":245,"_32":246,"_30":247,"_153":-5,"_40":41,"_39":248,"_155":25,"_37":249,"_13":182,"_33":158,"_34":250,"_24":25,"_160":-5,"_27":251},{"_42":238,"_32":239,"_30":240,"_153":-5,"_40":41,"_39":241,"_155":25,"_37":242,"_13":167,"_33":158,"_34":243,"_24":25,"_160":-5,"_27":244},{"_42":231,"_32":232,"_30":233,"_153":-5,"_40":41,"_39":234,"_155":25,"_37":235,"_13":167,"_33":20,"_34":236,"_24":25,"_160":-5,"_27":237},{"_42":223,"_32":224,"_30":225,"_153":-5,"_40":41,"_39":226,"_155":25,"_37":227,"_13":228,"_33":158,"_34":229,"_24":25,"_160":-5,"_27":230},{"_42":215,"_32":216,"_30":217,"_153":-5,"_40":41,"_39":218,"_155":25,"_37":219,"_13":220,"_33":158,"_34":221,"_24":25,"_160":-5,"_27":222},{"_42":208,"_32":209,"_30":210,"_153":-5,"_40":41,"_39":211,"_155":25,"_37":212,"_13":167,"_33":158,"_34":213,"_24":25,"_160":-5,"_27":214},{"_42":200,"_32":201,"_30":202,"_153":-5,"_40":41,"_39":203,"_155":25,"_37":204,"_13":205,"_33":20,"_34":206,"_24":25,"_160":-5,"_27":207},{"_42":193,"_32":194,"_30":195,"_153":-5,"_40":41,"_39":196,"_155":25,"_37":197,"_13":62,"_33":158,"_34":198,"_24":25,"_160":-5,"_27":199},{"_42":186,"_32":187,"_30":188,"_153":-5,"_40":41,"_39":189,"_155":25,"_37":190,"_13":167,"_33":158,"_34":191,"_24":25,"_160":-5,"_27":192},{"_42":178,"_32":179,"_30":56,"_153":-5,"_40":41,"_39":180,"_155":25,"_37":181,"_13":182,"_33":183,"_34":184,"_24":25,"_160":-5,"_27":185},{"_42":170,"_32":171,"_30":172,"_153":-5,"_40":41,"_39":173,"_155":25,"_37":174,"_13":175,"_33":158,"_34":176,"_24":25,"_160":-5,"_27":177},{"_42":162,"_32":163,"_30":164,"_153":-5,"_40":41,"_39":165,"_155":25,"_37":166,"_13":167,"_33":158,"_34":168,"_24":25,"_160":-5,"_27":169},{"_42":150,"_32":151,"_30":152,"_153":-5,"_40":41,"_39":154,"_155":25,"_37":156,"_13":157,"_33":158,"_34":159,"_24":25,"_160":-5,"_27":161},"6516dd91-8c76-4357-ab20-f54e296757c4","ui.tsx","fca19e20-7b48-11f1-8cf9-1607ee4eb77e","parentId",181,"latest",["D",1783653143543],31,"script","/** @jsxImportSource npm:hono@4.6.14/jsx */\nimport type { FC, PropsWithChildren } from \"npm:hono@4.6.14/jsx\";\nimport type { IssueStatus, Label, StateReason } from \"./db.ts\";\n\nexport const FIELD =\n\t\"bg-[#1f232c] border border-[#2a2f3a] rounded-md min-h-10 px-3.5 text-sm font-medium text-[#e6e9ef] focus:outline-none focus:border-[#6ea8fe]\";\nconst BUTTON =\n\t\"inline-flex items-center gap-1.5 rounded-md min-h-10 px-3.5 text-sm font-medium cursor-pointer no-underline\";\nconst VARIANTS = {\n\tsolid: \"bg-[#3d7bf0] border border-[#3d7bf0] text-white hover:brightness-110\",\n\tghost:\n\t\t\"bg-transparent border border-[#3d7bf0] text-[#e6e9ef] hover:brightness-110\",\n\tdanger:\n\t\t\"bg-transparent border border-[#f06e7b] text-[#f06e7b] hover:bg-[#f06e7b] hover:text-white\",\n} as const;\n\nexport const STATUS_LABELS: Record = {\n\topen: \"Open\",\n\tclosed: \"Closed\",\n};\nexport const STATE_REASON_LABELS: Record, string> = {\n\tcompleted: \"Completed\",\n\tnot_planned: \"Not planned\",\n\tduplicate: \"Duplicate\",\n\treopened: \"Reopened\",\n};\n\nexport const Card: FC> = ({\n\tchildren,\n\tclass: cls,\n}) => (\n\t\n\t\t{children}\n\t\n);\n\nexport const Button: FC<\n\tPropsWithChildren<{\n\t\tvariant?: keyof typeof VARIANTS;\n\t\thref?: string;\n\t\ttype?: \"button\" | \"submit\";\n\t\tclass?: string;\n\t\tname?: string;\n\t\tvalue?: string;\n\t}>\n> = ({\n\tvariant = \"solid\",\n\thref,\n\ttype = \"button\",\n\tclass: cls,\n\tname,\n\tvalue,\n\tchildren,\n}) => {\n\tconst classes = `${BUTTON} ${VARIANTS[variant]} ${cls ?? \"\"}`;\n\treturn href ? (\n\t\t\n\t\t\t{children}\n\t\t\n\t) : (\n\t\t\n\t);\n};\n\nexport const Select: FC<\n\tPropsWithChildren<{ name: string; id?: string; class?: string }>\n> = ({ name, id, class: cls, children }) => (\n\t\n);\n\nexport const Banner: FC<{ kind: \"ok\" | \"err\"; msg: string }> = ({\n\tkind,\n\tmsg,\n}) => (\n\t\n\t\t{msg}\n\t\n);\n\nexport const StatusBadge: FC<{ status: IssueStatus; reason?: StateReason }> = ({\n\tstatus,\n\treason,\n}) => (\n\t\n\t\t{STATUS_LABELS[status]}\n\t\t{reason ? ` · ${STATE_REASON_LABELS[reason]}` : \"\"}\n\t\n);\n\nexport const LabelTag: FC<{ label: Label }> = ({ label }) => (\n\t\n\t\t{label.name}\n\t\n);\n","label",[151],"80ef53f6-f527-4cdf-ac75-0c667acc93b6","test_sqlite.ts","2bb2ce86-7c0d-11f1-9a68-1607ee4eb77e",196,["D",1783711960293],2,"import { DatabaseSync } from \"node:sqlite\";\n\nexport interface TestResultSet {\n\tcolumns: string[];\n\trows: Record[];\n\trowsAffected: number;\n\tlastInsertRowid: bigint | undefined;\n}\n\nexport function createTestSqlite() {\n\tconst database = new DatabaseSync(\":memory:\");\n\tdatabase.exec(\"PRAGMA foreign_keys = ON\");\n\n\tconst execute = (\n\t\tstatement: string | { sql: string; args?: unknown[] },\n\t): Promise => {\n\t\ttry {\n\t\t\tconst sql = typeof statement === \"string\" ? statement : statement.sql;\n\t\t\tconst args = typeof statement === \"string\" ? [] : (statement.args ?? []);\n\t\t\tconst prepared = database.prepare(sql);\n\t\t\tif (/^\\s*(SELECT|PRAGMA|WITH)\\b/i.test(sql)) {\n\t\t\t\tconst rows = prepared.all(...(args as never[])) as Record<\n\t\t\t\t\tstring,\n\t\t\t\t\tunknown\n\t\t\t\t>[];\n\t\t\t\treturn Promise.resolve({\n\t\t\t\t\tcolumns: rows[0] ? Object.keys(rows[0]) : [],\n\t\t\t\t\trows,\n\t\t\t\t\trowsAffected: 0,\n\t\t\t\t\tlastInsertRowid: undefined,\n\t\t\t\t});\n\t\t\t}\n\t\t\tconst result = prepared.run(...(args as never[]));\n\t\t\treturn Promise.resolve({\n\t\t\t\tcolumns: [],\n\t\t\t\trows: [],\n\t\t\t\trowsAffected: Number(result.changes),\n\t\t\t\tlastInsertRowid: BigInt(result.lastInsertRowid),\n\t\t\t});\n\t\t} catch (error) {\n\t\t\treturn Promise.reject(error);\n\t\t}\n\t};\n\n\treturn {\n\t\tdatabase,\n\t\texecute,\n\t\t/**\n\t\t * Mirror the libsql `transaction(\"write\")` contract on top of node:sqlite:\n\t\t * `BEGIN IMMEDIATE` opens an exclusive write transaction, statements run\n\t\t * sequentially on the single in-memory connection, and `commit`/`rollback`\n\t\t * close it. This is the same atomic-write contract `db.ts` drives in\n\t\t * production, so the store tests exercise the real transaction path.\n\t\t */\n\t\ttransaction(_mode?: \"write\" | \"read\" | \"deferred\") {\n\t\t\tdatabase.exec(\"BEGIN IMMEDIATE\");\n\t\t\tlet settled = false;\n\t\t\tconst finish = (verb: \"COMMIT\" | \"ROLLBACK\") => {\n\t\t\t\tif (settled) return Promise.resolve();\n\t\t\t\tsettled = true;\n\t\t\t\tdatabase.exec(verb);\n\t\t\t\treturn Promise.resolve();\n\t\t\t};\n\t\t\treturn Promise.resolve({\n\t\t\t\texecute,\n\t\t\t\tcommit: () => finish(\"COMMIT\"),\n\t\t\t\trollback: () => finish(\"ROLLBACK\"),\n\t\t\t});\n\t\t},\n\t};\n}\n",[163],"cd8a9ea8-1579-4629-9a43-c9a3525477d5","mod.ts","d1e3fc5c-7b3c-11f1-af1c-1607ee4eb77e",30,["D",1783568883064],11,"export {\n\tcreateIssueTracker,\n\tdefault,\n\ttype IssueTrackerOptions,\n} from \"./app.tsx\";\n",[171],"b64f3437-f4bc-4279-9ad6-786ec6cac581","main.ts",162,["D",1783653141198],10,"http","import { createIssueTracker } from \"./mod.ts\";\n\n/**\n * This val's own issue tracker — manages THIS val's scoped SQLite database.\n *\n * To add issues to a DIFFERENT val, import the tracker into that val:\n *\n * import { createIssueTracker } from \"https://esm.town/v/nbbaier/val-issue-tracker/mod.ts\";\n * export default createIssueTracker({ owner: [\"nbbaier\"] });\n *\n * Because scoped SQLite is bound to the running val, the imported tracker\n * reads/writes the host val's database automatically — no per-val config needed.\n */\nexport default createIssueTracker({});\n",[179],"17e2256d-d27b-4705-aa51-8a95e016e3e4","layout.tsx","fd6015ee-7b48-11f1-bafe-1607ee4eb77e",107,["D",1783574315459],"/** @jsxImportSource npm:hono@4.6.14/jsx */\nimport type { FC, PropsWithChildren } from \"npm:hono@4.6.14/jsx\";\n\nexport const Layout: FC<\n\tPropsWithChildren<{\n\t\ttitle: string;\n\t\tuser?: string | null;\n\t\tauth?: boolean;\n\t}>\n> = ({ title, user, auth = true, children }) => (\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t{title}\n\t\t\t

Diff · v208