Commander is missing from Player's Zone #7

New Issue

veles-dev · 2026-06-28T21:45:50Z

veles-dev commented

2026-06-28 21:45:50 +00:00

What happened

I no longer see the Commander.

What should have happened

The Commander should be somewhere on the battlefield, in the hand, command zone, (even in the graveyard though it shouldn't be normally) somewhere. The commander should always be somewhere, but here Player D's commander is missing.

Context

Page URL: https://veles.bstein.dev/table?path=/data/veles-artifacts/logs/dashboard/ivory-beacon-tune/commander_pod_g1_682137069/game.jsonl
Route: table
Path: /table?path=/data/veles-artifacts/logs/dashboard/ivory-beacon-tune/commander_pod_g1_682137069/game.jsonl
Backend version: 0.4.5
Frontend version: 0.4.5
Sim version: 0.4.5

## What happened I no longer see the Commander. ## What should have happened The Commander should be somewhere on the battlefield, in the hand, command zone, (even in the graveyard though it shouldn't be normally) somewhere. The commander should always be somewhere, but here Player D's commander is missing. ## Category - kind: bridge-runtime / ui-table - severity: obvious[image](uploading ...) ## Context - Page URL: https://veles.bstein.dev/table?path=/data/veles-artifacts/logs/dashboard/ivory-beacon-tune/commander_pod_g1_682137069/game.jsonl - Route: table - Path: /table?path=/data/veles-artifacts/logs/dashboard/ivory-beacon-tune/commander_pod_g1_682137069/game.jsonl - Backend version: 0.4.5 - Frontend version: 0.4.5 - Sim version: 0.4.5

veles-dev added the

format/commander

kind/ui

severity/obvious

labels 2026-07-07 20:39:46 +00:00

bstein commented

2026-07-09 06:32:52 +00:00

Verified in Cassandra 0.5.30.

Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30.

Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed.

Issue-specific proof: compact replay/table coverage keeps command-zone/player-zone cards visible across compact hydration and transient refreshes, including metadata command-zone fallback and multi-seat shared-zone frames. Closing.

Verified in Cassandra 0.5.30. Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30. Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed. Issue-specific proof: compact replay/table coverage keeps command-zone/player-zone cards visible across compact hydration and transient refreshes, including metadata command-zone fallback and multi-seat shared-zone frames. Closing.

bstein closed this issue

2026-07-09 06:32:53 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#7