Skip to content

0.10.0's release notes were missing a public API addition that ships in it #198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rohanrkamath merged 2 commits into from
Sep 14, 2026
Merged

0.10.0's release notes were missing a public API addition that ships in it #198

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
313001a
0.10.0's release notes were missing a public API addition that ships …
arpanghoshal Sep 14, 2026
8aa08c4
Merge remote-tracking branch 'origin/main' into release/0.10.0-changelog
arpanghoshal Sep 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,14 @@ One question: when one agent hands work to another, what does the second one hol
- `ctrlrun inspect --hop` emits `ctrlrun.hop/v1`: who issued a hop, and **which dimensions each
link narrowed**, which is the question an operator paged at 3am actually has.
- `ctrlrun scan` names the principals holding a grant no hop bounds. It reports and does not score.
- **`task=` and `hop=` on `ctrlrun.adapter.needs_approval`**, the pre-invocation predicate a
framework asks before it invokes a tool. Without them the predicate evaluated against the
receiver's whole candidate set while `execute` evaluates against the hop **alone**, so it answered
"a human is needed" for a call `execute` then refuses: the framework surfaced an approval item, a
human said yes, and the call failed anyway. Never a wider grant, because `Control.execute` is the
enforcement point and refuses either way; what it cost was the framework's own approval item and a
receipt nobody could explain. `SPEC-v0.10.md` §9 froze the name and §9.4 records that it shipped
after this section was first written, which is why it is here and not above.

### Changed

Expand Down