CIAgent
61221222eb
Apply 10 binding grill fixes (G-001..G-010) to PLAN.md: - G-001: /api/byom/test-inference flagged as M3-deprecation proxy for REQ-008 - G-002: Trigger.dev health writes to runtime_health, NOT audit_log - G-003: Trigger.dev bootstrap + SSH whitelist hook annotated as M2/M3 pre-investments with expected payoff - G-004: CheckCommand signature + whitelist JSON locked as M2 contract - G-005: relay token contract (signed JWT, 24h) defined in Wave A so B and D parallelize without blocking - G-006: per-tenant audit hash-chain concurrent-write serialization documented as known M1 limit; M3 mitigation noted - G-007: shadow exec.Cmd integration test added to whitelist hook - G-008: explicit Wave D scope statement - M1 ships REQ-026 partially - G-009: unsupported-OS test matrix expanded to >=2 cases - G-010: two-tier credential taxonomy (infra env vars vs tenant SecretProvider-only) documented MVP/UX check: all 3 sections present in PLAN.md (User-Facing Surface, Happy Path, UX Acceptance Criteria). Gate PASS, EXECUTE unblocked. Checkpoint: stage=mvp_ux_check. ---ci--- phase: 0 milestone: v0.1 status: mvp_ux_check ---/ci---
2.1 KiB
2.1 KiB
MVP/UX Check (Phase 0 gate)
Per the run workflow, the MVP/UX checkpoint (REQ-MVP-UX-001) runs between GRILL and EXECUTE. At full autonomy, the orchestrator verifies the 3 sections are present in PLAN.md and auto-generates any missing sections.
Verification
PLAN.md (.ciagent/PLAN.md) is checked for the 3 mandatory sections:
| Section | Required | Present | Location | Content |
|---|---|---|---|---|
## User-Facing Surface |
yes | ✓ | PLAN.md line 49 | Names the M1 user-facing surface: Platform Lead admin dashboard (browser, Next.js, at /dashboard). Lists 8 specific dashboard surfaces (SSO entry, onboarding checklist, BYOM config form, relay install instructions, targets list, target detail, team/RBAC, audit export) + 3 non-UI operator surfaces (install script, Go binary, systemd unit). Explicitly states chat UI is M3, not M1. |
## Happy Path |
yes | ✓ | PLAN.md line 66 | End-to-end M1 scenario written BEFORE execute. Maps to spec Journey 2 (steps 1–4 + 7 + 9). 8 BDD steps (Given/When/Then) covering: SSO signup + tenant provision, BYOM validate-and-save, install script on Ubuntu 24.04, Relay Agent registration + heartbeat, dashboard green, team invite + RBAC enforcement, cross-tenant isolation, unsupported-OS abort. States this Happy Path IS the M1 demo recording required by the M1 review. |
## UX Acceptance Criteria |
yes | ✓ | PLAN.md line 86 | 9 explicit pass/fail criteria: SSO <3 clicks, BYOM feedback synchronous <10s, dashboard green within 90s of first heartbeat, install command copy-pasteable, RBAC enforced on next call, cross-tenant isolation verifiable, audit append-only (UPDATE/DELETE fails), secrets never in DB (scan returns zero), unsupported OS aborts cleanly. Each maps to a REQ. |
All 3 sections present and substantive. No auto-generation needed.
Verdict
PASS — PLAN.md satisfies REQ-MVP-UX-001. EXECUTE is unblocked.
Post-check actions
- Update CHECKPOINT.json:
stage: "mvp_ux_check"→ next: PHASE 0 SHIP. - Proceed to Phase 0 ship (tag
v0.0.1, mergephase/00-pre-execution→milestone/v0.1-bootstrap).