Repository navigation
Release 0.6.2: seat hooks, narrower room replies, and an overseer lead - #87
Merged
Merged
Conversation
foil send user reaches the human. A room reply wakes the thread and named seats. The lead checks a method that arrives with the goal. Co-authored-by: Cursor Agent <cursoragent@cursor.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.
Patch release. No command was added or removed, and the registry schema stays 1.
foil --versionprints 0.6.2. The changelog section that was Unreleased is now [0.6.2], dated 2026-10-23. Version pins in the package, lock, demos, and tests match.Since 0.6.1: seat git hooks,
foil send user, a narrower wake forfoil post --re, rotation stored on the registry, the lead as an overseer, and operator check-ins that stop on their own and clear only a validated folder-trust prompt.Review
One independent review of
v0.6.1..mainfound nothing worth fixing. Privacy and publish safety of the tree passed. It does not remove a command, refuse a flag 0.6.1 accepted, or bump the registry schema, so this stays a patch rather than 0.7.0.Verification
Against this commit, Python 3.12:
tests/test_version.pypassed,uv lock --checkmatched,ruff check .was clean. CI onmainat8308c08already passed the behavior. CI on this pull request covers the version pins.