review · segments

Solo Routines Recon Research Lane

pi 172 events 1 segments

segment 1 of 1

Map Solo's undocumented routines JS automation system

Done

Read spec, locked todo, explored CLI, binary strings, DB schema, created test routine, bundled and checked, extracted type definitions, discovered feature flags, wrote findings to scratchpad 771 and commented on todo 404.

outcome

Findings scratchpad 771 created with on-disk layout, run path, permissions, and blockers; todo 404 marked ready for review.

next steps

—

key decisions

Routines use routine.ts or src/routine.ts, not index.js
Bundle artifacts are dist/routine.js, .map, .bundle.json
Import from @solo/routine using defineRoutine
Permissions declared on defineRoutine, not inside run()
linkedCheckouts.create does not create git worktree; two-step flow required
Feature gated by get_routines_enabled; no public setter found
Trust review required before first run via UI
No CLI or MCP run tool in v0.8.2; only Tauri commands

open questions

Exact path for 'shared routine lib' not fully extracted
How to enable routines feature flag programmatically (no set_routines_enabled found)
Why --scope shipped returned zero routines on this install

3 weeks ago → 3 weeks ago