feat(admin): add backend-authoritative orchestration command center and usage view

This commit is contained in:
devops committed 2026-10-22 18:54:24 +00:00
1 parent e5c83e87fe
commit c8a3f35b0a
16 files changed
+510 -373

No files matched your search

@@ -0,0 +1,21 @@
# Verification and remaining integration work
Remote branch: feature/orchestration-v4-admin. All source changes limited to frontend/admin-panel. No push, deployment, production container command, or live operational mutation performed.
Disposable node:22-bookworm runners, --userns=host:
- Full `vitest run --maxWorkers=2`: 57 files, 326 tests passed, zero failed.
- Scoped ESLint for all new services/components/tests plus Monitoring: exit 0.
- `npm run typecheck` (solution config): exit 0, not an app check.
- `tsc --noEmit -p tsconfig.app.json`: exit 2, 33 pre-existing diagnostics (legacy unused imports/locals, Orders requiresRx type, Symptoms ConfirmModal props). No diagnostics in new files or Monitoring. Baseline captured before implementation had same legacy errors.
- `npm run build`: exit 0; pre-existing unresolved Shabnam font warning.
TDD red/green cycles exercised adapter missing exports, unadvertised actions, incomplete/expired Gate2 bindings, exact version/idempotency payloads and retry lock, task creation bounds, UI explicit confirmation, monitoring fake values and failures, navigation, router usage contract migration/unavailable state. Full UI tests use mocked HTTP boundary with realistic backend DTOs; they are not a live backend integration test. Additional UI tests cover immutable artifact binding, kill authorization failure, readiness BLOCKED response, chat escaping and typed bridge. Router usage aligned to concrete backend b0f4636 contract.
Remaining gaps / do not claim full end-to-end operation:
- Backend must advertise availableActions. Initial core worktree lacks them; client intentionally fails closed read-only without actions.
- Agents/model-policy/schedules/releases snapshots and typed chat bridge are proposed contracts, not initially present core routes. UI displays explicit unavailable errors, never synthetic content. Mutating model policy/schedules/agent operations not implemented against guessed endpoints.
- Kill switch current level cannot be read until backend exposes a status contract. No invented resume command.
- No live auth credentials used; endpoint auth/RBAC and cross-worker DTO integration still need isolated stack smoke tests.
- Legacy Approvals/Tasks/HQ/Audit pages remain separately available and unchanged. New v4 control center is at /orchestration inside existing protected layout; these legacy pages are not v4 authority and should be retired/migrated during integration.
- Full app typecheck is not green due existing errors listed above.
- Browser chat is advisory; no Hermes terminal or raw runtime connection.