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 5f6f961
Browse filesBrowse the repository at this point in the historyBrowse files
📝 Separate the shipped suspension substrate from what this Markdown calls
The documents had swung from one error to its opposite. They once said durable
suspension was unbuilt; the last commit corrected that and overshot, saying an
`<Elicit>` under `xmd workflow` *becomes* a durable suspension and that these
checkpoints release the executor. Neither is true, and the two mistakes are the
same mistake: reading shipped substrate as a shipped integration.
What is shipped is `suspendFor()` — a run waits, gives its executor lock back,
and a typed answer can be delivered to it (#367, #300). It is an Api operation.
There is no v1 Markdown element that spells it, a suspension is a different
mechanism from `<Elicit>`, which asks inside the execution already running, and
this workflow installs no component or middleware that turns one into the other.
So no checkpoint here releases the executor, delivery executes nothing, and
nothing schedules a resume. Consuming that substrate is #301's supervised
composition, and the documents now say exactly that without inventing a spelling
or a bridge for it.
Two smaller corrections fall out of the same pass. `<Git.Add>` and
`<Git.Commit>` were still listed among names that resolve to nothing, when they
are two of the six registrations the workflow host supplies alongside
`<Repository>`, `<Worktree>`, `<Dir>` and `<Git.Switch>`. And the forge read
that hands a network-denied reviewer a pull request's reviews, comments and
checks is no longer unowned: `<Fetch>` reads over HTTP and retains what it read
(#456). No stage writes those fetches yet, and admitting `<Fetch>` inside
generated XMD stays #369's.
The component probe now asserts four exact categories rather than a set — 16
ordinary, 5 bundled stages, 5 issue-owned unresolved, 6 workflow-host-only — and
fails if any component the documents write goes unclassified or lands in the
wrong group.
0 commit comments