Merge branch 'main' into small-fullwidth-body

This commit is contained in:
2026-10-19 00:07:03 +01:00
34 changed files with 1373 additions and 165 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
+17
View File
@@ -0,0 +1,17 @@
# Background tasks viewer limits
The chat background-task surface now shows only shell identities verified for the
selected chat session by the current-running snapshot and lifecycle events. It
keeps a bounded in-memory tail of exits observed by this client so a selected task
can settle with an observed exit code; it is not durable task history.
The upstream shell list is RUNNING-only. Tasks which ended before observation are
not enumerated or backfilled. Verified output is read lazily for the selected task
through one bounded 64 KiB page; refresh rereads that page from cursor zero rather
than accumulating client history. A task that exits after observation remains
visible and reports the server's output or an explicit unavailable/empty state.
This changes the chat UI. The packaged OpenCode skill references and chat topic
documentation should describe the running-only, bounded-observation behavior and
the lack of durable history when the manual `docs-fold` pipeline next updates
shared documentation.
+21
View File
@@ -0,0 +1,21 @@
# Local hide notice lifetime
## What this item changed
`android/app/src/main/java/net/awan/pipelines/ui/chat/ChatListPane.kt` now presents a local-hide
notice once with Material's short, finite snackbar duration. The `ChatStore` keeps the one-shot
notice separate from the undoable local override and records delivery separately from snackbar
completion, so leaving and re-entering cannot replay an in-flight notice. A later hide replaces the
pending notice rather than queueing it. Returning to the list,
recomposition and a session refresh therefore cannot replay an already-finished notice; Undo still
restores only the current local hide and does not delete server state or history.
`ChatRemovalNoticeTest` covers finite-notice consumption, rapid hides, Undo and list re-entry using
the pure store, with no real-time wait.
## Shared documents this change makes stale
- `android/README.md`'s chat-session behaviour should say that **Hide on this device** has a
short, finite Undo notice, rapid hides replace rather than queue notices, and an expired or
consumed notice is not replayed when returning to the list. It should name
`ChatRemovalNoticeTest` as unit-test evidence and leave on-device timing to visual review.
+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.
@@ -0,0 +1,6 @@
# Transitive retry memory prefixes
On 2026-10-18, resume checkpoints retain prefix provenance across selected-stage
retries. A retry-of-retry restores the original completed memory prefix from
the immutable checkpoint, then applies the new selected-stage override once;
the source attempt's steps remain evidence and are never copied or rerun.