AGENT A — Batch 1 report

1. Problems found, and their ROOT CAUSES

1.1 Work was one idea with three names and two addresses

Symptom (audit): /admin/staff/work renders a page titled "OPERATIONS"; /admin/operations also exists; the rail says "Work".

Root cause. Two components each believed they were Work, and the rail carried both:

internalNavForRole chose between the two rail rows *by role* — the studio-wide board for owner/staff, the cockpit for editors. So the role split was encoded as a URL split, and the second URL's screen called itself something else.

In Command mode this is exactly what the audit photographed: an owner clicking "Work" got the redesigned queue, but every link the domain produces — buildActionQueue defaults href to /admin/staff/work?deliverable=, and getAdminWorkHref produces /admin/staff/work?task= — lands on /admin/staff/work, which in Command rendered the SG board: three INTAKE LANE cards, nine count pills, a BOARD/TABLE/JOBS strip. ?task= was not even honoured by the Command branch (it only checked ?deliverable=), so roughly half the in-app links into a deliverable opened the board instead of the row they named.

1.2 Work's filters were seven reasons, not a triage

Eight chips (Everything + seven categories). Accurate, and the wrong first question. The audit's "nine count pills of which seven show zero" is the SG board's intake lanes; the Command chip row has the same shape of problem at lower volume.

1.3 The calendar: "3 EVENTS" over an empty month grid

Root cause: a window mismatch, and only that. In src/components/admin/calendar/command-calendar.tsx the header rendered {events.length} events where events = getStaffCalendarEvents(state, dept) — every event in the workspace, for all time — while MonthView drew 42 cells starting at the Monday before the 1st of the anchor month, anchored on today.

The demo fixture's dated work is in May and June 2026 (src/lib/data.ts: scheduledShootDate: "2026-05-23", "2026-05-29", "2026-06-01"). Today is 25 August 2026. So the count was right, the grid was right, and they were describing different things.

I checked and ruled out the other candidates the brief named:

• *Query* — there is no query; getStaffCalendarEvents reads useAdmin().state.
• *Timezone* — studioToday() uses en-CA/Asia/Bangkok; byDay keys and grid cells are both YYYY-MM-DD and matched.
• *Render* — .cmd-month-grid, .cmd-day, .cmd-event all exist in bulgar-command.css:1347+; data-outside dims, it does not hide.

SG does not have this bug — StaffGlobalCalendar filters getStaffCalendarEvents(...) by .startsWith(month) before counting (admin-separated-workspaces.tsx:5010). Command-only.

Two further defects found while fixing it:

• Month paging moved by 28 days (step = view === "week" ? 7 : 28). Twenty- eight days is a month only in February: from the 1st of any 31-day month it lands on the 29th of the same month, so pressing "next month" on 1 January redrew January.
• Date arithmetic was browser-local. addDays did new Date(iso + "T00:00:00") — parsed in the runtime's own zone — then setDate(+1). In a zone whose DST change is at midnight that can land back on the same date. Bangkok has no DST; a laptop in Santiago does.

1.4 Mobile at 390px

• The rail collided. At ≤900px .cmd-rail becomes flex-direction: row; overflow-x: auto, but no child was `flex: none` and .cmd-rail__tools additionally set min-width: 0. Flex items default to flex-shrink: 1, so instead of overflowing into the scroller the wordmark, the New button and the search input were all compressed past their content width and drew over each other. The overflow-x: auto never engaged because nothing ever overflowed.
• The table truncated mid-word. .cmd-table td:first-child carries min-width: 11rem (9rem below 60rem) and the Work table has seven columns; at 358px of usable width the remaining six share ~215px, so prose cells wrap at every 3–4 characters — "Clea setu", "Revi inter work".

1.5 Dead space at 1440×900

