Initial ForgeLM import
This commit is contained in:
commit
a392b9dc60
4296 files changed
+1212675
No files matched your search
@@ -0,0 +1,98 @@
|
||||
---
|
||||
gsd_state_version: 1.0
|
||||
milestone: v1.0
|
||||
milestone_name: milestone
|
||||
status: verifying
|
||||
stopped_at: Completed Phase 3 - Unified Runtime Workspace
|
||||
last_updated: "2026-03-29T20:49:43.441Z"
|
||||
last_activity: 2026-03-29
|
||||
progress:
|
||||
total_phases: 4
|
||||
completed_phases: 3
|
||||
total_plans: 9
|
||||
completed_plans: 9
|
||||
percent: 50
|
||||
---
|
||||
|
||||
# Project State
|
||||
|
||||
## Project Reference
|
||||
|
||||
See: `.planning/PROJECT.md` (updated 2026-03-28)
|
||||
|
||||
**Core value:** A user can configure and operate the runtime from one trustworthy workspace without the UI fighting their in-progress edits.
|
||||
**Current focus:** Phase 3 - Unified Runtime Workspace
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: 3 of 4 (Unified Runtime Workspace)
|
||||
Plan: 3 of 3 authored for current phase
|
||||
Status: Phase complete — ready for verification
|
||||
Last activity: 2026-03-29
|
||||
|
||||
Progress: [█████░░░░░] 50%
|
||||
|
||||
## Performance Metrics
|
||||
|
||||
**Velocity:**
|
||||
|
||||
- Total plans completed: 6
|
||||
- Average duration: 13min
|
||||
- Total execution time: 1.3 hours
|
||||
|
||||
**By Phase:**
|
||||
|
||||
| Phase | Plans | Total | Avg/Plan |
|
||||
|-------|-------|-------|----------|
|
||||
| 01 | 3 | 46min | 15min |
|
||||
| 02 | 3 | 33min | 11min |
|
||||
|
||||
**Recent Trend:**
|
||||
|
||||
- Last 5 plans: 02-03 (13min), 02-02 (14min), 02-01 (6min), 01-03 (18min), 01-02 (18min)
|
||||
- Trend: Improving
|
||||
|
||||
| Phase 01 P01 | 10min | 2 tasks | 4 files |
|
||||
| Phase 01 P02 | 18min | 2 tasks | 4 files |
|
||||
| Phase 01 P03 | 18min | 2 tasks | 5 files |
|
||||
| Phase 02-lifecycle-command-safety P01 | 6min | 2 tasks | 3 files |
|
||||
| Phase 02-lifecycle-command-safety P02 | 14min | 2 tasks | 5 files |
|
||||
| Phase 02-lifecycle-command-safety P03 | 13min | 2 tasks | 7 files |
|
||||
|
||||
## Accumulated Context
|
||||
|
||||
### Decisions
|
||||
|
||||
Decisions are logged in PROJECT.md Key Decisions table.
|
||||
Recent decisions affecting current work:
|
||||
|
||||
- Phase 1 starts with state ownership fixes before UI consolidation to eliminate poll-driven draft overwrites first.
|
||||
- This milestone stays brownfield and must preserve working lifecycle, model selection, and chat flows while improving runtime workspace trust.
|
||||
- [Phase 01]: Kept legacy snapshot and saveConfig outputs while adding explicit draft APIs so existing runtime drawer consumers keep compiling during the Phase 1 transition.
|
||||
- [Phase 01]: When a runtime draft is dirty, polling updates only operational live fields and leaves baseline plus draft config untouched.
|
||||
- [Phase 02-lifecycle-command-safety]: Expose active and last lifecycle command data on RuntimeSnapshot so frontend polling can render trustworthy lifecycle feedback without inferring from status alone.
|
||||
- [Phase 02-lifecycle-command-safety]: Centralize duplicate start/stop blocking in runtime state helpers so save, start, and stop flows share the same command-result contract.
|
||||
- [Phase 02-lifecycle-command-safety]: Keep restart-required save enforcement limited to connection_mode, model_path, addr, gpu_layers, and ctx_size to stay aligned with the existing backend runtime boundary.
|
||||
- [Phase 02-lifecycle-command-safety]: Mirror backend lifecycle metadata directly into the frontend RuntimeSnapshot so polling and command responses share one contract.
|
||||
- [Phase 02-lifecycle-command-safety]: Derive applyImpact from saved baseline versus draft config using the backend restart-required field list instead of UI-only heuristics.
|
||||
- [Phase 02-lifecycle-command-safety]: Expose activeLifecycleCommand, lastLifecycleResult, and lifecycleBusy from the manager so status-card and drawer copy can consume explicit state in plan 02-03.
|
||||
- [Phase 02-lifecycle-command-safety]: Use explicit lifecycle result banners instead of overloading last_error so completed and blocked actions remain visible after polling refreshes.
|
||||
- [Phase 02-lifecycle-command-safety]: Render apply guidance in the drawer before the CTA row so users see whether a draft applies immediately, needs restart, or must be saved before apply.
|
||||
- [Phase 02-lifecycle-command-safety]: Keep status-card and drawer props backward-compatible with optional lifecycle fields while Sidebar forwards the new manager contract.
|
||||
- [Phase 03-01]: Reuse existing restart-impact field list and lifecycle labels instead of creating parallel heuristics
|
||||
- [Phase 03-01]: Derive diagnostics from backend-owned snapshot fields (status, ready, process_running, resolved_url, config.*, binary_path, last_error)
|
||||
- [Phase 03-03]: One authoritative runtime workspace in sidebar shell - RuntimeWorkspace replaces split StatusCard + Drawer flow
|
||||
|
||||
### Pending Todos
|
||||
|
||||
None yet.
|
||||
|
||||
### Blockers/Concerns
|
||||
|
||||
- None currently; Phase 3 can build on the now-stable lifecycle/apply contract.
|
||||
|
||||
## Session Continuity
|
||||
|
||||
Last session: 2026-03-29T20:49:43.436Z
|
||||
Stopped at: Completed Phase 3 - Unified Runtime Workspace
|
||||
Resume file: None
|
||||
Reference in new issue
Block a user