Skip to content

docs: keep lock-gate and log-stream instructions current - #36

Open
quantizor wants to merge 4 commits into
mainfrom
docs/lock-gate-instructions
Open

docs: keep lock-gate and log-stream instructions current#36
quantizor wants to merge 4 commits into
mainfrom
docs/lock-gate-instructions

Conversation

@quantizor

@quantizor quantizor commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Follow-up to #34. The start funnel now also owns the resource-hold gate, so the agent map and the CLI contract say that up of a stopped server using a locked resource is refused, and a live one stays up. The unified-log stream command is /usr/bin/log, because zsh's log is a builtin and rejects the predicate. The design spec drops the retired --no-pause spelling. Changelog and design-spec commands now read as directa.

Also a daemon fix: two ensure calls for the same stopped server at the same moment join instead of one failing as a port conflict.

prepareSpawn is now the one start funnel for the resource-hold gate, so the map and the CLI contract say so: up of a stopped server that uses a locked resource is refused, and a live one stays up. zsh's log is a builtin, so the stream command is /usr/bin/log. The design spec drops the retired --no-pause spelling.
The ratified snapshot still described the old CLI, daemon, paths, and bundle id. Commands and identifiers now match the living tree. The notary keychain profile stays `devctl-notary` because that is the stored credential. Historical CHANGELOG links are unchanged.
Commands, GitHub links, the cask, and the daemon binary now read as directa so a copied command from an older entry still runs.
A second ensure of the same stopped server could see the first child's bind as an unmanaged listener and fail port-held, because handle is re-entrant at every await. The spawn gate holds the port claim until that start has begun so the other caller joins.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant