Commit 7854e40
committed
docs(tools): record why the Babysit GitHub tools are registry-only
The same branch added four user-facing GitHub tools through the full
block-exposure recipe (v2 variant, tools.access, dropdown, subBlocks) and
five internal ones through none of it. The distinction is deliberate — the
five are called by the Pi Babysit handler via executeTool, which resolves
against the registry rather than any block's access list — but nothing in CI
encodes it, and `check-block-registry.ts` silently skips ids it cannot find.
Worth stating because the trap is non-obvious: `GitHubV2Block` builds its
access list by appending `_v2` to every entry, so adding one of these to
`tools.access` without first adding a v2 variant would point the block at an
id that does not exist.1 parent 234693e commit 7854e40
1 file changed
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6286 | 6286 | | |
6287 | 6287 | | |
6288 | 6288 | | |
| 6289 | + | |
| 6290 | + | |
| 6291 | + | |
| 6292 | + | |
| 6293 | + | |
| 6294 | + | |
| 6295 | + | |
| 6296 | + | |
6289 | 6297 | | |
6290 | 6298 | | |
6291 | 6299 | | |
| |||
6299 | 6307 | | |
6300 | 6308 | | |
6301 | 6309 | | |
| 6310 | + | |
6302 | 6311 | | |
6303 | 6312 | | |
6304 | 6313 | | |
| |||
0 commit comments