Status: v0.1.0 skeleton (M1 migration in progress; data layer responsibilities have been handed over to the case-progress skill). For the design source of truth see the consuming project SuitAgent
docs/case-dashboard与数据真值方案.md(v1.4, decisions #045/#046).
Responsibility boundaries
| Feature | Form |
|---|---|
| Dashboard lifecycle | /dashboard: health check 7879 → start if not running → open browser; troubleshooting for port in use / missing PyYAML / empty scan |
| Progress analysis | /dashboard --review: weekly analysis (stalled cases, compounding deadline risk, next-step recommendations), for guardrails see references/manual.md |
Project management (
/progress: adding tasks, advancing status, registering deadlines, updating stages) has belonged to case-progress skill。
Development red lines (hard constraints for symlink installation)
- Path resolution must not depend on
__file__.resolve(): this skill is installed as a symlink (e.g. SuitAgent.claude/skills/case-dashboard→ this directory),resolve()will follow the link back to this repository. The project root is always discovered via upward discovery from cwd(finding an ancestor containing a case directory starting with 6 digits) or specified via the--rootargument /SUITAGENT_ROOTenvironment variable. - Runtime data must never go into the skill directory: this repository is public, so case.yaml,
.audit.jsonl, dashboard artifacts, etc. all go into the consuming project's case directory; the skill directory contains only code and documentation. - Parameterized port: default 7879 (
DASHBOARD_PORTcan override), yielding to content-registry (8765) and idle-task-runner (7878). - Single write implementation: all writes to case.yaml go through the case-progress skill case_store CLI (this skill's server calls it via subprocess, cross-skill import is forbidden) — schema validation → line-level source protection → flock → atomic replacement.
- Zero build: the frontend is a single-file HTML, with no node_modules build chain.
Directory structure
scripts/ dashboard_server.py(薄 HTTP 路由,subprocess 调 case-progress 的 case_store CLI)—— M1 迁入
assets/ dashboard.html(前端单文件)—— M1 迁入
references/ API.md(/api/v1 契约)、manual.md(--review 说明书);字段字典 schema.md 见 case-progress skill(唯一权威)
Roadmap
M1 migration completed → M5 feature expansion; for data layer M2/M3a/M3b/M4/M6 see the case-progress skill. See TASKS.md and the consuming project's plan document (v1.4) for details.