docs: finalize cross-project planning items

- Mark MVP scope as finalized
- Define release order across submodules
- Document rollback/degradation strategy
- Close CLI contribution note item
- Close repo-config-safe note
This commit is contained in:
zhi
2026-03-22 01:38:17 +00:00
parent 44f5d50261
commit 62ac7453a5

View File

@@ -8,7 +8,10 @@
## 0. Cross-cutting / coordination
- [ ] Finalize MVP scope for first shipping version of `hf`
- [x] Finalize MVP scope for first shipping version of `hf`
- MVP includes: all CRUD commands for users, roles, projects, milestones, tasks, meetings, support, proposals, monitor
- Permission-aware help system, padded-cell/manual mode, code-first resource addressing
- Plugin installer `--install-cli` for automated deployment
- [x] Confirm which existing backend routes can be reused vs which new routes are needed
- [x] Define canonical code-first lookup policy across all resources
- [x] Define permission introspection strategy for `--help` / `--help-brief`
@@ -22,8 +25,16 @@
- Monitor exposes `GET /health`, `GET /telemetry`, `POST /openclaw` on 127.0.0.1:MONITOR_PORT
- Plugin pushes OpenClaw metadata via POST /openclaw; Monitor enriches heartbeats with received data
- All communication is optional/degradable — both sides function independently
- [ ] Define release order across submodules
- [ ] Define rollback strategy if plugin / monitor bridge is unavailable
- [x] Define release order across submodules
- 1. Backend (code-first APIs, permission introspection)
- 2. CLI (depends on backend API surface)
- 3. Frontend (code-first UI, independent of CLI)
- 4. Monitor (standalone, bridge is optional)
- 5. Plugin (depends on CLI build for --install-cli, depends on Monitor for bridge)
- [x] Define rollback strategy if plugin / monitor bridge is unavailable
- Graceful degradation: Monitor operates normally without plugin data
- Plugin operates normally without Monitor bridge
- No hard dependency in either direction — bridge is optional enrichment
> Note: the CLI contract items above are now documented from the currently implemented `HarborForge.Cli` behavior; they can still be refined later if a stricter release contract is needed.
@@ -37,7 +48,8 @@
- [x] Add internal package layout (`config`, `help`, `mode`, `passmgr`, `client`, `commands`)
- [x] Add build instructions to `README.md`
- [x] Add `.gitignore` for Go artifacts
- [ ] Add repo-config-safe contribution note if needed
- [x] Add repo-config-safe contribution note if needed
- CLI README already contains build/run/install docs; no separate contribution note needed for current scope
### 1.2 Runtime mode detection
- [x] Implement `which pass_mgr` detection on startup