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 1659e79
Browse filesBrowse the repository at this point in the historyBrowse files
🎫 Bind with <Let>, and file a deferred finding where it belongs
Four merged capabilities change what this target may say, and two of them change
what it writes.
`<Capture>` left the reserved set with no alias (#528), so every structural
invocation here is `<Let>` — nine of them across five documents, plus the prose
that named the removed directive. The pull-request loop's seed stops being
JavaScript: `<Let as="pullRequest" value={{}} />` binds the empty object
directly, which is the shipped form for exactly this. It does not close#301's
gap and the documents say so — `<Let value>` binds a value, and does not make an
ordinary component prop whose expression evaluates to `undefined` become
omitted, so the seeded `number={pullRequest.number}` still waits on the omission
nothing has built.
The deferred-issue markup was invalid against the shipped contract (#516). It
passed `pullRequest` and `finding` props that do not exist on a component whose
schema is closed. It now writes what #516 actually offers: an
`<IssueTracker url={props.tracker}>` naming the container, a paired
`<Issue title={finding.title} as="deferredIssue">` whose body is the
description, and a result read as exactly `{ url }`. The body carries what a
reader needs to know why the finding was deferred — the finding, its evidence,
the pull request it came from, and the review and checkpoint that classified it.
`tracker` is a new required root prop threaded to the stage; it selects a target
and grants nothing, because the ceiling lives beside the host's credentials.
That moves `<Issue>` out of the unresolved inventory and leaves one name in it.
`<Expand>` is the only component here that resolves to nothing, and the stage
still cannot reach the forge — which is unreachable, not unbuilt.
Authentication and crash inspection are recorded where the documents already
discuss the effects they belong to. Credentials are live host input acquired per
invocation and are not a prop, a retained value, a journal field or anything an
Agent sees (#532). A crashed run is inspected from a private recovered copy,
leaving the authoritative source byte-identical (#521).
| shared Git-host reconciliation behind push, pull request and issue |#297| shipped — the surface, and now the push and pull-request components over it |
637
666
| the forge read that returns reviews, comments and checks |`<Fetch>` (#456) | shipped — this stage does not write it yet |
638
667
639
-
The agent, parsing, capture, and control-flow syntax runs today, and so do the
640
-
Git effects: `<Git.Add>`, `<Git.Commit>`, `<Git.Push>` and `<PullRequest>` are
641
-
all built and registered by the workflow host.
668
+
The agent, parsing, binding, and control-flow syntax runs today, and so do the
0 commit comments