* feat(onboarding): the first task chat delivers a small result in minutes
Live runs on an RTX Spark showed the task chat surveying the whole machine,
asking a plan question, and installing the picked plugins 11.5 minutes after
setup. Its suggestions ignored the picks and the scan, and the handoff text
said "Call me Sid." and "Start from this; look at my computer again...".
- New optional skill first-task. start_chat appends it to the task chat's
first message, after the ask and the "What setup learned" block, with a
JSON block of the connector and plugin ids picked in setup. No system prompt
changes. The history projection cuts the message at its marker, so no
surface shows the skill. Its rules: connect and install the picks first,
work visible in 1 minute and a finished result in 5, big asks cut to a
first slice, three options only for a vague ask, machine setup as a short
card interview.
- setup_choose records the picked ids and the fork pick. The fork card is
filled when shown: two first tasks from the picks and the scan (a daily
brief from the picked apps, "Install a few apps for this Spark", a small
page), then "I have something in mind", "Help me set up this <machine>",
"Let's figure it out together". The machine-first "Something else" step,
"automate" and "skip" rows are gone; "figure" hands off at once.
- The handoff template is the ask only; no "Call me", no install or plan
paragraphs. start_chat drops the "Start from this" line.
- initiate-setup SKILL.md keeps only the setup beats (20.5 KB -> 10 KB).
- Desktop shows the "What setup learned" block folded under the first
message; the model still gets the full text.
* fix(setup): one unexpected shutdown reads as singular
ff4760bfbd