Release 0.92.1: clearer delivery recovery and workspace maintenance

amplifier_web/__init__.py

@@ -1,2 +1,2 @@
 """Amplifier's local web host."""
-__version__ = "0.92.0"
+__version__ = "0.92.1"

amplifier_web/release-notes.json

@@ -1,6 +1,7 @@
 {
   "schemaVersion": 1,
   "releases": [
+    {"version":"0.92.1","title":"Clearer delivery recovery and workspace maintenance","changes":["Close an inactive failed or uncertain local delivery item without resending it or discarding its original input, text or attachment references. Find closed items in Chat info or the pre-chat screen to inspect or reopen them without sending. Closure survives reload and reconnect; a late passive check cannot reopen the item, and exact positive acceptance still retires it. Active sends cannot be closed, and existing collapsed warnings are not automatically converted.","Make passive delivery checks avoid redundant command-journal writes, full history refresh and copying unrelated execution history. A check still does not send or retry work; newly confirmed acceptance reconciles the original receipt, while dormant chats retain their existing admission and recovery checks.","Consolidate the internal rules for adding, renaming, archiving, restoring and removing workspace registrations with the existing discovery metadata owner. Existing workspace names, custom metadata and registration IDs are preserved; adding an already registered folder changes its name only when an explicit name is supplied.","Keep folder validation and creation, workspace selection, pins, Canvas effects and saved native conversation history with their existing host owners. This is internal maintenance, not a new workspace registry, identity migration or permission change. No migration or setting change is required."],"notices":[]},
     {"version":"0.92.0","title":"Read earlier public messages in shared agent rooms","changes":["Let supported external agents in a shared room request earlier committed public messages and continue the text of long messages when needed. Reads use the existing saved-message owner, with source attribution, bounded pages and explicit omissions; private agent context, tools, interrupted partial replies and unsent drafts stay separate.","Offer room-context tools through an optional standard HTTP MCP attachment when the agent advertises that capability and Unified has a primary configured HTTPS public address. That address must be reachable and trusted from the agent's runtime; configuration alone does not establish remote connectivity or TLS trust. Missing capability or HTTPS configuration leaves ordinary chat usable.","Scope each transport credential to the current room, participant and saved source binding. Membership and source changes are checked before reading and again before returning an asynchronous result. This grants no other room, private history or host-control access. Revocation prevents future reads but cannot erase content an agent already received.","Preserve the saved agent session identity when attaching context tools on creation or resume. An advertised attachment failure remains an explicit connection failure rather than silently removing the tools, creating a replacement session or replaying work. Existing singleton and directed chats and Stop's execution behavior remain unchanged."],"notices":[]},
     {"version":"0.91.0","title":"Shared agent rooms and simpler conversation delivery","changes":["Add several external agents to a new shared chat. Send one message to the room; agents can respond to you and one another without choosing a recipient. Agents can work concurrently while you keep posting. Participation may use model calls even when an agent chooses not to reply; Stop interrupts the room's current exchange.","Existing native chats, single-agent chats and saved directed groups keep their existing chat modes. Shared-room participation is a distinct new-room choice, not an automatic conversion of saved conversations.","Ordinary native Send addresses the conversation rather than the browser's last observed run. The native owner can guide an eligible active response, deliver at its next request boundary, or start a new turn after normal completion. Explicit run-anchored steering stays strict and does not become new work.","Keep a pending message's captured conversation source, text, attachments, quotes and settings checks through waits and navigation. Switching chats does not redirect it. Stop still fences submissions prepared before it; uncertain submissions retain their original identity, and Check delivery observes the saved receipt without resending.","Improve native worker lifecycle and health feedback so admission, completion and retained failure evidence stay distinct. This does not introduce a new delivery mode, manual queue, permission or automatic replay of uncertain work.","Clarify guidance for roots and native delegated workers, including repeated worker preparation and stored versus request-only reminders. Guidance distinguishes unavailable optional work from an essential blocker: continue independent authorized work where possible and report the concrete blocker when the assigned result depends on it. This changes guidance and role preparation, not permissions, task authority or automatic recovery, and does not guarantee a model will always follow it.","Add an independent scheduling package publisher without changing Unified's installed scheduling dependency or behavior. Component artifact publication is separate from application release publication; this does not select or co-install that separate package in existing installations."],"notices":[{"id":"conversation-addressed-native-send","title":"Ordinary Send follows the conversation, not a captured run","detail":"An ordinary native message may guide current work, wait for the next request boundary, or start a new turn after normal completion. Explicit run-anchored steering remains strict. Stop, captured source and configuration checks still apply. Previously uncertain saved submissions are not automatically replayed.","action":"No setting change is required. Use ordinary Send for a message to the conversation and Stop to interrupt current work. For an uncertain submission, use Check delivery to inspect its saved receipt rather than sending a duplicate; form a fresh retry only after definite rejection with the original target available."}]},
     {"version":"0.90.0","title":"End settled worker management without losing history","changes":["An assignment owner can now end management of a settled worker even when its saved task is unfinished or an earlier settings change failed. Retirement frees the member slot without marking the task successful, changing its saved task or settings, clearing Stop, deleting history or resuming work.","Active writers and settings work, pending or uncertain input and calls, checkout handoffs, shared task claims and unsettled test resources still block retirement. Retired workers with unfinished or unreadable task state cannot use standing automatic readmission; starting new work remains a separate authorized action.","Updated collaboration guidance and focused checks for stopped workers, retained failure records and separate readmission. This release does not itself retire existing chats or repair an earlier saved-versus-loaded settings mismatch.","Fixed fresh installation dependency resolution by having the shipped Foundation and session-naming defaults follow their common main source, matching Memory. New default worker preparations follow the same source; explicit installed pins, forks and existing runtime generations keep their recorded selections."],"notices":[]},

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "amplifier-unified"
-version = "0.92.0"
+version = "0.92.1"
 description = "A local voice-first Amplifier workspace with a shared user and agent interface"
 readme = "README.md"
 requires-python = ">=3.13"