sync: record magatama dashboard cache and port detail fix
This commit is contained in:
parent
8b42077081
commit
fd29bee5cb
@ -1,9 +1,44 @@
|
||||
# Current TIP Sync State
|
||||
|
||||
Updated: 2026-05-07 08:05 UTC
|
||||
Updated: 2026-05-09 02:05 UTC
|
||||
|
||||
## Newest Work
|
||||
|
||||
- MAGATAMA dashboard truthfulness / UX hardening on 2026-05-09:
|
||||
- live `api/llm/status` on MAGATAMA now publicly confirms the corrected `magatamallm` lane counts:
|
||||
- `15679` train / collected
|
||||
- `1743` eval
|
||||
- `17422` total
|
||||
- `15679` new since last training
|
||||
- the Training page inconsistency was traced to a stale browser/static-cache path plus mixed UI sources
|
||||
- dashboard static UI was updated and deployed live to Erik:
|
||||
- new cache version:
|
||||
- `2026-05-09a`
|
||||
- Training Control now force-merges the visible summary with the live `llmStatus.training` payload so the page and modal cannot silently disagree on pair counts
|
||||
- Switchblade network port UX was hardened:
|
||||
- hover detail remains
|
||||
- each port is now also clickable
|
||||
- click opens a real MAGATAMA-side detail modal with:
|
||||
- status
|
||||
- speed
|
||||
- description
|
||||
- peer device / peer port
|
||||
- connected host
|
||||
- VLAN
|
||||
- transceiver
|
||||
- in/out errors
|
||||
- octet counters
|
||||
- this was done because hover-only behavior was still presenting as broken / ambiguous for the operator
|
||||
- direct live deployment truth on Erik:
|
||||
- `/opt/magatama/packages/dashboard/public/index-v2.html` now contains:
|
||||
- `API_CACHE_VERSION = '2026-05-09a'`
|
||||
- `openSwitchbladePortModal`
|
||||
- `Ports · Hover = Nutzung / Status · Klick = Detail`
|
||||
- important honest remainder:
|
||||
- this fixes the visible UI inconsistency and the broken/stale port interaction path
|
||||
- it does **not yet** complete the deeper backend truthfulness issue where Atlas/host-audit raw files can still show real issues while the live open-findings surface may be empty
|
||||
- that rematerialization / anti-auto-resolve backend block still needs a dedicated follow-up pass
|
||||
|
||||
- Full cross-agent sync refresh on 2026-05-07:
|
||||
- all current MAGATAMA/RunPod training automation findings from this chat were consolidated again into `sync/`
|
||||
- latest confirmed truth:
|
||||
|
||||
@ -0,0 +1,87 @@
|
||||
# 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.
|
||||
Loading…
x
Reference in New Issue
Block a user