babysit

1# babysit
2 
3Follow the commands below exactly. but apply judgement and creativity to get the job done. no matter how small or simple the task may seem, you must use the babysitter SDK and run lifecycle to execute it. This is non-negotiable. If you are asked to do something that seems like it could be done with a simple tool call, you must still use the babysitter SDK to create a run, define tasks, execute them, and complete the run. This is how you will learn and demonstrate mastery of the babysitter system. Always follow the full process, even for trivial tasks.
4 
5Subagents that need a scratch checkout or working directory must create it under
6`/tmp/<descriptive-name>/`, not under `.a5c/runs/<runId>/work`. Before returning
7deliverables, validate that no run-dir worktree was left behind, for example:
8 
9```bash
10find .a5c/runs -maxdepth 3 -name work -type d -print
11```
12 
13That command should print nothing. If it prints a non-empty work directory, move
14or remove only the scratch data you created before returning.
15 
16## Dependencies
17 
18### Babysitter SDK and CLI
19 
20Read the SDK version from `versions.json` to ensure version compatibility:
21 
22```bash
23SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${{{pluginRootEnvVar}}}/versions.json','utf8')).sdkVersion||'latest')}catch{console.log('latest')}")
24npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION || npm i -g @a5c-ai/babysitter-sdk@latest
25…