web: shared chat stars, pipeline mini graphs and agent questions
- 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.
This commit is contained in:
+8
-43
@@ -1,33 +1,10 @@
|
||||
# stage worker
|
||||
|
||||
```prompt
|
||||
Complete the task in input.md in the run directory. Inspect only relevant context and
|
||||
follow the user's scope and constraints. Limit repository inspection and
|
||||
verification to relevant repository paths; never scan filesystem or mount roots,
|
||||
and use commands supported by the actual execution environment rather than
|
||||
guessed platform flags. This is a working instruction, not an OS sandbox. Work
|
||||
with the repository's actual languages and file types; do not assume a framework
|
||||
or technology. Prefer repository conventions, supported standard libraries and
|
||||
existing dependencies/APIs/helpers over bespoke or copy-pasted code, and avoid
|
||||
unnecessary new dependencies rather than treating useful supported standard
|
||||
libraries as off-limits; justify any genuinely needed custom implementation,
|
||||
compatibility exception or dependency choice with its tradeoffs and do not force
|
||||
coincidental lookalikes into a shared abstraction. Research official primary
|
||||
sources with websearch/webfetch only when the task genuinely needs external
|
||||
knowledge, recording source URLs and applicability/version evidence or stating why
|
||||
none was needed; keep queries free of private code and secrets. Return blocked only
|
||||
when required reliable evidence cannot be obtained; a single failed, blocked or
|
||||
anti-bot search may be replaced by a successful official-source webfetch that
|
||||
fully supplies the required evidence, otherwise return blocked. Fix causes rather
|
||||
than suppressing errors or weakening checks, and avoid speculative abstractions.
|
||||
Preserve unrelated work and leave the commit to the committer stage: do not commit,
|
||||
push, deploy, or perform destructive actions. Save any artifacts you produce
|
||||
(reports, logs, screenshots) into the artifacts directory named in the runtime
|
||||
context; they are attached to this stage. Verify the change with the repository's
|
||||
relevant checks and report the exact commands and observed results in an
|
||||
`# evidence` section; never claim an unexecuted check passed. Return the complete output.md markdown; the only required section is `# outcome` followed by a declared edge word, with free-form headings for the facts later stages need. Return blocked
|
||||
if the task or required tools are unavailable; otherwise return success with
|
||||
actual results.
|
||||
Complete the task in input.md. Inspect the repository first and follow its
|
||||
conventions. Keep the change focused, preserve unrelated work, and run the
|
||||
relevant checks. Report what changed, the exact checks you ran, and anything you
|
||||
could not verify. Do not commit, push or deploy.
|
||||
```
|
||||
|
||||
```tools
|
||||
@@ -56,22 +33,10 @@ error -> #failure
|
||||
# stage committer
|
||||
|
||||
```prompt
|
||||
Commit this run's change locally. Never push, tag, deploy or rewrite history.
|
||||
Inspect `git status` and the full diff, and stage this run's change, including
|
||||
inherited work, restricted to paths that still exist and keeping any exclusions. Inspect the staged diff before
|
||||
committing; never commit unrelated work, secrets or generated artifacts. Follow the
|
||||
documentation-note step of the committer checklist in `references/format.md`: when the
|
||||
change makes a shared document stale, stage the item's own documentation note
|
||||
(`docs/notes/<slug>.md`) with the change, and never edit a shared document (a README,
|
||||
topic docs or the packaged skill references) here; a single documentation writer folds
|
||||
notes later. Pre-commit
|
||||
checklist: confirm the staged paths are this run's change; run the repository's
|
||||
required checks and record the exact commands and observed results in an
|
||||
`# evidence` section; do not commit if a required check fails, return blocked
|
||||
with the failing output instead. If nothing is staged, do not create an empty
|
||||
commit; return success with a clear note. Otherwise commit with a concise message
|
||||
naming this run's change and report the commit hash. Return the complete output.md markdown; the only required section is `# outcome` followed by a declared edge word, with free-form headings for the facts later stages need. Never claim an unexecuted
|
||||
check passed or fabricate a commit.
|
||||
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.
|
||||
```
|
||||
|
||||
```tools
|
||||
|
||||
Reference in New Issue
Block a user