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 b1c33b3
Browse filesBrowse the repository at this point in the historyBrowse files
🔐 Refuse a rejected credential, and tear a lease down in order
Continues e81561c. A6's correction, the ordering correction, and the evidence
for exclusivity, teardown, infrastructure failure, Windows and host assembly.
**`erase` is a signal, not an erasure.** Git sends it when a transport refused
what the helper gave, and it is the only way this run can tell "the host proved
nothing" from "the host proved something the remote would not accept". It is
never forwarded, reaches no helper or keychain, and produces no output — it
tells the broker, the broker tells its parent, and the refusal vocabulary reads
it. Both cases are `authentication-unavailable`; neither is an invalid locator.
A rejection belongs to the lease it happened on: the next invocation's lease
knows nothing about it, and an erase about another repository is ignored.
**Teardown order is observed, not assumed.** Invalidate the lease, terminate the
group, close the IPC, await every child, then remove the endpoint and the
launcher. Each step announces itself and a test asserts the sequence, because
these same steps in another order would leave a live broker addressable by a
path nobody owns.
**Exclusivity is per lease.** One caller answered at a time — three at once
cannot all be this invocation — while a reconciliation's sequential commands are
all answered.
**Infrastructure failure is a host condition.** A broker mode that is not there
produces no lease, no credential and no completion, and still removes what it
made. A socket spoken to badly is answered with nothing.
**Windows is proved on this host**, because the platform is a parameter: a
random invocation-local pipe name, different per lease, with no all-user access
option — and the capability still validated before any credential byte, which is
what makes the name enough.
**Both entrypoints assemble the same two modes**: from source the executable is
Deno and the module is named to it; compiled, the executable is the host and
carries its own.
Architecture and §13.1 now describe the broker child rather than the
environment-bearing lease that preceded it.
Refs #522
0 commit comments