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 e195703
Browse filesBrowse the repository at this point in the historyBrowse files
`<Dir path>` installed a working directory and created nothing, so a document
that named a directory which was not there ran its content somewhere that did
not exist. It now performs one provider-neutral directory act before it installs
cwd and before any content expands.
`API.Files` gains a mandatory `ensureDirectory`. It recursively creates a
missing target, succeeds for an existing directory without replacing it or
clearing its contents, and refuses a file or another non-directory at the target
or on the way to it. Success carries nothing at all — no path, no handle, and no
word on whether this call is what created it — for the same reason `deleteFile`
carries nothing: a document that asked for a directory to exist has been
answered by its existence, and a caller that could tell the two apart would be
branching on a race.
The host provider creates directly and persistently. There is no rollback and no
teardown removal: a later failure of the content running inside a directory says
nothing about whether the directory should exist. It is also the one operation
here that accepts an absolute path, which is `<Dir>`'s established exception, so
it resolves its own destination rather than inheriting the rule that refuses one.
The workflow provider publishes one `workspace_file` effect. The recursive
creation runs inside its savepoint, so a refusal after a partial creation leaves
neither the parent nor a rolled-back transaction — the effect that follows still
commits. An absolute path there is a logical Workspace path used as written, and
names nothing on the host.
Shared `<Dir>` calls only `API.Files.ensureDirectory`, through core's door that
turns an illegal provider throw into a fenced failure. It reaches no `API.Fs`,
no `@effectionx/fs`, no runtime API and no Repository composition, and it
changes no Repository selection or identity member.
`allow={["write"]}` now authorizes persistent recursive creation, so the pinned
paired identity is versioned to
`@executablemd/workflow/composition/dir-v2#Dir`. A continuation retaining the
former identity — which authorized placement that created nothing — refuses
before generated execution and before any mutation.
The thirteen composition components take their accepted descriptions.
Evidence: HF15b, HF24–HF28, FF2, the compiled contract probe, WF23–WF26,
WGAC17, ORC6–ORC6i, runtime parity under Deno, Node and Bun, and ORC20.
0 commit comments