@orbytes/astrolab 0.3.0 → 0.4.0-next.2

package/docs/PIN.md

@@ -1,8 +1,10 @@
 # The pin board
 
 Click a rendered element on `astro dev`, leave a comment, and get a markdown ticket plus a PNG on
-local disk for a Claude Code agent to pick up. Then work the tickets on a kanban at `/pin`, on the
-same dev server. No cloud, no API key, no MCP, no second process.
+local disk for a Claude Code agent to pick up — from the lab's navbar (**Comment**, on the page it is
+previewing) or from Astro's dev toolbar on the site's own pages. Then work the tickets on a kanban
+at `/lab/tasks`, in the lab, on the same dev server. No cloud, no API key, no MCP, no second
+process. It needs the site to be inside a git repository (› *Wiring*).
 
 It is for a **solo pass** — your own review of a site in dev, before anyone else sees it. It does
 not sync with whatever tool you use for review rounds with other people, and is not meant to
@@ -24,7 +26,7 @@ own port (`backlog browser`, 6420). That is the whole reason it is gone — the
 
 | Stop | Do instead |
 |---|---|
-| `backlog browser` | `npm run dev`, then `/pin` |
+| `backlog browser` | `npm run dev`, then `/lab/tasks` |
 | `backlog task edit <n> …` on a pin ticket | drag the card, or use the status menu in its detail panel |
 
 `backlog task edit` is the original defect, not an alternative. Any write through backlog.md
@@ -33,7 +35,7 @@ pin ticket that erases `dispatch`, `source`, `selector`, `rect`, `shot` and `out
 why the pin fields live in a fenced block in the body, and why `/pin` was read-only until
 2026-09-22:
 a second writer of these files would have rebuilt the bug. With backlog.md out of the loop there
-is no second writer, so `/pin` writes them correctly by construction (› *The write path*).
+is no second writer, so the board writes them correctly by construction (› *The write path*).
 
 If backlog.md is still installed globally, this does not uninstall it.
 A `backlog/config.yml` left behind in a repo that used backlog.md is a record and nothing reads it
@@ -78,20 +80,34 @@ isCancelled(t.status);   // the archive test
 
 `isOpen()` is *not `Resolved` and not `Cancelled`* — one definition, shared by this board's chips
 and the in-page panel's Open tab, so the two cannot disagree by one ticket. `Cancelled` appears in
-neither tab: it is reachable on `/pin` only.
-
-## The board at `/pin`
+neither tab: it is reachable on the board only.
+
+## The board at `/lab/tasks`
+
+**In the lab since 2026-09-24** (decided that day: one URL, everything under `/lab`). The board is
+two views in the lab's own chrome — **Kanban Board** at `/lab/tasks` and **All Tasks**, a sortable
+table of every ticket, newest first, at `/lab/tasks/all` — with no second-level panel beside them
+(decided 2026-09-24: the board's own status chips already filter, so a status list beside it only
+took width from the columns); `/lab/tasks?status=Ready%20for%20review` opens the board filtered to
+one column.
+`/pin`, the board's address until then, redirects there. Both views are Astro pages the pin half
+injects in `astro dev` only, rendered from the same markup, stylesheet and script as the standalone
+file (`boardParts` in [`src/pin/board.mjs`](../src/pin/board.mjs)); the stylesheet is scoped with
+`@scope (.pin-board)` so it cannot restyle the chrome around it, and it takes the lab's palette and
+dark mode inside the lab.
 
 Six columns in the order above, read fresh from `backlog/tasks/` on every request. No build step,
-no regeneration; a refresh is the reload.
+no regeneration; a refresh is the reload. In the lab the columns keep a fixed width and the row
+scrolls sideways, rather than wrapping into a stack beside two sidebars.
 
 - **Ready for review is drawn to be seen**, because it is the human review queue and the whole
   reason the model changed — violet rule, violet dot, *waiting on you* under the name, a tinted panel
   with a filled count **only when it actually holds something**. An empty queue stays quiet; one
   that shouts at nothing teaches you to stop looking at it. Its count also leads the top bar.
 - **Cancelled is drawn to be ignored**: a narrow dashed rail rather than a sixth of the wall, its
-  cards desaturated until hovered. Still a real drop target, and still the only place a cancelled
-  ticket can be seen at all — an archive nobody can open is a delete.
+  cards desaturated until hovered. Still a real drop target. This rail, the All Tasks table (which
+  lists every ticket) and the gallery file are the only places a cancelled ticket can be seen at
+  all — an archive nobody can open is a delete.
 - Every column carries a one-line gloss under its name (*agents start here*, *waiting on you*),
   because six nouns with no explanation is a vocabulary you have to be told once and remember.
 - **A card** carries its screenshot, id, title, dispatch mode, priority and source file, plus the
@@ -110,27 +126,51 @@ printed `0 ticket(s)` until 2026-09-22). It renders from the same module and is
 board is writable exactly when `renderBoard` is given an endpoint, and a `file://` page has nothing
 listening behind it.
 
