transceiver-db/sync/history/2026-05-09-magatama-dashboard-cache-training-and-port-detail-fix.md

MAGATAMA Dashboard Cache, Training Count and Port Detail Fix

Date: 2026-05-09 02:05 UTC

Scope

Operator reported multiple MAGATAMA UI trust issues:

• Training still showed 1097 pairs in places
• Attack Paths guidance button had previously behaved like a no-op
• Switchblade port hover was unreliable / looked broken
• dashboard states felt stale or contradictory

What Was Verified

• Public https://magatama.fichtmueller.org/api/llm/status now returns the corrected magatamallm lane values:
  • collectedExamples = 15679
  • evalExamples = 1743
  • totalExamples = 17422
  • newSinceLastTraining = 15679
• Erik live file verification confirmed the new dashboard HTML is deployed:
  • API_CACHE_VERSION = '2026-05-09a'
  • openSwitchbladePortModal(...)
  • Ports · Hover = Nutzung / Status · Klick = Detail

Changes

1. Dashboard cache invalidation

The public dashboard static UI cache key was bumped so browsers stop reusing stale localStorage/API cache state:

• file:
  • magatama/packages/dashboard/public/index-v2.html
• new cache version:
  • 2026-05-09a

2. Training count truthfulness

The Training page summary now force-merges the displayed training summary with the live state.llmStatus.training payload.

Effect:

• if training-control or stale cached page state lags behind,
• the operator still sees the live lane count from api/llm/status
• page cards and modal are less likely to disagree silently

3. Switchblade port intelligence UX

Port chips in MAGATAMA’s Network / Switchblade section were upgraded from hover-only to hover + click:

• hover still updates the inline usage/status area
• click now opens a real MAGATAMA detail modal with:
  • port label
  • switch/device
  • status
  • speed
  • description
  • peer device
  • peer port
  • connected host
  • VLAN
  • transceiver
  • error counters
  • octet counters

This makes the port view resilient even when browser hover behavior or pseudo-tooltip rendering is unreliable.

Deployment

Live-synced to Erik:

• /opt/magatama/packages/dashboard/public/index-v2.html

Dashboard health still answered:

• https://magatama.fichtmueller.org/api/health

Important Remaining Truth

This fixes the operator-facing dashboard inconsistency and stale/static interaction problems.

It does not yet fully solve the deeper backend truthfulness problem:

• Atlas / host-audit raw files can still show real problems
• while live open findings may still appear empty

That backend rematerialization / anti-auto-resolve chain needs a separate follow-up fix.