What Studio needs
An open questions view across several projects at once, so a practitioner can see what is blocking anywhere without opening each project.
Where it should live
Probably not here. bin/open-questions.sh --json already emits everything needed per project. The toolkit has no project list: there is no registry anywhere in bin/, project-bin/, claude-hooks/ or tests/, and the "six wired projects" and "8 crash-net projects" figures in bin/sync-project.sh are hand counts in comments. Studio does have a list, in ~/.mxstudio/config.json.
So the honest options are:
- Studio loops projects itself and calls
open-questions.sh <dir> --json per project. No toolkit PR at all.
- A new
bin/open-questions-rollup.sh that takes projects as arguments or reads a plain list file owned by the toolkit.
Option 1 looks right, and matches the existing decision that Studio reads the toolkit's JSON rather than re-deriving it.
Blast radius
New script only. Rating: safe additive.
Hard constraint either way: do not add a multi project mode to open-questions.sh itself. Its --json keys and its 0/1/2/3 exit codes are read by bin/gate-check.sh and pinned by tests/wave2/test-open-questions.sh. A second positional argument is parsed as a stage today, and aggregated exit codes would collide with the contract the stage gates depend on.
A per project exit 2 should count as "skipped", not fatal.
Decision needed
Toolkit script or Studio view.
What Studio needs
An open questions view across several projects at once, so a practitioner can see what is blocking anywhere without opening each project.
Where it should live
Probably not here.
bin/open-questions.sh --jsonalready emits everything needed per project. The toolkit has no project list: there is no registry anywhere inbin/,project-bin/,claude-hooks/ortests/, and the "six wired projects" and "8 crash-net projects" figures inbin/sync-project.share hand counts in comments. Studio does have a list, in~/.mxstudio/config.json.So the honest options are:
open-questions.sh <dir> --jsonper project. No toolkit PR at all.bin/open-questions-rollup.shthat takes projects as arguments or reads a plain list file owned by the toolkit.Option 1 looks right, and matches the existing decision that Studio reads the toolkit's JSON rather than re-deriving it.
Blast radius
New script only. Rating: safe additive.
Hard constraint either way: do not add a multi project mode to
open-questions.shitself. Its--jsonkeys and its 0/1/2/3 exit codes are read bybin/gate-check.shand pinned bytests/wave2/test-open-questions.sh. A second positional argument is parsed as a stage today, and aggregated exit codes would collide with the contract the stage gates depend on.A per project exit 2 should count as "skipped", not fatal.
Decision needed
Toolkit script or Studio view.