• Owner Home rendered a decisions panel plus three stat tiles and stopped. The launcher-summary read it uses carries three counts; the *day* — today's shoots, due dates and deliveries, and what has moved — is computed by buildHomeSummary and shipped inside /api/admin/action-queue as payload.home, and Command was not reading it. SG's Home V2 has rendered it since 19 August. Command was showing a strict subset of its own product.
• Client World rendered two short cards (Engagements, Projects) on the overview tab. buildClientOverview and recentActivityForClient already exist, are pure, read the same store, and answer the two questions a person opens an account for — what is wrong with it, and what just happened.

1.6 A link whose parameter did nothing

command-client.tsx linked each project to /admin/staff/work?project=<id>. filterActionQueue had no projectId filter, so the parameter was dropped and the whole board rendered. Found while working on item 5.

2. Changes made, and why

2.1 One Work world — /admin/staff/work

New: src/components/admin/work/admin-work.tsx — the single entry point. It decides one thing: queue or one row's detail, in which presentation mode. It reads no data, computes no category, enforces no permission.

/admin/staff/work won the address, not /admin/staff/action-queue, because it is the one the domain already produced (buildActionQueue's default href, getAdminWorkHref) and the one /admin/operations and /admin/editor already redirect to. The route that lost is the one nothing pointed at.

The role scoping did not go away. It moved to where it was always enforced. /api/admin/action-queue has served editors scopeActionQueueToEditor(...) since Phase 3 regardless of what the rail showed. canSeeActionQueue still decides which payload is sent and still decides the studio-wide framing on the screen. What stopped being a role decision is the URL.

Capability preserved, item by item (the list in the instruction):

2.2 Work as one queue — five lanes

New: src/domain/operations/work-lanes.ts (pure) — Now / Changes / Waiting / Upcoming / Done today as sets of the *existing* action categories.

• now → overdue, due_today
• changes → needs_changes
• waiting → new_intake, unassigned, waiting_review
• upcoming → upcoming
• done → nothing from the queue. Finished work is not in the action queue at all: categoriesForWork returns early on completedAt. A done lane built from categories could only ever have read zero. It is fed from HomeSummary.momentum.completedToday — real completed_at rows the server already computes from the same deliverables in the same request — and it is called "Done today", because today is all that payload can prove.

Guarantees, and they are tests: every category is in exactly one lane; a lane count is the length of the list it opens, distinct rows, never a sum (a row that is unassigned *and* awaiting review is one row in Waiting); the lane vocabulary may not contain the words capacity, utilisation, health, progress, score, or a percent sign.

The seven reasons survive as a second chip row inside an open lane, and ?filter=overdue still works — Home, the attention strip, Team and the client screen all deep-link an exact category, and a category always resolves to and lights the lane that holds it.

Command's Work no longer renders the intake-lane cards or the view strip. SG lost nothing: AdminOperationsBoard keeps Board / Table / Jobs and gains Queue as its first view (owner/staff only, canSeeActionQueue), and the intake lanes render only in the grouped views, where a lane is how the rows below are arranged rather than three cards of counts in front of the list they came from.

2.3 The calendar

New: src/lib/domain/calendar-window.ts (pure, UTC) — one function says what a view is looking at; the header and the cells both read it, so they cannot disagree.

• Header now reads N events for the drawn window, and adds · M in all only when the two differ — so the common case is one number and the empty case explains itself.
• An empty window renders a panel above the grid saying so in words, naming the month, and offering the nearest dated day as a button (nearest by absolute distance, ties going forward). Drawn only when the total is non-zero — a workspace with no dated work already says "0 events" and a panel repeating it would flash on every first paint while the bootstrap arrives.
• The grid still renders. Losing it would lose the dates and the shape of the month; the point was that a blank grid should say why it is blank.
• Month paging now moves by a month, clamped (31 Jan + 1 month = 28 Feb, leap-aware).
• All calendar-day arithmetic is UTC, so it cannot be changed by the reader's timezone or by a DST boundary at midnight.

2.4 Mobile at 390px

src/app/bulgar-command.css:

• ≤900px: .cmd-wordmark, .cmd-rail__tools, .cmd-nav, .cmd-identity get flex: none. The strip now scrolls, which is what overflow-x: auto was there for; nothing is compressed past its content.
• ≤640px: the rail wraps into three bands — wordmark + identity, then create + search on their own full-width line, then the nav, which is the only thing that scrolls sideways. Search takes the slack the New button does not need.
• ≤640px, `.cmd-table--stack` (opt-in): a Work row becomes a card. <thead> is visually hidden but stays in the accessibility tree, and each cell prints its own column name from data-label. The title cell is the card headline — full width, no label, and released from the 11rem minimum that exists to stop numeric columns squeezing a name there are none of here. Opt-in because Command's money and configuration tables are meant to line up for comparison; they keep horizontal scroll until each is looked at properly.

2.5 Dead space, filled with data that already existed

Owner Home (home/command-home.tsx) adds Today (shoots / due / deliveries) and Moving (finished today / ready to deliver / in production), read from payload.home on /api/admin/action-queue. A second read, in its own effect, deliberately silent on failure — Home never wears an error banner, so a failed read means those sections are absent, not that the page breaks. Lists cap at five rows and say + N more — no silent truncation. Empty groups render nothing. A stat tile reading 0 keeps its place and dims to 45% (data-quiet): a checked zero is worth knowing, and a tile that vanished would reflow the row under the cursor.

Client World (clients/command-client.tsx) leads the overview with Needs attention — buildClientOverview, which runs buildActionQueue narrowed to one client, so this screen cannot say "nothing outstanding" while Work lists three overdue rows for the same account. Below it: Recent activity (recentActivityForClient over activity_logs) and an At a glance count block (open deliverables, needing attention, due next week, nobody assigned, who is on the account, the active retainer month). Rows cap at six with "N more in Work".

2.6 Two smaller fixes made along the way

• `?project=` now filters. Added projectId to ActionQueueFilters and to the Work hook; the Client World link that had been dropping it now works, and an active project filter renders as a removable chip so an inbound URL is visible rather than a silently smaller board. Leads are excluded from a project filter, which is correct — a lead is not part of a project until it becomes one.
• `?task=` opens the detail in Command. getAdminWorkHref writes ?task= and buildActionQueue writes ?deliverable=; both carry an order_deliverables.id. Command honoured only the second. Both now.

2.7 One extraction, so nothing is defined twice

src/components/admin/work/use-task-action.ts — the five workflow transitions (claim, start, submitForReview, requestRevision, approveTask), lifted verbatim out of admin-operations-workspace.tsx. The SG board and the Command detail now import one module. It decides nothing: getTaskNextAction says what a viewer may do, the server's compare-and-set decides whether it happens, and the two guards it carries are the same two the board had — they stop an obviously wrong request being sent, they are not the permission boundary.

The Command work detail was read-only, which was survivable only while /admin/staff/work still rendered the SG board underneath it. Merging Work removed that board from Command, so the transitions had to arrive on the detail or the merge would have quietly deleted an editor's ability to work. Manager Approve / Request changes is offered on the domain's own REVIEW_SUBMISSION code, not on a second reading of editorStatus.

3. Tests added and changed

Added — 4 files, 35 assertions:

Changed — 6 files. No assertion was weakened; where a premise changed, the replacement is stronger. Nothing was deleted to make something pass.

4. Approaches I tried that FAILED, or that I rejected after looking

1. Redirecting `/admin/staff/work` → `/admin/staff/action-queue` (the other direction). Rejected after reading buildActionQueue and getAdminWorkHref: the domain's canonical deliverable href is /admin/staff/work?deliverable= and getAdminWorkHref writes /admin/staff/work?task=, and /admin/operations and /admin/editor already redirect there. Retiring /admin/staff/work would have meant rewriting the domain's href construction for a cosmetic preference.

1. Making `/admin/staff/work` render the queue for editors in SG too. Rejected. It would have taken the claim / start / submit cards away from editors on the default skin, which is a capability loss dressed as a merge. SG keeps the board and gains the queue as an additional view.

1. Replacing the seven action categories with five lanes outright. Started this, then found ?filter=overdue deep links from Home, the launcher's attention strip, command-team.tsx and admin-client-command-center.tsx. Replacing the vocabulary would have silently turned "4 overdue" into the whole board. The URL now accepts both, and a category lights its lane.

1. A `DONE` lane over the action queue. It would always have read zero — categoriesForWork returns early on completedAt, so finished work is not in the queue at all. Rather than ship a permanently-zero chip (exactly the failure the audit reported: "nine count pills of which seven show zero") I traced where finished work *is* known — HomeSummary.momentum.completedToday, already in the same payload — and named the lane Done today, because today is the only span that data can prove.

1. `useState(() => canSeeActionQueue(role))` for the SG board's default view. Written, then caught before it shipped: currentUser is null on the first render because the bootstrap has not arrived, so the default would have been computed from a role nobody has and never recomputed. An owner would have opened Work on the board for the rest of the session. Replaced with a nullable "chosen view" and a derived default.

1. A generic mobile card layout for `.cmd-table`. Rejected: Command's money and configuration tables have no data-label, and stacking them would have produced unlabelled columns of numbers. The stack is opt-in (cmd-table--stack) and only Work uses it.

1. A blanket empty-state panel on the calendar whenever the window is empty. It flashed "no dated work anywhere" on every first paint while the store was still filling. Narrowed to the actual bug — total non-zero, window empty — which cannot flash, because a non-zero total means the data has arrived.

1. `npx vitest run --reporter=basic`. Fails at startup on vitest 4; not a valid reporter name here. Used the default reporter.

5. Areas I deliberately did NOT change, and why

• SG and OG. Both still work. SG's Work board keeps Board / Table / Jobs, the intake lanes, the needs-attention filters, the projects overview, the task modal and every action; it gains the queue as its first view and is titled Work instead of Operations. No bulgar-sg.css or OG rule was touched — every CSS change is inside bulgar-command.css, which is scoped to html.bulgar-command.
• `admin-separated-workspaces.tsx` (6,681 lines). Untouched, per the plan's own risk note. StaffGlobalCalendar lives there and does not have the Command calendar's bug.
• Owner Home and Client World were not rewritten. They are the reference. Home keeps its greeting, decisions panel and tiles and gains two sections below; Client World keeps its tabs, URL state and year grid and gains three panels on the overview tab.
• DNA, Showcase, Blueprint, AI Studio's generation surface, every editing form. Out of scope or deliberately preserved.
• `admin-destinations.ts` detail lines other than Work's, WORKSPACE_ROLES, RBAC, the RLS policies, src/proxy.ts, any API route's permission check. No authorization was moved, widened or narrowed by this batch. The only change adjacent to it is that /admin/staff/work is now offered to owner, staff and editor in the rail — which it already was for editors, and which the API scopes.
• The `revisionNotes` double mapping (workInputsFromRows vs delivery-planner). CLAUDE.md records the 21 Aug decision to preserve the distinction and tests/domain/revision-vocabulary.test.ts enforces it. Left alone.
• Batch 2. Not started.

6. Remaining blockers and open questions

1. I could not run the app. No Docker, no local Supabase, no .env and no .env.development.local in this container. Every claim below about *rendering* is reasoned from the code and the CSS, not observed in a browser. The visual approval this batch stops for is exactly what I could not do myself.
2. The test suite cannot go green here — see §7. This is the environmental failure CLAUDE.md already records, made total by the absence of any local database.
3. `.cmd-scroll-x:has(...)` — :has() is used once, to switch off horizontal scrolling when the table has become a stack. Supported in every current browser and in the Tauri/Electron shells; if it ever is not, the fallback is a scroller with nothing to scroll. Harmless, but worth knowing it is there.
4. Home now makes two reads (/api/admin/launcher-summary and /api/admin/action-queue). SG's Home already makes the second, so this is not new load for the product, but it is new load for Command's Home. If that matters, the honest fix is to serve the three launcher counts from the action-queue payload and drop the first read — a loader change, not a component change, and not something I should decide alone.
5. Open question for Ivan / Kris: the waiting lane groups new_intake (an unanswered enquiry), unassigned (nobody has picked it up) and waiting_review (nobody has looked). All three are "waiting on somebody at BULGAR", which is why they are together — but if the studio thinks of new enquiries as their own thing, that is a one-line change in WORK_LANE_CATEGORIES and the test that says every category has exactly one lane will keep it honest.
6. Still genuinely wrong, and NOT fixed here (carried forward from STATUS.md): Finance's lane filter does not filter; the tablet route reads the static gym fixture rather than the database; src/lib/email-outbox.ts is a localStorage mock. None is Batch 1.

7. GATES

Vocabulary is exact. Nothing below is reported as passing that I did not run.

7.1 Typecheck — PASS

$ npx tsc --noEmit
(no output, exit 0)

Run repeatedly through the batch and clean at the end.

7.2 Lint — see §7.5 for the final run

npx eslint on every touched path was clean throughout the batch (0 errors, 0 warnings). The whole-repo run is recorded below.

7.3 Tests — INFRASTRUCTURE_FAILURE, with a usable partial result

`npm test` as configured cannot run in this container at all.

$ npx vitest run
Error: Tests need a local DATABASE_URL; got "unset".
Test Files  117 failed (117)
     Tests  no tests

Root cause: tests/support/use-local-supabase.ts is a vitest setupFiles entry that throws unless DATABASE_URL points at a local Supabase. It exists to stop npm test mutating hosted production — the trap CLAUDE.md records — and it is correct. This container has no Docker (docker: command not found), no supabase stack, no .env and no .env.development.local, so there is nothing for it to point at. Every one of the 117 files fails at import, before a single assertion.

I did not weaken, skip or delete that guard. To get signal I set DATABASE_URL to the local address the guard asks for, for the duration of a run. Nothing is listening on it, so the suites that need a database fail on connect (TypeError: fetch failed in src/lib/supabase/server.ts) and the pure suites run normally.

Baseline, at the starting SHA, before any of my changes:

$ DATABASE_URL=postgresql://postgres:postgres@127.0.0.1:54322/postgres npx vitest run
Test Files  24 failed | 93 passed (117)
     Tests  33 failed | 1366 passed | 206 skipped (1605)

All 33 baseline failures are fetch failed against the absent database. So the honest statement is:

• Database-backed suites: INFRASTRUCTURE_FAILURE (24 files). Not run against a database on this machine, at HEAD or after my changes. CLAUDE.md already records that nothing has run against a real DB since 9 August; this container makes it total.
• Pure suites: PASS. Final numbers in §7.5.

7.4 Build — see §7.5

The first attempt compiled and was then killed during TypeScript:

✓ Compiled successfully in 112s
  Running TypeScript ...
Killed          (exit 137)

exit 137 is SIGKILL by the OOM killer. cat /sys/fs/cgroup/memory.max → 2147483648 — this container is capped at 2 GiB, and memory.current sat at 2,050,256,896 while Next 16's Turbopack build and its TypeScript worker ran together. free -m reports the host's 8 GiB and is misleading here.

Note the same TypeScript configuration passes standalone (npx tsc --noEmit, §7.1) — it is the two running in one 2 GiB cgroup that does not fit.

8. What a human must review

Ranked by how much I would want a second pair of eyes on it.

1. The Work merge is a routing and navigation change, and I could not click it. Open /admin/staff/work as owner, as staff and as an editor, in Command AND in SG. Confirm: one Work row in the rail; the editor sees only their own rows; the SG board still offers Board / Table / Jobs with every action; /admin/staff/action-queue?filter=overdue&client=X lands on /admin/staff/work with both parameters intact.
2. Editors in Command now work from the detail, not from cards. Claim / Start / Submit for review are on /admin/staff/work?deliverable=<id>. This is the one place the merge could have removed capability, and the one place I most want a real editor to try before this ships. The transitions are the same module the SG board uses (use-task-action.ts, lifted verbatim), and the server's compare-and-set is unchanged — but the *route* an editor takes to reach them is new.
3. `tests/admin/action-queue-visibility.test.ts` was rewritten. It is a security-adjacent test. It now asserts the data boundary (scopeActionQueueToEditor) instead of the rail, which I believe is the stronger guarantee — but the decision that "one Work route for every internal role, scoped server-side" is acceptable is Ivan's and Kris's, not mine. If they disagree, reverting is small: restore roles: STUDIO_ONLY on the internal Work row and give editors their own row again.
4. Home now makes a second read. /api/admin/action-queue in addition to /api/admin/launcher-summary. See §6.4 for the loader change that would remove it. Someone should decide whether the extra read is acceptable.
5. The `waiting` lane's membership — see §6.5. A product decision, one line to change.
6. Search copy. Work's global-search label changed from "Work / Jobs" to "Work". The words that were in the label moved into the detail line, which the search route also matches on, and the test now asserts that "jobs", "action queue", "my work" and "review" all still find the screen. Worth confirming in the real search box.
7. Everything visual. I have no browser here. The CSS changes — the wrapped phone rail, the stacked table, the sub-chip row, the action buttons, the dimmed zero tile — are reasoned, not seen. docs/design/command-redesign/ STATUS.md has been updated with the same account, for whoever picks this up.

9. What I did NOT invent

Checked against the loader before use, as instructed:

Every other number added in this batch is the length of a list of real rows, and tests/domain/operations/work-lanes.test.ts fails the build if the lane vocabulary ever mentions capacity, utilisation, health, progress, a score or a percent sign.

10. Files

New (6)

src/components/admin/work/admin-work.tsx        the one Work entry point
src/components/admin/work/use-task-action.ts    the five transitions, shared
src/domain/operations/work-lanes.ts             the five lanes (pure)
src/lib/domain/calendar-window.ts               what a calendar view draws (pure)
tests/domain/operations/work-lanes.test.ts
tests/domain/calendar/calendar-window.test.ts

Modified (30) — 24 source, 6 test. git diff --stat at the end of the batch: +1,604 / −403 across 30 tracked files, plus the 6 new ones.

Routes: src/app/admin/staff/work/page.tsx, src/app/admin/staff/action-queue/page.tsx. Styles: src/app/bulgar-command.css (Command-scoped only; SG and OG untouched). Components: admin-action-queue.tsx, admin-operations-workspace.tsx, admin-nav.ts, admin-shell.tsx, admin-command-palette.tsx, admin-workspace-launcher.tsx, admin-home-operations.tsx, admin-client-command-center.tsx, work/command-work.tsx, work/command-work-detail.tsx, work/use-action-queue.ts, home/command-home.tsx, clients/command-client.tsx, calendar/command-calendar.tsx, team/command-team.tsx, finance/command-finance.tsx, partners/command-partners.tsx. Domain / lib: domain/operations/action-queue.ts, domain/operations/home.ts, lib/admin-destinations.ts, lib/hermes-screen.ts. Docs: docs/design/command-redesign/STATUS.md. Tests: the six listed in §3.

Nothing was deleted. Two exported symbols were renamed (AdminActionQueue → AdminActionQueueSg, AdminOperationsWorkspace → AdminOperationsBoard); both had exactly one caller each, and both callers were updated.