alex
2247ec47c9
Use canonical profile files and writable Git working copies so editor and container changes share one source. Require confirmation before destructive Git refreshes and overlay profile files without composite snapshots.
2.4 KiB
2.4 KiB
Live Config Profile Refresh — Tasks
Review Workload Forecast
| Field | Value |
|---|---|
| Estimated changed lines | 500–750 |
| 400-line budget risk | High |
| Chained PRs recommended | Yes |
| Suggested split | Container-user standardization → canonical profile mounts → API/UI feedback → verification |
| Delivery strategy | feature-branch-chain |
| Chain strategy | feature-branch-chain |
Decision needed before apply: No Chained PRs recommended: Yes Chain strategy: feature-branch-chain 400-line budget risk: High
Execution Plan
- Canonical non-Git mounts: bind declared profile files and mount directories directly from profile-scoped canonical storage; ensure the container user owns writable canonical sources.
- Editor synchronization: materialize editor saves into canonical storage and return canonical declared-file content through profile responses; add explicit Reload working copy controls in desktop and mobile editors.
- Writable Git working copies: expose profile-scoped Git sources as writable mounts and replace them from the configured remote ref on explicit refresh.
- Server refresh contract: require explicit destructive-refresh confirmation at the API boundary and return a typed outcome when confirmation is missing.
- Overlap safety: replace profile/Git composite snapshots with child file-level canonical profile overlays so Git directory mounts remain intact.
- Outcome UI: display destructive-refresh confirmation and explicit Reload working copy controls in both editor layouts; restart-required/overwrite states remain available as API errors/outcomes.
- Focused tests: cover destructive refresh and overlap behavior at service/API/frontend levels; canonical source reuse is covered by resolver tests.
- Verify: targeted backend/frontend tests, typecheck, lint, and diagnostics passed. Docker multi-instance validation remains skipped by user choice.
Verification Notes
- Passed: frontend production build (
npm run build), Python compilation for changed backend modules, and targeted LSP diagnostics. - Skipped: backend pytest and Ruff; this environment has no project-managed Python runner, system Python lacks those packages, and the user declined system-package installation.
- Skipped: Docker/Compose and manual multi-instance checks; explicit Docker approval was not granted.