JAM-46 UAS company detail UI cleanup
Scope
Simplify the Mission Control UAS Database company detail page so it reads like a company review surface, not a database admin panel.
Files changed
/Users/vinny/.openclaw/workspace/mission-control/components/uas-database/CompanyDetailWorkspace.tsx/Users/vinny/.openclaw/workspace/mission-control/data/tasks.json
UI removals implemented in source
Removed from the company detail UI source only:
- internal company ID badge
- Raw JSON button
- JSON source of truth chip
- full local file path chip
- Human-readable evidence text field
- helper copy / suggested evidence block tied to that field
- Evidence confidence field
- NDAA basis field
- Linked evidence IDs field
- full Evidence traceability card
- empty-state box for missing evidence records
- structured evidence helper copy
Kept visible:
- NDAA status
- Updated chip
- status pills, including low evidence, NDAA status/unknown, Lantronix relevance, QC state
- core company, classification, segment, and product fields
Validation
Source inspection confirms the requested UI elements were removed from CompanyDetailWorkspace.tsx and copy was tightened.
Live-browser check against http://127.0.0.1:3100/uas-database/companies/company%3Abirdseyeview-aerobotics still showed the old production bundle, including:
- company ID badge
- Raw JSON button
- JSON source of truth chip
- file path chip
- Human-readable evidence text field
- Evidence traceability section
That means the 3100 Mission Control service needs a full rebuild, then restart, before the live page reflects the source change.
Remaining gaps
- I could not run the rebuild/restart flow for the launchd-managed Mission Control service from this Discord subagent session because shell execution / approval was unavailable here.
- During validation I briefly tried a built-bundle fallback under
.next, so the safe follow-up is a clean rebuild before restart. - Because the live 3100 service stayed on the old bundle, end-to-end live validation is still pending the rebuild/restart.