-**The board's corner links** are an option (`links`), not the hardcoded `/` and `/lab` they were
-until 2026-09-22. Through `orbytesLab()` they are filled in from the lab's own resolved `subpath`,
-so the "Lab" link is derived from the value the routes are injected at rather than agreeing with it
-by luck.
+**The standalone board's corner links** are an option (`links`), not the hardcoded `/` and `/lab`
+they were until 2026-09-22. Inside the lab there are none — the lab's own menu is right there.
+
+## Pinning from inside the lab
+
+Every preview in the lab is an `<iframe>`, and Astro's dev toolbar is hidden inside the lab's
+frames, so a lab page has one toolbar — its own — and one pin app. The lab drives that app rather
+than carrying a second picker:
+
+- **Comment**, in the navbar of a component page and of a page view, starts a pick confined to the
+  canvas: only the framed page can be picked, never the lab's chrome around it. Escape stops the
+  pick and turns Comment off; a comment already typed into the composer is kept, never discarded.
+  The composer that follows is the pin app's own window on the dev toolbar. The button is disabled
+  until the pin app has started, which it does when the dev toolbar is idle.
+- **The pins** already left on the framed page are drawn over the frame at their elements: blue
+  while open, grey once resolved, numbered in the order they were made, cancelled ones never. A
+  ticket whose selector finds nothing on that page, or more than one thing, draws no pin rather
+  than a guessed one. A pin, and the pin row in the component's Properties panel, open All Tasks.
+- **⋯ › Pins** holds two switches, Show pins (on) and Show resolved (off), remembered per browser
+  in `localStorage` (`lab-pins-show`, `lab-pins-resolved`).
+
+The list of pins is the pin app's own, re-read after every write, so a new pin appears as soon as
+its ticket lands. How the lab and the app talk is in [the contract](./PIN-CONTRACT.md) › *The lab's
+channel*. On the site's own pages, outside `/lab`, the dev toolbar's pin app works exactly as it
+always did.
 
 ## The write path
 
 One endpoint, `POST <route>/api/ticket`, registered in `astro:server:setup` — which does not exist
 in a build, so it cannot reach `dist/`.
 
-**`route` shadows a host page at the same path.** The board and this endpoint are middleware,
-installed ahead of Astro's own request handler, so a site with its own `src/pages/pin.astro` gets
-the board instead of its page — in dev only, and with nothing on screen to explain it. The default
-stays `/pin`: it is the address every document here names. A site that owns
-that path sets `pin: { route: "/__pin" }`.
+**The endpoint, the screenshots and the `/pin` redirect are middleware**, installed ahead of
+Astro's own request handler, so they shadow a host page at the same path — in dev only. Through
+`orbytesLab()` the route is `<subpath>/tasks`, which no site page is likely to be; the one exposed
+address is `/pin`, which redirects. Setting `route` does not free it: inside the lab `/pin`
+redirects to `route` whatever that is, and a `route` of `/pin` puts the Tasks views there instead,
+so no `route` leaves a site's own `/pin` page alone in dev — `pin: false` does. On its own,
+without the lab, the pin half still serves its standalone board at `route`, default `/pin`, and
+there `pin: { route: "/__pin" }` moves it off a site page.
 
 ```json
 { "id": "PIN-004", "status": "Ready for review", "expect": { "status": "In Progress" } }
 ```
 
