You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spec-review.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,10 +169,12 @@ Incremental progress:
169
169
-`Workspace` carries a narrow Git runner interface, with the production implementation isolated in `realGitRunner`. Workspace-owned Git operations route through that boundary, and a focused test verifies runner injection without creating a Git repository.
170
170
-`Workspace` carries a narrow working-tree filesystem interface for live file reads and writes. Materialization uses resolved absolute worktree paths instead of CWD-relative plan paths, with regression coverage for dirty-path materialization while the process CWD is elsewhere.
171
171
-`Workspace` carries a narrow temp-store interface for Git object directories and synthetic index files. Planning and dry-run temp allocations are injectable, isolated under a test-owned directory in regression coverage, and cleaned up after use.
172
+
- Script loading uses an injectable `scriptSource`, so command-line `run` no longer embeds direct script file reads in CLI argument handling.
173
+
-`Workspace` carries a narrow path-resolution interface for process CWD and symlink resolution. Path resolution can be tested with fake symlink targets instead of real filesystem links.
172
174
173
-
Remaining implementation gap: path resolution and script reading still use process OS APIs directly. The production Git runner shells out to Git, and most tests use real temporary Git repositories. This means:
175
+
Remaining implementation gap: the production Git runner shells out to Git, and most tests use real temporary Git repositories. This means:
174
176
- Tests cannot model scenarios without touching the filesystem.
175
-
- The architecture diagram's separation between planner, snapshot store, and git backend is not reflected in the code.
177
+
- The architecture diagram's separation between planner, snapshot store, and git backend is only partially reflected in the code.
0 commit comments