Live evidence that a lease says who - #413
Merged
Merged
Conversation
A real chain run held a scratch workspace while `lease` and `lease release` were asked about it, and again after it ended. Records 5.4 of a-lease-says-who: the lease file the run itself wrote, both outputs, and the exit codes — 0 answering who holds it, 1 refusing to clear a live holder, 0 once nothing held it. The unit tests drive the reader with written files. This is the first run to show that the identity a chain records is the identity the command reports, and the same conflict message a second run is refused with. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task 5.4 of
a-lease-says-who, the one item that could not be closedfrom a written file: only a real run shows that the identity a chain
records is the identity the command reports.
A chain run of a throwaway change in a scratch workspace whose
user.emailis set, driven byopenspec-ui-cli runbuilt from thischange:
apply->verify->archive, exit 0.While it held the workspace:
.openspec-ui/workspace.lease.jsonwas written by the run itself andcarries
"hostKind": "cli", its pid, and the git identity.leasenamed that identity and exited 0;--format jsonreturned thereader's own shape and exited 0.
lease releaserefused it and exited 1, naming stopping the processas the remedy; the lease file was still there afterwards.
openspec-ui-cli runwas refused with exit 2 and a message naming thesame git author.
After the run ended: the lease file was gone,
leaseprinted "Nothingholds this workspace." (exit 0) and
lease releaseprinted "Nothingheld this workspace." (exit 0, the
already-freeoutcome).Documentation only — the lease file, both outputs and the exit codes are
recorded in
tasks.md. No source changes, so no changeset.openspec validate --strict --changes: 1 passed, 0 failed.🤖 Generated with Claude Code