-`updateTicket` (`src/board.mjs`) rewrites **only** the frontmatter lines it is changing, plus
+`updateTicket` (`src/pin/board.mjs`) rewrites **only** the frontmatter lines it is changing, plus
 `updated_date`. It never serialises: the file is split by index, and the slice from the closing
 `---` onward — the comment, the image and the fenced ```yaml pin block — is the same substring on
 the way out as on the way in. That identity is asserted on every write, and the write is a temp
@@ -172,7 +212,7 @@ Nothing is wired separately: the board comes with the lab, through the one integ
 already configures.
 
 ```js
-import orbytesLab from "./packages/astro-lab/index.mjs";
+import orbytesLab from "@orbytes/astrolab";
 
 const includeLab =
   process.argv.includes("dev") || process.env.PUBLIC_DEPLOY_ENV === "staging";
@@ -188,6 +228,15 @@ export default defineConfig({
 gates itself on `command === "dev"`, so including the lab in a staging build registers it and it
 does nothing there.
 
+**The site must be inside a git repository.** Every path in a ticket is repo-relative, and the root
+is the Astro project's folder or the nearest one above it that holds `.git`. With none, the board
+stands down for that run instead of taking the dev server with it (measured 2026-09-22: a freshly
+scaffolded Astro project, which has no git yet, could not run `astro dev` at all before the board
+learned to stand down). The only sign is a warning in the dev server's log. `<route>`,
+`<route>/all` and `/pin` answer 404, the lab shows no Tasks group and no Comment button, and there
+is no pin app on the dev toolbar and no source stamp. `git init` and a restart turn it on;
+`pin: false` silences the warning.
+
 `playwright` is an **optional** peer and is loaded by dynamic import inside the screenshotter, not
 at module scope — a site without it loads its config, runs the lab and writes tickets without
 pictures. Install it (`npm i -D playwright && npx playwright install chromium`) for the screenshots,
@@ -199,14 +248,14 @@ Pass these as `orbytesLab({ pin: { … } })`.
 
 | Option | Default | What it does |
 |---|---|---|
-| `stamp` | `["src/lab/sections", "src/components"]` | **Site-relative** directories whose `.astro` files get `data-orbytes-src`. |
+| `stamp` | `["src/lab/sections", "src/components"]` | **Site-relative** directories whose `.astro` files get `data-orbytes-src`. Replaces the default whole, and does not follow the lab's `directory`. `src/lab/components` and `src/lab/explorations` are not in it — see *The source attribute*. |
 | `stampSkip` | `[]` | **Site-relative** `.astro` paths exempt from the stamp's hard failure. See below. A repo-relative path is accepted too — until 2026-09-22 that was the only spelling that worked, while `stamp` beside it was site-relative, so the exemption silently lapsed wherever the Astro project was not the repo root. |
 | `backlogDir` | `"backlog"` | Repo-relative board directory: tickets in `tasks/`, PNGs in `assets/`. |
 | `archiveDir` | `~/.orbytes/feedback-archive` | Canonical screenshot home; the repo copy is a hardlink into it. |
 | `project` | the checkout's folder name | The folder under `archiveDir` this project's screenshots live in. Two clones of **different** repos under one folder name share an archive silently, one overwriting the other's `pin-007.png` — set it where that is possible. |
 | `shots` | `true` | `false` writes tickets and takes no screenshots. |
-| `route` | `"/pin"` | Where the board is served. `<route>/assets/*` serves its screenshots, `<route>/api/ticket` is the write endpoint. **It shadows a host page at that path** — see *The write path*. Trailing slashes are stripped. The toolbar app reads the resolved value too (it fetches the ticket list from it and its **Board ↗** button opens it), through the virtual module below — until 2026-09-22 it carried a literal `/pin`, so setting this left the panel fetching a path nothing serves. |
-| `links` | the lab's resolved subpath | The board's corner links, `[{ href, label }]`. `[]` draws none. |
+| `route` | `"<subpath>/tasks"` (`"/pin"` without the lab) | Where the board is served. `<route>/assets/*` serves its screenshots, `<route>/api/ticket` is the write endpoint; in the lab, `<route>` and `<route>/all` are the two views. Trailing slashes are stripped. The toolbar app reads the resolved value too (it fetches the ticket list from it and its **Board ↗** button opens it), through the virtual module below — until 2026-09-22 it carried a literal `/pin`, so setting this left the panel fetching a path nothing serves. |
+| `links` | the lab's resolved subpath | The standalone board's corner links, `[{ href, label }]`. `[]` draws none. |
 | `appId` / `appName` / `icon` | `"orbytes-pin"` / `"Pin"` / `"bug"` | The dev-toolbar app's identity. |
 
 ## What a ticket looks like
@@ -306,26 +355,33 @@ Two rules now keep a selector off that ground, both in
 - **A class naming a runtime condition never enters a selector** (`isTransientClass`,
   `extendsSiblingClass`) — `swiper-slide-active` is on slide 1 now and slide 2 after a scroll.
 
-Neither is complete, and the field is what makes the remainder visible. `src/shot.mjs` already
+Neither is complete, and the field is what makes the remainder visible. `src/pin/shot.mjs` already
 loads the page **fresh in a real browser** to take the screenshot; before the shutter it asks that
 page how many nodes the ticket's selector finds, and writes the answer back into the pin block:
 
 | Value | Means |
 |---|---|
 | `1` | healthy — the selector names exactly this element on a fresh load |
-| `0` | dead — work the ticket from `source`, the screenshot and `outer_html` |
+| `0` | dead — flagged *needs a human* on the board; a person works it from `source`, the screenshot and `outer_html` |
 | `2`+ | ambiguous — the selector names several elements |
 | `pending` | never tested — shots are off, or the screenshot failed |
 
 Anything but `1` is said in the dev log and in the toolbar panel. A ticket whose selector died is
 **still a good ticket** — it is labelled, never discarded. The defect was the silence.
 
+On the board, `0` and `2`+ put a banner on the card, count towards *needing a human* in the
+summary, and match the *Needs a human* filter. The banner's note for `0` says an agent cannot
+locate the element: its selector cannot, and the rest of the ticket is intact for a person to work
+from. **The flag is a label, not a gate.** It changes no status, and neither `isAgentReady()` nor
+`listTickets()` reads `selector_matches` — a flagged ticket left in `Ready for agent` is still
+handed to an agent. Only its status keeps an agent off it.
+
 ## Screenshots
 
 One chromium for the whole dev session, launched lazily on the first pin and kept warm, closed
-when the dev server closes. Measured on an Apple-silicon laptop, 2026-09-21: the launch itself is
-~98 ms, and a full capture — navigate, freeze motion, settle every image, hold the scroll position,
-clip — is ~1.34 s warm against ~1.42 s cold.
+when the dev server closes. What a shot costs has been measured three times, each timing a
+different span; the figures, their dates and what each one timed are in
+[the contract](./PIN-CONTRACT.md) › *Screenshots*.
 
 You never wait for any of it. The ticket is written and `orbytes-pin:created` replied on the
 same synchronous tick; the screenshot follows and sends `orbytes-pin:shot` when it lands. A ticket
@@ -349,6 +405,22 @@ file under `stamp`, and the picker walks up from the clicked node to the nearest
 it. No ancestor found → `source` is `unresolved`, and the CSS selector plus `outer_html` still
 make the ticket actionable.
 
+**The default does not cover every tier.** It stamps `src/lab/sections` and `src/components`, so a
+component kept in the lab's own `src/lab/components/` (or `src/lab/explorations/`) and pinned on its
+own variant has no stamped ancestor, and its tickets say `unresolved`. Name the folder to include it
+— `stamp` replaces the default, so restate what you keep:
+
+```js
+orbytesLab({
+  pin: {
+    stamp: ["src/lab/sections", "src/lab/components", "src/components"],
+  },
+})
+```
+
+Widening `stamp` widens the hard failure below with it, so check the folder for templates with no
+element to stamp first.
+
 The attribute is inserted immediately after the tag name (`<section` → `<section
 data-orbytes-src="…"`), so no attribute value, expression, spread or self-closing slash can be
 mangled and no line number moves.
@@ -374,14 +446,17 @@ orbytesLab({
 
 ## The browser ↔ server channel
 
-Astro's dev toolbar, over the existing Vite HMR socket. No HTTP endpoint, no port, no CORS.
+Creating a ticket goes over Astro's dev toolbar, on the existing Vite HMR socket — no HTTP endpoint,
+no port, no CORS. Changing a ticket's status is the one HTTP write, from the board and from the
+panel's own menus alike: `POST <route>/api/ticket`, same-origin, on the dev server already
+running.
 
 | Direction | Event | Payload |
 |---|---|---|
 | browser → server | `orbytes-pin:create` | `{ comment, dispatch, source, selector, url, viewport, scroll, rect, outerHTML }` |
 | server → browser | `orbytes-pin:created` | `{ id, file, shot, error }` — all four keys, always |
 | server → browser | `orbytes-pin:shot` | `{ id, shot, selectorMatches, error }` |
-| board → server | `POST <route>/api/ticket` | `{ id, status?, priority?, expect? }` → `{ ok, id, status, priority, file, changed, card }` |
+| board or panel → server | `POST <route>/api/ticket` | `{ id, status?, priority?, expect? }` → `{ ok, id, status, priority, file, changed, card }` |
 
 On failure the reply is `{ id: null, file: null, shot: null, error: "why, in one plain sentence" }`.
 
@@ -410,10 +485,12 @@ window, so clicking it again focuses that tab instead of opening another.
 
 1. `astro:config:setup` returns early unless the Astro command is `dev` — no plugin, no toolbar
    app, no stamp.
-2. Both Vite plugins carry `apply: "serve"`, so they cannot load in a build even if they were
+2. All three Vite plugins — the source stamp, the toolbar's config module and the one that closes
+   the browser — carry `apply: "serve"`, so they cannot load in a build even if they were
    registered.
-3. `astro:server:setup`, where every write lives — the ticket writer, the board and the
-   `/pin/api/ticket` endpoint — does not run in a build at all.
+3. `astro:server:setup`, where every write lives — the ticket writer, the screenshots and the
+   `<route>/api/ticket` endpoint — does not run in a build at all. The lab's two Tasks views are
+   injected past assertion 1, so they exist in `astro dev` and in no build.
 4. That hook returns early anyway when `astro:config:setup` stood down, so a host that runs the
    hooks in an order this package did not choose still gets nothing.
 
@@ -422,8 +499,11 @@ The first one matters more since the merge than it did before: the lab is delibe
 in a build for the first time, and `command === "dev"` is what makes that a no-op.
 
 Verified by running a real `npm run build` and grepping `dist/` for `orbytes-pin`, `data-orbytes-src`
-and `/pin/api`: no hit.
+and `/pin/api`: no hit. Re-checked 2026-09-24 on a staging build of the testbed, the case where the
+pin half is registered: no hit for those three or for `/tasks/api`, and no `lab/tasks/` page.
 
 No path this package emits into served HTML or into a ticket is absolute. The repo root is found
-by walking up from the Astro config root to the first directory containing `.git`, and it throws
-rather than guess.
+by walking up from the Astro config root to the first directory containing `.git`, and
+`findRepoRoot` throws rather than guess. The integration catches that throw, warns, and stands down
+for the run (› *Wiring*) — a library that guesses writes files where nobody asked, and an
+integration that rethrows takes the dev server down.

package/index.d.ts

@@ -11,11 +11,6 @@ export interface LabTierOption {
    * thumbnails and in the viewport configurator. Defaults to true for a tier named "sections".
    */
   responsive?: boolean;
-  /**
-   * This tier's stories may be marked for deletion in the sidebar and removed by
-   * `orbytes-lab-cull`. Defaults to true for a tier named "explorations".
-   */
-  cullable?: boolean;
 }
 
 export interface OrbytesLabOptions {
@@ -23,14 +18,17 @@ export interface OrbytesLabOptions {
   directory?: string;
   /** Where the lab is served. Default `"/lab"`. */
   subpath?: string;
-  /** The consumer's token/stylesheet files, as Astrobook takes them. Default `[]`. */
+  /**
+   * The consumer's token/stylesheet files. They reach the PREVIEW only — the bare story each
+   * component page shows in its canvas — never the lab's own chrome. Default `[]`.
+   */
   css?: string[];
   /**
-   * A path to the consumer's own head component, rendered inside the lab's head — how fonts and
-   * anything else site-specific reach lab pages. Relative to the project root.
+   * A path to the consumer's own head component, rendered inside every story preview's head — how
+   * fonts and anything else site-specific reach the previews. Relative to the project root.
    */
   head?: string;
-  /** The lab's name, shown in the dashboard. Default `"Component lab"`. */
+  /** The site's name as the lab shows it (the tab title, the home page). Default `"Component lab"`. */
   title?: string;
   /**
    * The deployed lab's base URL — the real minified build, which a dev server is not. Every card
@@ -49,17 +47,35 @@ export interface OrbytesLabOptions {
   feedbucketKey?: string;
   /**
    * The tiers, in reading order. Default `["sections", "components", "explorations"]`; a tier
-   * named "sections" takes the responsive role and one named "explorations" the cull role unless
-   * the entry says otherwise.
+   * named "sections" takes the responsive role unless the entry says otherwise.
    */
   tiers?: (string | LabTierOption)[];
+  /**
+   * The screen sizes the viewport offers. Every key is optional; an omitted one keeps the default
+   * (the orbytes scale).
+   */
+  viewports?: {
+    /**
+     * The widths the design is drawn at — the navbar's device switch, in order. `icon` is one of
+     * `monitor`, `tablet`, `phone-landscape`, `phone`.
+     * @default 1440 desktop · 834 tablet · 550 phone landscape · 390 phone
+     */
+    design?: { label: string; width: number; icon?: string }[];
+    /**
+     * The lower edge of each CSS band; the last is 0. The readout names the band the frame is in,
+     * and the presets offer both sides of every edge.
+     * @default desktop 992 · tablet 768 · phone landscape 480 · phone 0
+     */
+    breakpoints?: { name: string; min: number }[];
+    /** Named sizes that set width AND height. @default iPhone 15, iPad, MacBook, … */
+    devices?: { label: string; width: number; height: number }[];
+  };
   /**
    * The pin board — the dev-only click-to-ticket feedback half of this package (`docs/PIN.md`).
    *
-   * `true` or omitted ships it at `/pin` with its defaults; `false` omits it entirely, for a site
-   * that wants the component lab alone. An object is the pin integration's own options, and the
-   * lab fills in `links` from its RESOLVED `subpath` so the board's "Lab" link is derived rather
-   * than guessed — pass your own `links` to override that.
+   * `true` or omitted ships it at `<subpath>/tasks` (the lab's Kanban Board and All Tasks views),
+   * with `/pin` redirecting there; `false` omits it entirely, for a site that wants the lab alone.
+   * An object is the pin integration's own options.
    *
    * @default true
    */
@@ -95,11 +111,12 @@ export interface OrbytesPinOptions {
   shots?: boolean;
   /**
    * Where the board is served, dev only. `<route>/assets/*` serves its screenshots and
-   * `<route>/api/ticket` is the one write endpoint.
+   * `<route>/api/ticket` is the one write endpoint; through `orbytesLab()`, `<route>` and
+   * `<route>/all` are the lab's Kanban Board and All Tasks views.
    *
-   * It is MIDDLEWARE, installed ahead of Astro's own request handler, so it SHADOWS a host page at
-   * the same path — in dev, silently. A site with its own `/pin` page sets something else here.
-   * @default "/pin"
+   * Its asset and API paths are MIDDLEWARE, installed ahead of Astro's own request handler, so they
+   * shadow a host page at the same path — in dev, silently.
+   * @default "<subpath>/tasks" through orbytesLab(), "/pin" on its own
    */
   route?: string;
   /**
@@ -117,9 +134,10 @@ export interface OrbytesPinOptions {
 }
 
 /**
- * The orbytes component lab AND the pin board: the Astrobook core vendored into this package
- * (`src/core/`, 0.13.3), the lab shell around it, and the dev-only feedback board at `/pin`. Astro
- * flattens the returned array, so one entry in `integrations` configures all three.
+ * The orbytes lab AND the pin board: the Astrobook core vendored into this package
+ * (`src/core/`, 0.13.3), the lab's chrome around it, and the dev-only feedback board at
+ * `<subpath>/tasks`. Astro flattens the returned array, so one entry in `integrations` configures
+ * all three.
  *
  * `pin: false` returns the lab alone.
  */
@@ -206,7 +224,7 @@ export const OPEN_STATUSES: readonly PinStatus[];
 export function normaliseStatus(status: unknown): string;
 /** Open — neither accepted nor cancelled. `isOpen("Done")` is `false`. */
 export function isOpen(status: unknown): boolean;
-/** Archived. Every agent-facing read drops these; `/pin` is the one place they are visible. */
+/** Archived. Every agent-facing read drops these; the board is the one place they are visible. */
 export function isCancelled(status: unknown): boolean;
 /** May an agent START work on this ticket? Exactly one status says yes. */
 export function isAgentReady(status: unknown): boolean;