CIAgent
0c15d3d0b2
M2 delivers the read-only MCP capability broker gateway and four Day-1 infrastructure adapters (Proxmox, SSH/Linux, GitHub, Gitea). 13 REQs (015-027) all pass. 656 tests green. M1 non-regression verified. MCP spec 2025-06-18 conformance verified (PROTOCOL.md + 7 tests). Defense-in-depth SSH (broker layer 1 + Relay Agent layer 2 + no-shell exec). Two-track LLM smoke (Track A mock-path P0 gate passes). CI: Gitea Actions (.gitea/workflows/ci.yml) with Postgres 16 + RLS verification. Phases shipped: P0 pre-execution v0.1.0 P1 Wave F — MCP gateway v0.1.1 P2 Wave G — Proxmox v0.1.2 P3 Wave H — SSH/Linux v0.1.3 P4 Wave I — Git adapters v0.1.4 P5 Wave J — SSE+smoke+UI v0.1.5 P6 Final — review+ship v0.1.6 ← milestone release ---ci--- phase: 6 milestone: v0.2 status: complete phase_role: final milestone_complete: true requirements: covered: [REQ-015, REQ-016, REQ-017, REQ-018, REQ-019, REQ-020, REQ-021, REQ-022, REQ-023, REQ-024, REQ-025, REQ-026, REQ-027] partial: [] ---/ci---
2.8 KiB
2.8 KiB
MVP/UX Check — CoreCI Chat v0.1 M2
Date: 2026-08-25
Plan: .ciagent/PLAN.md (M2 — MCP Layer & Day 1 Adapters)
Spec: .ciagent/steer-m2-spec.md v1.0 (locked 2026-08-25)
Checker: ciagent (autonomous, full autonomy)
Verification
| Section | Present | Substantive | Location | Notes |
|---|---|---|---|---|
## User-Facing Surface |
yes | ✓ | PLAN.md line 69 | TWO user-facing surfaces named: (1) Settings → Adapters configuration UI (/dashboard/settings/adapters) — adapter type picker (4 types), per-adapter config forms, SecretProvider-backed credential entry, role/scope validation, "Test connection" button, multi-target support, introspection gap help text. (2) Test-Call UI (/dashboard/test-call) — capability picker (9-tool closed set), argument forms (JSON Schema), target picker, SSE stream consumer, staleness indicator, result rendering. Non-UI surfaces enumerated (broker, adapters, llm-mock, mcp_adapters table). Explicitly states chat UI is M3, not M2. |
## Happy Path |
yes | ✓ | PLAN.md line 104 | End-to-end M2 scenario written BEFORE EXECUTE. Maps to spec §3.2 Journey 1 (adapter config) + Journey 2 (Test-Call). BDD Given/When/Then steps covering: adapter config + validation, Test-Call capability invocation, write rejection at broker (Edge 1), SSH whitelist violation (Edge 7, defense-in-depth), multi-target disambiguation (Edge 3), rate limit (Edge 5), SSE client disconnect (Edge 8), LLM smoke (gate item 8, two-track). States the Happy Path IS the M2 gate demo. |
## UX Acceptance Criteria |
yes | ✓ | PLAN.md line 151 | 11 explicit pass/fail criteria: adapter config saves <5s with validation, test connection <5s, SSE stream starts <100ms, staleness indicator for cached inventory, write attempts rejected at broker 403 before adapter, SSH non-whitelist rejected at BOTH layers (broker + Relay Agent), multi-target picker for ≥2 same-type, rate limit 429 + Retry-After, LLM smoke Track A passes reliably (P0), LLM smoke Track B optional, adapter audit events visible in audit export. Each maps to a REQ or gate item. |
Verdict
PASS — all 3 mandatory MVP/UX sections present and substantive. The plan passes the MVP/UX checkpoint gate (REQ-MVP-UX-001). The User-Facing Surface names 2 dashboard UIs (Settings → Adapters + Test-Call) with specific routes and component descriptions. The Happy Path has BDD steps covering all 8 spec edges + the LLM smoke gate. The UX Acceptance Criteria has 11 measurable pass/fail thresholds with REQ mappings.
Post-check actions
- All 3 sections present (verified above)
- No auto-generation needed (sections were written by ci-planner, verified by orchestrator)
- Grill fixes G-014 (closed-tool-set gap documentation in UI help text) integrated into the User-Facing Surface section
- Proceed to Phase 0 ship