Phase 4: Warehouse screen, pull table, shorts, MTRs and the upload pipeline

The Warehouse home with the numbers, the Open shorts table, the find bar and the five-column task board
(waiting, being pulled, on hold, pulled, released in the last 3 days) with buttons, hold reasons and drag.
Every role sees the warehouse stage on a packet as the WH pill and the line under it. The pull table on the
Materials tab: Pulled with auto-start, issued, location, heat with Enter to the next line, shorts with
receipts, N/A, MTR per line with a viewer. Send back to Clerical with a reason. Release to supervisor stays
blocked until every line is pulled or short and every pulled line has a heat.

Server: the heats_recorded precondition on WH_RELEASE, receive by custody, server-validated hold and short
reasons, the old packet history texts, GET /api/warehouse/board, cards with the warehouse stage and pull
counts. Uploads typed by content per kind (drawing, mtr, document, bom with XLSX and CSV), limits per kind,
optional ClamAV behind the clamav compose profile, a storage quota alert on the new notification_events
table (migration 0005) shown on the Admin Storage tab.

Tests: every warehouse action as every role, the release gate, the short-receive exception, the heat
pattern, upload sniffing and limits, the ClamAV path with a fake scanner, the quota alert; frontend board
and pull table tests; Playwright scenarios for the board and the pull flow. Verified on docker-1 in the CI
stack: 3557 server tests, 106 frontend tests, 17 Playwright scenarios. Docs updated; D5 closed.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

server/packetstation/worker/jobs/housekeeping.py

@@ -1,10 +1,12 @@
 """Housekeeping, nightly at 03:30 site time: prune the VISUAL change rows and gone cache rows, old job runs and
-old claimed run requests. It never touches packets, the audit log or anything append-only."""
+old claimed run requests. It never touches packets, the audit log or anything append-only. Then it checks the assets
+storage against its warning threshold (assets.check_quota opens or resolves the alert)."""
 
 from __future__ import annotations
 
 from datetime import datetime, time
 
+from ...domain import assets
 from ...feed.config import FeedSettings
 from . import Counts, JobContext, JobSpec, seconds_until
 
@@ -50,6 +52,16 @@ def run(ctx: JobContext) -> Counts:
     for name, sql, days in STEPS:
         with ctx.conn.transaction():
             counts[name] = ctx.conn.execute(sql, (days,)).rowcount
+    try:
+        usage = assets.check_quota(ctx.conn, ctx.settings)
+    except Exception as e:  # the storage check never fails the pruning
+        ctx.log.exception("the storage quota check failed")
+        counts["quota_error"] = type(e).__name__
+    else:
+        counts["quota_pct"] = usage["pct"]
+        counts["quota_warn"] = usage["warn"]
+        if usage["alert"]:
+            counts["quota_alert"] = usage["alert"]
     return counts