The 'X alerts' and 'X warns' badges in AlertCard and AlertListRow
had no whitespace-nowrap, so '2 alerts' could wrap to two lines on
narrow viewports. Add whitespace-nowrap in both AlertCard and
AlertListRow variants of the alert-red and warn-amber badges.
The Type column badge had no whitespace-nowrap, so 'Fleet (L)' /
'Plant (h)' wrapped inside the pill whenever the table column was
narrow. Add whitespace-nowrap to the badge className so the label
stays single-line at any column width.
Tighten padding, gap, and rounding on the alert cards and the
Fleet mobile card so they take less vertical and horizontal real
estate on narrow viewports. Layout restores to the roomier
current sizing once the screen reaches the 'sm' breakpoint (640px).
Per-card changes:
- AlertCard (mobile): gap-3 -> gap-2 sm:gap-3; p-4 -> p-3 sm:p-4.
- AlertListRow (desktop list): px-4 py-3 -> px-3 py-2 sm:px-4 sm:py-3;
gap-3 -> gap-2 sm:gap-3.
- FleetMobileCard (mobile): gap-2 -> gap-1.5 sm:gap-2; p-3 -> p-2.5
sm:p-3.
The leading text in alert cards (mobile + desktop) and fleet rows
wrap to a multi-line layout when the description + project badge +
status pill can't all fit horizontally. The inner flex containers
holding the description span already had 'truncate' on the span,
but were missing 'min-w-0', so the flex children couldn't shrink
below their content size.
Add 'min-w-0' to four inner flex containers:
- AlertCard top row (mobile alert cards)
- FleetMobileCard edit-mode meta row (project badge + fuel-limits +
UnitTypeSelect)
- FleetMobileCard non-edit meta row (project badge + UnitTypePill +
fuel-limits)
- FleetRow top cell (desktop fleet row, Description or Link)
Add native 'title' attribute on the three truncatable description
spans (AlertCard, AlertListRow, FleetMobileCard non-edit) so the
full vehicle name is available on hover as a fallback for the
ellipsis truncation.
The vehicles PB collection already has a unit_type field (fuel |
plant, default fuel, made optional on 2026-08-28) and the
PATCH /api/vehicles/[id] endpoint accepts it with full test
coverage. Today there is no UI surface for assigning or changing a
vehicle's unit_type on either the Fleet page (/dashboard/fuel) or
the Plant page (/dashboard/plant), so the 53 currently mis-classified
vehicles cannot be triaged from the UI.
This spec adds that surface via the existing inline-edit pattern
already used on both pages for description editing: a Type column
renders a 'Fleet (L)' / 'Plant (h)' badge in display mode and a
Select in edit mode. Saving a flip calls PATCH /api/vehicles/[id];
on success router.refresh() re-pulls the page and the row drops
out of the page's filter, effectively moving it to the other page.
Scope is intentionally tight:
- Server-side filter on each page (Fleet: unit_type=fuel or empty;
Plant: unit_type=plant AND cost_per_hour > 0).
- New Type column on the existing Fleet and Plant tables (no new
pages, no new top-level nav).
- New shared <UnitTypePill> / <UnitTypeSelect> cell components.
- Reuses the generic useInlineEdit<K extends keyof T> hook (no
hook changes needed).
- No schema migration, no API changes, no new tests.
Spec self-review pass: tightened two claims (pb-types.ts UnitType
line 37 not 48; useInlineEdit is already generic so no hook edit).
The PO upload route (and the delivery-notes and xlsx import
paths) writes the uploaded file into the DATA_IMPORT_BATCHES.
original_file field. That field was bootstrapped with a CSV/Excel
allowlist only:
text/csv, text/plain, application/vnd.ms-excel, application/csv
When the upload route was rewritten on 2026-08-19 (commit f0f7c82)
to write directly to PB instead of forwarding the file to n8n, every
PDF and image upload started failing PB field validation with
validation_invalid_mime_type, surfacing in the API as a 500 with
error='batch_create_failed' and the real cause buried in
pb_data.original_file. The 2026-08-24 migration that should have
added xlsx was also never applied to prod (verified in PB:
xlsx missing too).
Migration: scripts/migrations/2026-08-31-data-import-batches-allow-pdf-images.py
- Strictly additive: unions the new mimeTypes onto the existing
allowlist, exits no-op if already applied (verified idempotent).
- Adds application/pdf, image/jpeg, image/png, image/webp (PDF /
image support for the PO and delivery-note flows) and
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
(xlsx, completing the missed 2026-08-24 migration).
- No code change in the upload routes required - they were already
validating against ALLOWED_MIME in purchase-order-schema.ts and
expecting PB to accept the same set.
Verification on https://pb.mega.infra.apphub.co.za:
Before: POST /api/purchase-orders/upload (PDF) -> HTTP 500,
pb_data.original_file.code = 'validation_invalid_mime_type'.
After: same POST -> HTTP 202 with batch_id, PB row created
(batch_type=purchase_orders, status=pending, file_hash
populated, original_file stored).
Three concerns from testing:
1. Chat typing UX: the textarea was disabled while a request was in
flight, so the user couldn't draft the next question. Removed the
disabled attribute; Enter is just a no-op while busy. Send button
still gates actual submission.
2. Sticky footer: switched the chat wrapper to 100svh (mobile-keyboard
aware) and made the composer sticky bottom-0 with a solid background
so it no longer fades into the scroll area.
3. Limit-warning: the SSE stream now reads the 'done' event and surfaces
a banner when the server reports the agent loop hit its iteration
cap, so a quiet stream end isn't mistaken for a complete answer.
Sidebar: added 'Ask' nav item pointing at /dashboard/chat with the
Sparkles icon so the chat is reachable from the dashboard even if the
standalone-PWA install path keeps misbehaving.
Next 16's appleWebApp metadata API only emits `mobile-web-app-capable`,
which iOS Safari ignores for Add-to-Home-Screen standalone mode. The
home-screen icon launches the page inside regular Safari with full
browser chrome instead of as a standalone app.
Adding the iOS-specific `apple-mobile-web-app-capable` tag to the root
layout's <head> so the home-screen bookmark launches without Safari UI.
Harmless on non-iOS browsers (those use `mobile-web-app-capable` which
Next already emits).
The next-pwa plugin's `manifest` option is silently ignored in
@ducanh2912/next-pwa@10.2.9 — only the service worker is generated.
The dashboard Web App Manifest now lives as a static file at
public/manifest.json, sourced from the next.config.js block we just
removed. This is the same shape the project shipped at HEAD~3, just
with the new short_name and id field added by Task 4.
Probing 'combined value of the top three delivery notes' against the
production model returned R 3 285 785 — arithmetically correct, exactly
what the ban was written to prevent.
The previous prompt said 'never do arithmetic' but did not say what
to do instead when the user explicitly asks for an aggregate. The
model picked the path of least resistance and summed them.
New prompt lists the verbs that count as arithmetic (including average,
percent, ratio, weighted, combined, total, sum) and gives the model a
concrete response shape: report each row's value, declare the
aggregate 'not available from me', tell the user which number is
missing.
Re-probed — the model now lists the three values individually and
declines the sum.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Hides app chrome via a 'printing-answer' class on body, leaves only the
.print-target visible. The class is removed in a finally so a cancelled
print dialog can't leave the app invisible.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds a camera button next to the paperclip that opens the device camera
on phones (capture='environment') and a file picker otherwise. Photos
are read into base64 and sent with the next user turn.
Pending photos render as a thumbnail strip above the composer with a
remove button each. The state had to be hoisted above the composer
handlers — useCallback closes over it at handler-creation time, so
declaring it lower in the file produces a TS2448.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Anthropic adapter: image content block before text.
OpenAI-compatible adapter: image_url with a data: URL.
Route normalizer carries images through the trust boundary.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
M2.7 is text-only; M3 is the first MiniMax model that accepts both the
tools parameter and image inputs on the OpenAI-compatible endpoint.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Closes the coverage gaps: delivery notes, plant hours, fixed costs,
income claims, the employee roster and import batches. Each takes an
optional site, an enumerated sortBy and a limit, so list/highest/lowest
questions work across every collection.
Verified live against the dashboard:
- list_delivery_notes sorts by value; top result AS0002086 at R3 255 444
- list_employees returns 72 (16 permanent + 56 casual)
- list_imports returns 44 batches, none failed
- list_plant_hours returns 0 rows — same as /dashboard/plant
(the production plant_hours_log collection is empty today)
- list_fixed_costs / list_income_claims wired through same shape
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Six new loaders: delivery notes (with received items bucketed for
value computation), plant hours, fixed costs, income claims, employees
and import batches. Each takes optional filters rather than full
queries, so callers always run through typed tool handlers.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
delivery_notes stores no value; a note is worth the quantity received on
each line times the matched PO item's rate. Unmatched lines contribute
zero rather than a guessed rate.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Queried by two dashboard pages and the agent loader, but previously
untyped — those reads compiled only because untyped getFullList returns
loose records.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The root layout hardcoded <link rel="manifest" href="/manifest.json">
in its head. Next's metadata API cannot override a hand-written tag, so
/dashboard/chat emitted two manifest links — browsers honour only the
first, making which app installed depend on tag order.
Declaring it as metadata.manifest lets the chat route's own manifest
replace it. Each route now emits exactly one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The chat page now exports Metadata that points at /chat.webmanifest and
declares appleWebApp for Safari's Add to Home Screen path (which
ignores manifest scope rules).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The dashboard's manifest is generated by next-pwa from next.config.js.
A second static manifest in public/, linked from the chat page,
installs as its own app called Ask. The explicit id field stops the
two manifests on the same origin from being treated as updates to one
another.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reuses the existing /api/purchase-orders/upload endpoint with a 20 MB
cap, SHA-256 dedup, MIME allowlist and a status poll. The model never
enters the write path — the human uploads, and the agent only reads
the result. read-only.test.ts is unmodified.
Also made the paperclip button more visible: a plain grey-on-grey
icon is easy to miss for a primary input. Now it has a bordered
treatment consistent with the send button.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The status endpoint reports a PB record id, which is meaningless to the
chat upload card. Resolve it to the readable order number when the
batch type is purchase_orders, and leave the label null otherwise.
Failure to resolve the PO (e.g. it was deleted) is swallowed — the
batch status still stands and the raw id is still in the response as
the fallback.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Brings the tool set to 11. All five build on the same metrics pass the
dashboard uses, so per-fill variance, per-worker totals and the
underlying records reconcile with the pages they sit next to.
Also: sort='-created' on purchase_orders returns HTTP 400 from
PocketBase for this collection. Switched to -required_by_date, which
sorts by ordering recency — closer to what a project manager wants
than document creation time anyway.
Caught by calling list_purchase_orders against live data; the test
suite does not cover the live sort syntax.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both build on the same metrics pass the dashboard uses, so per-fill
variance and per-worker totals reconcile with the pages they sit next
to. No new business math — the data already existed, but no tool
exposed it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Mirrors resolveSite: id, then QR code, then exact description, then
substring — and ambiguity is reported, never guessed. Picking the wrong
vehicle silently attributes fuel spend to the wrong machine.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The models return GFM — tables of vehicles, bold figures, lists — and
the view rendered it as preformatted text, so users saw raw pipes and
asterisks.
Answers now render through react-markdown with every element mapped to
this app's own conventions: tables get the borders, muted header and
hover of components/ui/table.tsx, and numeric columns get tabular-nums
so rand figures line up as they do on the fuel and sites pages.
Alignment is computed per COLUMN, not per cell — the table inspects its
own rows, decides which columns are numeric, and publishes that through
context so a header never ranges left above a right-ranged figure.
Layout: questions are compact chips, answers are full-width documents
with a thin amber rule. Bubbles fight tables. Each answer carries a
provenance strip naming the tools it used — for a tool whose value is
that its numbers reconcile with the dashboard, the source is part of the
answer.
Motion is limited to a streaming caret and the running-tool pulse, both
disabled under motion-reduce.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The browser sends assistant turns as {role, text} with no toolCalls, so
both adapters threw 'Cannot read properties of undefined (reading
length)' on the second message. The ChatEntry type guarantees nothing
across a JSON boundary.
Normalizes history at the route (the trust boundary) and makes both
adapters defensive.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
MiniMax M2.x emits its chain of thought inline in `content` wrapped in
<think> tags, so the user watched the model reason at itself before
every answer. Anthropic returns reasoning as separate thinking blocks,
so this is a provider quirk and the filter lives in the OpenAI-compatible
adapter only.
Tags can straddle chunk boundaries ('<thi' + 'nk>'), so the filter is a
small state machine that holds back a short tail rather than emitting
text that might turn out to start a tag. Verified character-by-character.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
