Merge branch 'main' into background-tasks-viewer

This commit is contained in:
2026-10-18 23:45:42 +01:00
20 changed files with 616 additions and 70 deletions
+15
View File
@@ -16,6 +16,21 @@ service manager directly. Legacy Python-managed installations require an explici
For source development, use `go run ./cmd/pipelines help`; start the native server
separately. Set `PIPELINES_URL` or pass `--url` to select another server.
## Local resource pools
`pipelines resource-pool-inspect NAME --json` reads a declared pool's members,
enabled/quarantined status and non-secret metadata. It does not report lease tokens.
`pipelines resource-pool-configure pool.json --yes --json` replaces the full pool
declaration; use `-` instead of a file to read stdin. Input is limited to 256 KiB.
Without `--yes`, interactive confirmation is required. Both commands require the
loopback operator transport; ordinary remote/stage clients are refused.
Declarations contain `name` and `members`, each with `member`, `enabled`, optional
`quarantined` and bounded string `metadata`. Existing validation limits the member
count to 32 and metadata to 16 fields per member. Configuration does not release
active owners, discard waiters or prove a device is ready; inspect ownership and
verify readiness before activating a target. Never put credentials in metadata.
## Dashboard and status
`pipelines --url ws://HOST:PORT/connect ping --json` returns `pong` with the
+10
View File
@@ -0,0 +1,10 @@
# Needs you: Clear all
The Needs you bottom sheet now exposes **Clear all** when it has entries. It
dismisses only the entries present when the sheet opened through the existing
individual dismissal path; entries arriving while it is open remain visible.
The action is absent from the empty state. UI verification remains the next
stage's responsibility.
The packaged author skill/reference documentation should be folded to mention
this user-facing behavior rather than being edited in this item.
@@ -0,0 +1,7 @@
# Resource-pool operator configuration — 2026-10-18
`resource-pool-configure <pool.json|-> --yes` replaces one bounded pool declaration
through the loopback-only operator transport. `resource-pool-inspect <pool>` reads
the declared members, enabled/quarantine status, and non-secret metadata. Existing
owners and waiters remain under the store's normal ownership, quarantine, and FIFO
rules; configuration does not release active leases.
+4 -2
View File
@@ -2,8 +2,10 @@
Stage `resources` declarations now accept exactly one of `exclusive` or `pool`.
Pool stages wait on the named pool, then receive the selected concrete member and
bounded metadata through explicit runtime context. The model input remains
unchanged and capability tokens remain private to the store. Retained control
bounded metadata through explicit runtime context. Model execution serializes that
server-granted context as a separate `resource_target` runtime field for both
native and plain harnesses; the task input map remains unchanged and cannot select
the target. Capability tokens remain private to the store. Retained control
evidence records the concrete target; queued run state names the pool while an
active owner names the selected member.
@@ -0,0 +1,7 @@
# Committed and merged stage diffs remain retained
The server captures workspace contents around each stage visit rather than comparing
Git status or HEAD. Regression coverage now exercises a stage that commits its edit,
a later stage that resolves and commits a merge conflict, and an empty commit-only
stage. After reopening SQLite, the first two patches remain available while the final
stage correctly records no source-content change.