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 c34b85d
Browse filesBrowse the repository at this point in the historyBrowse files
✨ Expose the repository vocabulary to an ordinary xmd run (#643)
The provider exists; this is what reaches it. The Deno source entrypoint and the
compiled binary install it for `xmd run` and for an approved `xmd plan --run`,
parameterized by the same credential-helper assembly the workflow host uses and
by the two existing host configurations, both read and validated before a
document expands rather than in the middle of one.
Node and Bun register the same thirteen declarations and install no operational
provider, so `xmd syntax` describes one language everywhere and every repository
operation on those runtimes reaches a clear provider-absence error before a
lock, a credential, a subprocess or a request exists. That is the whole
implementation of the portable half: one array, declared once, with three
consumers — the workflow attachment, `xmd syntax` and `xmd plan`, and an
ordinary document execution.
`run-repositories.ts` names the managed root and the unsupported installer and
is on the shared command path; `deno-repositories.ts` assembles the live
provider and is imported only by the two Deno entrypoints. The split is load
bearing rather than tidy: the adapter's module graph reaches `node:sqlite`,
which Bun has no built-in for, so a static import from shared code would stop
`xmd` loading on Bun entirely instead of refusing one operation.
A nested `<Execution host="run">` child installs no provider here. Giving a
child a live one is inseparable from placing it in the document's contextual
repository — a child that had authority but discovered the process directory
would operate on a checkout nobody named — so both land together, later,
as one change. At this level `xmd test`, a nested child and a workflow execution
all reach provider absence.
The public specifications describe the ordinary profile, the compiled smoke
proves the provider and its kernel-released lock survive `deno compile`, and CI
carries the smoke as its own step.
0 commit comments