Skip to content

Add the Fleet Wall: every open case as a square, grouped by workflow - #2273

Draft
G-r-ay wants to merge 1 commit into
mainfrom
feat/fleet-wall
Draft

G-r-ay wants to merge 1 commit into
mainfrom
feat/fleet-wall

Conversation

@G-r-ay

@G-r-ay G-r-ay commented Oct 14, 2026

Copy link
Copy Markdown
Collaborator

What

A Fleet Wall console screen (nav: Overview → Fleet Wall). It draws every open case as one square in its workflow's band.

  • Squares are coloured by state: needs you, stuck, running, near its limit, paused, on hold, waiting. A thick outline means 5 or more alerts were combined into the case. Pointing at a square shows a one-line readout; clicking selects it into a panel that opens the case.
  • Strip: slots in use against the cap, and cases closed today against yesterday.
  • Filters by state, remembered for the session.
  • Band header: open cases, slots in use with a bar and level, runs today, and how many are waiting.
  • Layout: the bands scroll inside the view; the head, strip, filters and the "just closed" row stay put.

The API is a contract, not an implementation

GET /api/fleet-wall is defined by FleetWallPayload in core/monitor/models.py:

  • The route validates every answer against the model.
  • schema.d.ts is generated from it, and the console's types alias it.
  • Each field's description says what it counts. The open decision (what "slots" means) is flagged in the model.

The read itself (core/monitor/wall.py) is not implemented:

  • The route answers 501 and the screen shows its error state.
  • In demo mode it serves a seeded sample (core/monitor/fixtures.py). That sample is also built from the models, so it cannot drift from the contract.

The read's docstring lists each field's source and the TODOs for whoever implements it, e.g. index the run-by-case lookup before polling it every 10 s.

Tests

  • tests/unit/monitor/: 501 when unbuilt, demo fixtures satisfy the contract, a read that drops a field or sends an unknown state is refused, plus the level and time helpers.
  • monitor.test.tsx: the wall draws, filters, selects and opens a case.
  • SocConsole.test.tsx: nav order and separators.
  • The full vitest run has one timeout, "navigates primary screens and the More menu". It fails the same way on untouched main.

Origin

Taken from @krmayankb's krmayankb/vigil PR #7 (fleet/console-monitor), credited as co-author. The data reads are left as 501 stubs, and the screen gained more of the design (states, hover readout, band slots, scrolling bands).

Pulse is the follow-up PR, stacked on this one.

A console screen that draws each open case as one square in its
workflow's band, coloured by state (needs you, stuck, running, near its
limit, paused, on hold, waiting), under a strip of slots in use against
the cap and cases closed today. Pointing at a square reads it; clicking
selects it into a panel that opens the case. The bands scroll inside the
view while the strip and filters stay put.

GET /api/fleet-wall validates its answer against FleetWallPayload in
core/monitor/models.py, and the console's types are generated from it.
The read itself is not implemented: the route answers 501 and the screen
shows its error state, except in demo mode, where it serves the seeded
sample in core/monitor/fixtures.py.

Taken from krmayankb/vigil PR #7 (fleet/console-monitor).

Co-authored-by: krmayankb <krmayankb@gmail.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Signed-off-by: gray <egboluche.g@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant