Merge lane-go: keep the lane's reviewed work
Combines lane-go's typed omni search, launch-time model overrides, TUI artifacts view, run-state websocket push, and the "reflect the change where it belongs" committer rule with the Templates gallery, chat/omni-search and other reviewed work already on main. The 12 files both sides touched keep both intents composed rather than dropping either side: the omni search keeps the typed search contract (CLI `pipelines search` and the TUI popup with type badges and marked snippets) alongside the run-list quick filter; cli.md and ui-ux-review.md document both the search rework and the artifacts view; orchestration.md, harnesses.md and operations.md keep the model-override and reflect-where-it-belongs guidance; and the protocol/CLI/server/TUI code keeps the new search, run-event, override and artifacts paths alongside the existing run, title and help surfaces. Checks before committing: - go build ./... -- pass - go vet ./... -- pass - go test -count=1 ./internal/... ./cmd/... -- all pass Doc check before committing: nothing needs updating. The lane's own docs and references (docs/cli.md, docs/ui-ux-review.md, and the orchestration, harnesses and operations skill references) already carry the new features. format.md and the packaged templates already describe the line-oriented result format and the human decision stage from the earlier lane-go merge. The root README already describes the omni search popup. Model overrides, the search command, run events and the artifacts view are runtime/CLI/TUI surfaces that cli.md documents; no template, README or topic-doc edit is required by this merge.
This commit is contained in:
+59
-11
@@ -48,13 +48,15 @@ Search includes pipeline name, version, status, outcome, stage and diagnostic;
|
||||
`#123` searches run-ID prefixes. Esc while searching clears the filter without
|
||||
closing the list. The filter survives inspection/back and live list refreshes.
|
||||
Home's `/` instead opens the omni popup, which searches pipelines, versions, runs,
|
||||
stages/visits, artifact names, and the text of stage inputs, outputs and evidence.
|
||||
A bare status word (`queued`, `running`, `succeeded`, `failed`, `canceled`,
|
||||
`interrupted`) or a date (`today`, `yesterday`, `this week`, or `YYYY-MM-DD`
|
||||
interpreted in UTC) selects runs, and a leading `pipeline:`/`version:`/`run:`/
|
||||
`step:`/`field:`/`artifact:`/`match:` prefix narrows the result kind. Enter opens
|
||||
the matched pipeline, run, stage visit, artifact or field; unrecognised words
|
||||
remain text.
|
||||
steps/visits, artifact names, and the text of stage inputs, outputs and evidence.
|
||||
Each row carries a short type badge (`pipeline`, `run`, `step`, `artifact` or
|
||||
`match`); a text match also shows a snippet with the matched part bracketed so it
|
||||
is legible without colour. A bare status word (`queued`, `running`, `succeeded`,
|
||||
`failed`, `canceled`, `interrupted`) or a date (`today`, `yesterday`, `this week`,
|
||||
or `YYYY-MM-DD` in local time) selects runs. Enter opens the matched pipeline,
|
||||
run, stage visit, artifact or field. The same query is available non-interactively
|
||||
as `pipelines search QUERY [--type KIND] [--limit N] [--json]`; `--type` is the
|
||||
only kind-narrowing mechanism.
|
||||
Wide terminals
|
||||
show runs and pipelines side by side, with stacked panels on narrow terminals.
|
||||
Home run cards prioritize reported results, status, completed visits and duration;
|
||||
@@ -259,7 +261,7 @@ Submitting activates included schedules, so review them before publishing.
|
||||
| Browse templates/source | `templates --json`, `template KEY --source` |
|
||||
| Create or edit a definition | `new`, `edit`, `drafts` |
|
||||
| Validate and publish | `validate FILE`, `submit FILE` |
|
||||
| Start a run | `run NAME PROMPT [--title TITLE] --yes --json` |
|
||||
| Start a run | `run NAME PROMPT [--title TITLE] [--model P/M] [--stage-model S=P/M] --yes --json` |
|
||||
| Run history/inspection | `runs --json`, `inspect ID --json` |
|
||||
| Rename a run | `title ID "TITLE" --json` |
|
||||
| Decide a waiting human stage | `decide ID [STAGE] --option KEY [--feedback TEXT] --json` |
|
||||
@@ -281,9 +283,10 @@ printf '%s' '{"type":"get_pipeline","pipeline_id":1,"version":1}' | pipelines rp
|
||||
Existing protocol commands: `ping`, `list_pipelines`, `get_pipeline`,
|
||||
`list_templates`, `validate`, `submit`, `run_pipeline`, `list_runs`, `get_run`,
|
||||
`cancel_run`, `retry_run`, `decide_run`, `set_run_title`, `get_run_evidence`,
|
||||
`get_status`, `search`. `search` takes `query` and an
|
||||
optional `kind` and `limit` and returns ranked typed `matches`, each with a stable
|
||||
`target` the client can open. `list_runs` also returns all-history `usage`
|
||||
`get_status`, `search`. `search` takes a `search` request object (`query`, with an
|
||||
optional `kind` and `limit`) and returns a `search_results` response whose ranked
|
||||
`results` each carry a stable `target` the client can open plus the typed payload
|
||||
and matched field. `list_runs` also returns all-history `usage`
|
||||
aggregates. See `internal/protocol/message.go` for JSON envelopes. Mutating RPCs
|
||||
have real effects; they are not previews. TUI-only animation, scrolling, and
|
||||
transient client logs are presentation, not separate server capabilities.
|
||||
@@ -302,6 +305,41 @@ pipeline are distinguishable. Rename after the fact with `pipelines title
|
||||
<run-id> "<title>"`; the run's input, steps and execution are unchanged. The
|
||||
stored prompt is unchanged, and listing/renaming never calls a model.
|
||||
|
||||
### Model overrides at launch
|
||||
|
||||
A pipeline version pins one model per stage. Without republishing, a run can
|
||||
choose different models at launch:
|
||||
|
||||
```sh
|
||||
pipelines run "bug fix" "Fix the layout" --json --yes \
|
||||
--model openai/gpt-5 \
|
||||
--stage-model review=openai/o4-mini
|
||||
```
|
||||
|
||||
- `--model PROVIDER/MODEL` overrides the model for **every** model stage of that
|
||||
run.
|
||||
- `--stage-model STAGE=PROVIDER/MODEL` overrides **one** stage and is repeatable,
|
||||
so any number of stages can be overridden. A repeated key for the same stage is
|
||||
last-wins.
|
||||
- Precedence: a per-stage override beats the whole-run override, which beats the
|
||||
model pinned in the pipeline version.
|
||||
|
||||
Overrides apply to that run only. The pipeline definition and its immutable
|
||||
version are never modified, `show <name> --version N` still returns the pinned
|
||||
source and graph, and the run records the `model` and `stage_models` it was
|
||||
launched with so it stays reproducible; `retry` reuses them. At launch every
|
||||
value must be a `provider/model` pair of the configured form and every stage key
|
||||
must exist in the pinned version — an unknown key fails naming the valid keys and
|
||||
no run is created. A per-stage key that names a non-model stage is refused
|
||||
because that stage never runs a model; `--model` on a pipeline with no model stage
|
||||
is accepted and inert. The effective model reaches the stage and its
|
||||
repair/formatter path from the same resolved definition, and each step's evidence
|
||||
records the provider/model it actually ran with (`inspect <id> --json` exposes
|
||||
per-step `provider`/`model`, and the run's graph shows the effective pair). The
|
||||
CLI is the deliverable; a TUI picker for choosing overrides is a documented
|
||||
follow-up, not half-built.
|
||||
|
||||
|
||||
On either the runs list or run inspector, press `P` (or use `:pipeline`) to open
|
||||
the selected run's exact pipeline version. Navigation does not cancel the run.
|
||||
|
||||
@@ -350,6 +388,16 @@ or Tab to return to details. When not focused, the graph follows the latest visi
|
||||
or selected stage. Existing polling refreshes the graph once per second, and
|
||||
running durations show elapsed time rather than “in progress.”
|
||||
|
||||
The server can also push run changes. A client sends `subscribe` scoped to a
|
||||
workspace (and optionally to explicit run ids); the server first returns the
|
||||
current state of the matching runs, then a compact `run_event` delta on each
|
||||
transition — which run changed, its status, outcome, current stage, completed-step
|
||||
count and timestamps, and, when a single step changed, that step's sequence, stage,
|
||||
status, outcome, target and diagnostic. It is a delta, never the whole run, and
|
||||
rapid changes are coalesced to at most a few frames per second per run.
|
||||
`unsubscribe` or disconnecting stops the frames. This lets a client drop the
|
||||
once-per-second poll; the TUI and Android app still poll in this release.
|
||||
|
||||
In the run inspector, `n`/`p` select the next/previous recorded execution visit,
|
||||
including repeated visits in loops, from any pane. Selection stops at the last
|
||||
visit or overview; it does not wrap. The selected stage has a full-row highlight;
|
||||
|
||||
Reference in New Issue
Block a user