Remove old inline dashboard snapshot from production builds #5

New Issue

MrSphay · 2026-05-17T11:21:50Z

MrSphay commented

2026-05-17 11:21:50 +00:00

Created from local project scan after fixing the live-data bug.

Current status: dashboard/public/jarvis.html still contains a large inline April 2026 snapshot as offline fallback. The server now ignores it and fetches /api/data, but keeping old operational-looking data in the shipped HTML remains confusing and risky for cache/offline scenarios.

Acceptance criteria:

Production Docker/dashboard runtime should ship a shell without stale operational data embedded in D.
Offline/demo mode must be explicit and visibly labeled as demo/offline if retained.
inject.mjs static injection remains available only as a CLI/build helper, not as hidden production fallback.
Add a small regression check that server-mode dashboard fetches /api/data before rendering operational data.

Created from local project scan after fixing the live-data bug. Current status: dashboard/public/jarvis.html still contains a large inline April 2026 snapshot as offline fallback. The server now ignores it and fetches /api/data, but keeping old operational-looking data in the shipped HTML remains confusing and risky for cache/offline scenarios. Acceptance criteria: - Production Docker/dashboard runtime should ship a shell without stale operational data embedded in D. - Offline/demo mode must be explicit and visibly labeled as demo/offline if retained. - inject.mjs static injection remains available only as a CLI/build helper, not as hidden production fallback. - Add a small regression check that server-mode dashboard fetches /api/data before rendering operational data.

MrSphay commented

2026-05-17 12:04:34 +00:00

In Bearbeitung durch Codex auf Branch codex/issue-5-dashboard-shell. Scope: alten inline Dashboard-Snapshot aus production jarvis.html entfernen bzw. Demo/offline eindeutig machen, server-mode /api/data Fetch vor Operational-Rendering absichern, kleiner Regressionstest. Keine Source-/Docker-/Alert-Aenderungen, damit parallele Branches sauber mergbar bleiben.

MrSphay commented

2026-05-17 12:08:53 +00:00

PR geoeffnet: #20\n\nStatus: Umsetzung fuer Issue #5 ist fertig auf Branch codex/issue-5-dashboard-shell. Der alte April-2026-Snapshot ist aus jarvis.html entfernt, Server-Mode fetches /api/data vor init/render, offline/file mode nutzt nur eine explizite Offline-Shell. Lokale npm/node Tests nicht ausgefuehrt; Runner soll npm run test:unit pruefen.

PR geoeffnet: https://git.wilkensxl.de/MrSphay/intelligence-terminal/pulls/20\n\nStatus: Umsetzung fuer Issue #5 ist fertig auf Branch codex/issue-5-dashboard-shell. Der alte April-2026-Snapshot ist aus jarvis.html entfernt, Server-Mode fetches /api/data vor init/render, offline/file mode nutzt nur eine explizite Offline-Shell. Lokale npm/node Tests nicht ausgefuehrt; Runner soll npm run test:unit pruefen.

MrSphay commented

2026-05-17 12:34:41 +00:00

Update: PR #20 wurde auf die aktuelle codex/production-intelligence-terminal rebased und ist wieder mergeable. Konflikt in dashboard/public/jarvis.html geloest: neue Terminal-Actions-UI bleibt erhalten, alter Inline-Snapshot bleibt entfernt. Runner-only: keine lokalen npm/node Tests.

MrSphay closed this issue

2026-05-17 19:12:28 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MrSphay/intelligence-terminal#5