beantownbabe
f1f0d23e7e
Mckinley wants Edit in the dash itself, not the separate localhost page - the earlier split (Add embedded, Edit stays remote) didn't hold. Built the same picker -> field -> current-value -> new-value -> submit flow as Input Interface's standalone page (reused their exact UX pattern, restyled to match this dashboard), calling their JSON API via absolute URLs (this page isn't served by their Flask app, so relative paths from their reference wouldn't resolve): GET http://localhost:8507/prospect-scout/api/entries GET http://localhost:8507/prospect-scout/api/entries/<id> POST http://localhost:8507/prospect-scout/api/edit Category field swaps to a select (matching the 6 known categories) instead of free text, same as their reference. Editing contact_email shows the same "counts as human confirmation" hint. Viewing the dashboard stays fully static/dependency-free; only Add and Edit require the backend running, same trade-off already accepted for Add. Verified via jsdom with a stubbed backend: entry list loads, field list populates per entry, current value fetches and displays, email hint shows correctly, category field renders as a select with the right value pre-selected, submit posts and updates status, and none of the existing 73 rendered cards regressed.