What's missing
The README "Driving one full gardener → breeze cycle end-to-end" prompt (landed in #326/#327) promises a cold-start user:
...trigger one drift event end-to-end so I can watch: source PR → tree issue → breeze pickup → draft-node PR.
first-tree tree help onboarding now bootstraps the flow correctly (the #326 chicken-and-egg is fixed by #327), but the narrative it prints does not script the final leg. Step 6 delegates to "see the breeze skill" (only reachable post-install) and "Sample Tasks" covers gardener sync / gardener comment individually but never stitches together the source-PR → breeze-dispatch → draft-PR demo.
Cold-start E2E finding
Running npx -p first-tree first-tree tree help onboarding in a fresh scratch dir on PR #327's branch produced 301 lines of narrative that covered Steps 1–5 cleanly, then:
- Step 6 punts to
.agents/skills/breeze/... (exists after tree init, but no inline commands)
- No "Step 8 / End-to-End Drift Demo" section
- A cold agent has to improvise: guess the breeze install command, guess how to trigger a drift event, guess what "breeze pickup" looks like in logs
Proposal
Add a "Step 8: End-to-End Drift Demo" section to the onboarding narrative that scripts:
first-tree breeze install --allow-repo <source>,<tree> with the gh api /repos/<source>/subscription watch-status checkfirst-tree breeze start (or whatever the daemon-start surface is) with a note about what success looks like- How to trigger a drift event (make a source-repo change + PR, or run
gardener sync manually) and what to expect in the tree repo's issues + breeze logs
- How to confirm the draft-node PR appeared and close the loop
Why this is worth doing
The end-to-end drift demo is the only part of the onboarding prompt that demonstrates the value of first-tree (as opposed to just setting up plumbing). A cold user who can't see the chain fire has no evidence the tool is doing anything.
Context
What's missing
The README "Driving one full gardener → breeze cycle end-to-end" prompt (landed in #326/#327) promises a cold-start user:
first-tree tree help onboardingnow bootstraps the flow correctly (the #326 chicken-and-egg is fixed by #327), but the narrative it prints does not script the final leg. Step 6 delegates to "see the breeze skill" (only reachable post-install) and "Sample Tasks" coversgardener sync/gardener commentindividually but never stitches together the source-PR → breeze-dispatch → draft-PR demo.Cold-start E2E finding
Running
npx -p first-tree first-tree tree help onboardingin a fresh scratch dir on PR #327's branch produced 301 lines of narrative that covered Steps 1–5 cleanly, then:.agents/skills/breeze/...(exists aftertree init, but no inline commands)Proposal
Add a "Step 8: End-to-End Drift Demo" section to the onboarding narrative that scripts:
first-tree breeze install --allow-repo <source>,<tree>with thegh api /repos/<source>/subscriptionwatch-status checkfirst-tree breeze start(or whatever the daemon-start surface is) with a note about what success looks likegardener syncmanually) and what to expect in the tree repo's issues + breeze logsWhy this is worth doing
The end-to-end drift demo is the only part of the onboarding prompt that demonstrates the value of first-tree (as opposed to just setting up plumbing). A cold user who can't see the chain fire has no evidence the tool is doing anything.
Context