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
{{ message }}
Repository navigation
Commit 273653d
Browse filesBrowse the repository at this point in the historyBrowse files
📝 Compose the checkout path and the directory it is worked in
The flow bound its worktree with a lexical `<Worktree as="worktree">` and
expected that same invocation to render the stages inside it. Generic `as=` is
an ordinary private capture, and #293 settled that Repository and Worktree get
no exception to it — so that spelling would have captured the whole flow and
left the root's `<Output>` with nothing to emit.
The two existing forms compose instead: a self-closing `<Worktree … as>` creates
or restores the retained checkout and binds its path, and a lexical
`<Dir path={worktree}>` inside the same `<Repository>` makes that path cwd,
renders the stages and the final report, and restores the enclosing cwd. Agent
access is still `<Agent.AddDir>`; cwd never implies it.
`<Dir>` is not built either, so the unresolved inventory is ten names rather
than nine, and #293 owns the boundary this composition consumes.
Reading a run back is no longer future work. `xmd workflow status`, `list` and
`history` report immutable lifecycle snapshots — no lease, no replay, no
Workspace, no append — so the documents say so, and say what history actually
prints: an authored source position rather than a forkability reason it does not
have. Suspension, executor ownership, cancellation and deletion stay #367;
forks and forkability stay #368.
| versioned history checkpoints and compatible forks |#368| open |
317
+
| read-only `status`, `list` and `history` over immutable lifecycle snapshots |#367 slice 1, delivered by #460| shipped |
318
+
| durable suspension, releasing the executor at a checkpoint, single-executor ownership, atomic lifecycle transitions, cancellation, deletion |#367| open |
319
+
| versioned history checkpoints, compatible forks, `history --forkable` and forkability reasons |#368| open |
303
320
304
321
`xmd workflow start` is what makes this document a workflow rather than a script,
305
322
and it exists: `xmd workflow start [--id] [--props-*] <definition>` creates the
@@ -335,7 +352,7 @@ component search path is introduced for workflow execution. The mechanism is
335
352
336
353
| Capability | Issue | Status |
337
354
| --- | --- | --- |
338
-
|`<Repository>` and `<Worktree>` as named Workspace composition, with lexical cwd|#293| open |
355
+
|`<Repository>` and self-closing `<Worktree>` as named Workspace composition, and the lexical `<Dir>` boundary that consumes a bound checkout path|#293| open |
339
356
|`<Git.Switch>`, `<Git.Add>`, staged-only `<Git.Commit>`|#294| open |
340
357
| shared external forge-effect reconciliation |#297| open |
0 commit comments