526c19fc21
- Persist chat stars in the operator-session registry (chat_star) so every browser/device shows the same Starred group; migrate old local stars once. - Add a compact pipeline graph shape to list responses and draw a lightweight list miniature; replace the cryptic id/version line with the stage count. - Surface OpenCode form questions as a chat card (chat_answer), replay a pending form to late subscribers, and notify for background questions. - Make the mobile dock's Search cell equal to every destination, keep the tab row visible with 100svh, and let Source use the full pane height. - Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie with Expires so Remember me survives app/link launches. - Keep shipped starters and the skill agnostic: no repository paths, project areas or personal device commands; add Diagnose/Fix and Research starters. - Refresh the installed skill and document the new browser conventions.
2.2 KiB
2.2 KiB
stage planner
Plan the task in input.md without implementing it. Inspect the repository and
reuse what already exists. State the approach, the files likely to change, and
the checks that will prove the change works. Research external facts only when
the task needs them, and cite what you use. Do not edit.
read
glob
grep
websearch
webfetch
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> implementer
blocked -> #failure
error -> #failure
stage implementer
Implement the plan from input.md. Follow the repository's conventions, keep the
change focused, and add or update tests where they matter. Preserve unrelated
work. Run the relevant checks and report the exact commands and actual results,
including what you could not test. Do not commit, push or deploy.
read
glob
grep
edit
shell
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> reviewer
blocked -> #failure
error -> #failure
stage reviewer
Independently review the actual change against the task and plan. Inspect the
diff and related code, and run the relevant checks yourself rather than trusting
an earlier summary. Look for correctness, duplication, unnecessary complexity and
missing tests. Report each blocking finding with a location, evidence and remedy;
keep advisory notes separate. Return success only when the applicable checks pass
and no substantive issue remains. Do not edit or commit.
read
glob
grep
shell
websearch
webfetch
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> committer
rejected -> #failure
error -> #failure
stage committer
Commit this run's change locally. Inspect `git status` and the full diff; stage
only this run's work, never secrets or generated files. Run the relevant checks
and report the actual results. If nothing changed, say so rather than creating an
empty commit. Do not push, tag, deploy or rewrite history.
read
glob
grep
shell
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> #success
blocked -> #failure
error -> #failure