Context
The Operations Home now reads live runtime data through same-origin /work/api/*, brokered by the authenticated portal into the private work-engine Lambda. Production uses that path, but current local-dev routes and smoke tests do not fully exercise the browser-to-broker-to-work-engine flow.
Related: #10, #45, #49.
Acceptance Criteria
- Local frontend/dev server setup can return JSON for
/work/api/health and representative /work/api/tasks requests instead of falling through to index.html.
- A smoke or integration test verifies the frontend uses
/work/api/* for dashboard runtime data, not bare /api/*.
- Auth/session failure for live work API calls is tested so login HTML cannot render as an empty dashboard.
- Documentation explains how to run the portal plus work-engine locally for dashboard development.
Notes
Commit d981f47 tightened the request helper to reject non-JSON API responses; this issue is about environment and end-to-end coverage.
Context
The Operations Home now reads live runtime data through same-origin
/work/api/*, brokered by the authenticated portal into the private work-engine Lambda. Production uses that path, but current local-dev routes and smoke tests do not fully exercise the browser-to-broker-to-work-engine flow.Related: #10, #45, #49.
Acceptance Criteria
/work/api/healthand representative/work/api/tasksrequests instead of falling through toindex.html./work/api/*for dashboard runtime data, not bare/api/*.Notes
Commit d981f47 tightened the request helper to reject non-JSON API responses; this issue is about environment and end-to-end coverage.