@pellux/goodvibes-agent 1.0.31 → 1.0.33

package/CHANGELOG.md

@@ -2,8 +2,43 @@
 
 Product-facing release notes for GoodVibes Agent.
 
-## 1.0.31 - 2026-06-03
-
+## 1.0.33 - 2026-06-04
+
+- Fixed the release lockfile so frozen CI installs resolve @pellux/goodvibes-sdk@0.33.36 and its published peer packages.
+- Carries forward the 1.0.32 model-facing harness coverage, compact tool catalog, keybinding discovery fallback, and connected-host release evidence.
+
+## 1.0.32 - 2026-06-04
+
+- Pin the Agent release line to `@pellux/goodvibes-sdk@0.33.36` so the packaged connected-host runtime includes Agent Knowledge alias scope normalization and telephony channel surface support.
+- Refresh release readiness evidence to match the current strict live verification run: 19 pass, 0 warn, 0 fail, 0 skip.
+- Treat environment-provisioned connected-host operator tokens as first-class status, doctor, auth, pairing, Agent Knowledge, and model-visible connected-host credentials.
+- Expose channel readiness through `agent_harness` with summary/search and single-channel lookup so the model can inspect setup state, delivery posture, risk labels, and safe config-key names before using the explicit confirmed send tool.
+- Expose notification target posture through `agent_harness` with redacted summary/search and single-target lookup so the model can inspect configured target readiness without receiving full webhook values.
+- Expose provider account posture through `agent_harness` with summary/search and single-provider lookup so the model can inspect auth routes, subscription freshness, usage windows, route issues, and confirmation-gated account actions without receiving tokens.
+- Expose MCP server posture through `agent_harness` with summary/search and single-server lookup so the model can inspect connection, trust, role, quarantine, and tool inventory posture before using explicit confirmed workspace or slash-command mutation flows.
+- Expose setup/onboarding posture through `agent_harness` with summary/search and single setup-item lookup so the model can inspect onboarding snapshot state, derived capability flags, setup marker state, local behavior discovery, channel/media/setup signals, and setup collection issues without applying setup.
+- Expose provider/model routing through `agent_harness` with summary/search and single route/model lookup so the model can inspect current chat route, selectable models, provider ids, pinned models, reasoning support, context windows, and safe route setting keys without changing routes.
+- Expose companion pairing posture through `agent_harness` with summary/search and single pairing-route lookup so the model can inspect endpoint binding, pairing surface id, token presence/fingerprint, and route catalog without receiving raw tokens or QR payloads.
+- Expose explicit build-delegation posture through `agent_harness` with summary/search and single-route lookup so the model can inspect delegation routes, runtime availability, review policy, main-conversation ownership, and blocked local coding ownership without submitting delegated work.
+- Expose security/support posture through `agent_harness` with redacted summary/search, single-finding lookup, bundle route discovery, and existing-bundle inspection by counts and redaction metadata without returning raw config, token, or secret values.
+- Expose voice/media posture through `agent_harness` with summary/search and single-provider lookup so the model can inspect provider readiness, selected TTS setup, browser-tool posture, artifact availability, and safe secret-key names before using confirmed media generation or settings routes.
+- Expose sessions/bookmarks through `agent_harness` with current-session posture, saved-session metadata/search, bookmark counts, saved bookmark file counts, and single-session lookup while save/resume/export/delete/bookmark changes stay visible user flows.
+- Compact model-facing tool registration and schema descriptions, with package verification thresholds to prevent tool-description bloat from returning.
+- Compact `agent_harness` summary route hints so the model gets concise mode names and confirmation rules instead of paragraph-length surface guidance.
+- Keep shortcut and keybinding discovery available when the live keybinding manager is absent by returning default-fallback descriptors while keybinding execution and mutation still fail closed.
+
+## 1.0.31 - 2026-06-04
+
+- Expose the packaged release evidence bundle through agent_harness so the model can inspect release notes, performance snapshot, readiness inventory, and live-verification artifacts.
+- Expose service posture and single-endpoint diagnostics through agent_harness so the model can inspect status/doctor/support-bundle endpoint posture without connected-host lifecycle control.
+- Expose the public operator method catalog through agent_harness with preferred first-class tool routes and single-method lookup, without arbitrary route invocation.
+- Expand agent_knowledge beyond status/ask/search to cover read-only source, node, issue, item, map, connector, and connector doctor inspection.
+- Expand live verification definitions to check isolated Agent Knowledge source, node, issue, map, and connector routes in addition to status, ask, and search.
+- Strengthen architecture/package policy so the full Agent Knowledge route catalog remains Agent-specific.
+- Reject Agent Knowledge responses that expose default scope metadata or known non-Agent payload markers across CLI, model tools, and live verification.
+- Count the packaged release evidence bundle and release-evidence harness modes in the verification ledger.
+- Count the model-visible service posture modes and endpoint ids in the verification ledger.
+- Count the model-visible operator method catalog modes and sources in the verification ledger.
 - Expose settings catalog filters in the agent_harness summary so the model can discover category, prefix, query, includeHidden, and limit before mutating settings.
 - Expose model-tool catalog schema inlining in the agent_harness summary and package docs.
 - Add focused harness coverage for settings filter guidance and model-tool includeParameters schema inlining.
@@ -187,7 +222,7 @@ Product-facing release notes for GoodVibes Agent.
 
 ## 1.0.0 - 2026-06-03
 
-- Promoted GoodVibes Agent to the release-candidate operator product surface: the fullscreen Agent workspace is the primary TUI, with setup, provider/model routing, status, compatibility, and doctor flows shaped around personal operator use instead of copied host lifecycle controls.
+- Promoted GoodVibes Agent to the stable 1.0.x operator product surface: the fullscreen Agent workspace is the primary TUI, with setup, provider/model routing, status, compatibility, and doctor flows shaped around personal operator use instead of copied host lifecycle controls.
 - Completed the Agent-local behavior system for day-one operation: local memory and notes, personas, skills, skill bundles, routines, starter profiles, discovery/import flows, review/stale/delete controls, and secret-looking content rejection all stay under Agent ownership.
 - Completed isolated Agent Knowledge coverage across CLI, slash commands, workspace panels, connector/source/node/issue views, URL/file/browser/connector ingest, semantic ask/search, and connected-host `/api/goodvibes-agent/knowledge/*` routes without fallback to default or non-Agent knowledge surfaces.
 - Completed connected-host operator integration without taking host lifecycle ownership: compatibility/status checks, authenticated health and model routes, channel readiness, provider-account posture, approvals, automation snapshots, schedules, work plans, media/voice readiness, pairing, and explicit public-route diagnostics are all visible from Agent.

package/README.md

@@ -7,7 +7,7 @@ GoodVibes Agent is the personal operator assistant TUI for GoodVibes. It is buil
 
 The Agent product connects to a GoodVibes host owned outside this package. It does not install, start, stop, restart, or own that host.
 
-Most work happens in the interactive TUI. The installed CLI exists to launch that TUI and provide scriptable mirrors for workflows that are already reachable from the workspace. The main Agent model can inspect the same harness surface through Agent-owned tools: workspace categories/actions and single-action lookup, built-in panels and single-panel lookup, modal/overlay/picker UI surfaces and single-surface lookup, named operator surfaces, top-level CLI mirrors and single-mirror lookup with preferred model routes, fixed shortcuts, configurable keybindings, single-keybinding lookup, shell-safe keybinding execution, slash commands, single-command lookup with effect, boundary, and preferred-route policy metadata, filtered settings and single-setting lookup, model tools with optional schema inlining and individual model tool schemas, local registries, connected-host capability boundaries, and live connected-host readiness are all discoverable from the conversation without exposing connected-host lifecycle control.
+Most work happens in the interactive TUI. The installed CLI exists to launch that TUI and provide scriptable mirrors for workflows that are already reachable from the workspace. The main Agent model can inspect the same harness surface through Agent-owned tools: workspace categories/actions and single-action lookup, built-in panels and single-panel lookup, modal/overlay/picker UI surfaces and single-surface lookup, named operator surfaces, top-level CLI mirrors and single-mirror lookup with preferred model routes, fixed shortcuts, configurable keybindings, single-keybinding lookup, shell-safe keybinding execution, slash commands, single-command lookup with effect, boundary, and preferred-route policy metadata, filtered settings and single-setting lookup, direct channel/notification/provider-account/MCP/setup/model-routing/pairing/delegation/security/support/media/session posture modes, compact model tools with optional schema inlining and individual model tool schemas, release evidence bundle summary/search/single-artifact lookup, release-readiness inventory summary/search/single-item lookup, local registries, public operator method catalog, service endpoint posture, connected-host capability boundaries, and live connected-host readiness are all discoverable from the conversation without exposing connected-host lifecycle control.
 
 ## Install
 
@@ -56,7 +56,7 @@ Use the workspace as the primary product surface:
 - Artifacts: image attachment, conversation/session export, source-file ingest, source lookup, bookmark/browser-history import, and generated media artifact handling.
 - Setup: provider/model, compatibility, Agent Knowledge readiness, profiles, support bundles, subscriptions, and auth review.
 - Tools & MCP: MCP server setup, tool inventory, trust review, secret storage/link/test/delete, and settings.
-- Knowledge: isolated Agent Knowledge status, ask/search, URL/URL-list/file/bookmark/browser-history/connector ingest, source library, review queue, and reindex.
+- Knowledge: isolated Agent Knowledge status, ask/search, source/node/issue libraries, item lookup, map review, connector inspection, URL/URL-list/file/bookmark/browser-history/connector ingest, review queue, and reindex.
 - Memory & Skills: local memory, scratchpad notes, learned behavior capture, personas, skills, routines, and schedule promotion.
 - Notes: Agent-local scratchpad for source triage, temporary decisions, and operator handoff. Notes do not become memory or Agent Knowledge unless you explicitly promote or ingest something; reviewed notes can prefill memory, skills, routines, personas, or an isolated Agent Knowledge URL ingest.
 - Channels: companion pairing, channel readiness, confirmed channel delivery, and confirmed webhook add/remove/test/send.
@@ -66,7 +66,9 @@ Use the workspace as the primary product surface:
 
 Inside the Agent workspace, press `/` to search every workspace action by name, category, command, or detail. This is the primary discovery path for product actions; slash commands and CLI subcommands remain power-user/scriptable mirrors.
 
-The model has the same harness map through `agent_harness`: it can list Agent workspace categories, list Agent workspace actions, inspect or run one workspace action by `actionId`, `command`, `target`, or `query`, list built-in panels and inspect one panel by `panelId`, `target`, or `query`, inspect modal/overlay/picker UI surfaces by `surfaceId`, `target`, or `query`, list top-level CLI mirrors and inspect one mirror by `cliCommand`, `command`, `commandName`, `target`, or `query`, inspect fixed shortcuts and configurable keybindings by `actionId`, `target`, `key`, or `query`, run shell-safe keybinding equivalents with confirmation, list slash commands, inspect or run one slash command by `command`, `commandName`, `target`, or `query` with parsed arguments and concrete built-in effect, boundary, and preferred-route policy metadata, inspect model tool definitions with optional schema inlining or one model tool schema, filter/list Agent settings by `category`, `prefix`, `query`, `includeHidden`, and `limit`, inspect or change Agent settings by `key`, `target`, or `query` with confirmation, and report connected-host capability and live readiness posture. CLI mirror modes are read-only catalog and parser inspection, and every supported top-level mirror reports the preferred in-process model route or current-conversation route; inside the main conversation, the model uses that returned route instead of launching hidden nested CLI processes. Panel modes expose catalog/open state and route visible panel/workspace changes through the current Agent shell bridge with confirmation. UI surface modes expose help, shortcuts, command browser, conversation search, prompt-history search, slash-command mode, file picker, block actions, context, runtime activity, live process output, bookmarks, model/provider/reasoning-effort pickers, TTS provider/voice pickers, session/profile pickers, the panel-picker compatibility route, security/knowledge/subscription operator surfaces, settings, MCP workspace, onboarding, and Agent workspace entrypoints; `open_ui_surface` is confirmation-gated and only performs visible shell navigation. Shortcut modes expose fixed runtime/editor controls plus the live resolved keybinding table; each keybinding descriptor reports its model operation route, `run_keybinding` executes only supported shell-safe equivalents with confirmation, and prompt-editor-only or terminal-selection shortcuts remain explicit direct user interaction. `set_keybinding` and `reset_keybinding` write the same `keybindings.json` file the user edits and require confirmation. Workspace action discovery can inline editor field schemas with `includeParameters:true`; every editor action descriptor reports `modelExecution` route metadata for local-registry, slash-command, direct local-create, prompt-returning, or first-class-tool execution; model tool discovery can inline JSON schemas with `includeParameters:true`; single-action lookup and execution use the same user-facing search fields, return or preserve lookup metadata where the action result carries descriptors, and refuse ambiguous run requests with candidates; CLI mirror, panel, UI surface, keybinding, slash-command, model tool, setting, and connected-host capability lookup use their catalog search fields and refuse ambiguous route, schema, capability, or mutation requests with candidates; confirmed slash-command execution uses the same slash-command lookup and refuses ambiguous requests before any handler runs; profile editors use the current starter-template inventory, and routine schedule editors can prefill a selected local routine from `recordId`. Selection-based local workspace actions accept a local `recordId` so the model can use the same note promotion and local registry flows as the TUI. Direct local create editors for memory, notes, personas, skills, and routines can execute from submitted fields through `run_workspace_action` and `agent_local_registry` with confirmation. Command-backed editor actions execute through the shared slash-command registry with confirmation, while web research/fetch editor actions return the main-conversation prompt for the model to use directly. The `connected_host` report includes route families, allowed capabilities, blocked lifecycle/non-Agent surfaces, and availability for the first-class Agent tools; `connected_host_capability` inspects one allowed or blocked capability by id, target, or query with its route families and boundary. The `connected_host_status` report performs a read-only live check of the connected-host status route and the isolated Agent Knowledge status route, reports SDK compatibility, token posture, endpoint bindings, route readiness, and actionable findings, and still refuses connected-host lifecycle control. The model uses those first-class tools for product workflows where they exist, such as Agent Knowledge, local memory/notes/personas/skills/routines, channel sends, notifications, reminders, media generation, work plans, and connected-host operator actions.
+The model has the same harness map through `agent_harness`: it can list Agent workspace categories, list Agent workspace actions, inspect or run one workspace action by `actionId`, `command`, `target`, or `query`, list built-in panels and inspect one panel by `panelId`, `target`, or `query`, inspect modal/overlay/picker UI surfaces by `surfaceId`, `target`, or `query`, list top-level CLI mirrors and inspect one mirror by `cliCommand`, `command`, `commandName`, `target`, or `query`, inspect fixed shortcuts and configurable keybindings by `actionId`, `target`, `key`, or `query`, run shell-safe keybinding equivalents with confirmation, list slash commands, inspect or run one slash command by `command`, `commandName`, `target`, or `query` with parsed arguments and concrete built-in effect, boundary, and preferred-route policy metadata, inspect model tool definitions with optional schema inlining or one model tool schema, inspect the release evidence bundle by summary, search, or single artifact, inspect the release-readiness inventory by summary, search, or single item, filter/list Agent settings by `category`, `prefix`, `query`, `includeHidden`, and `limit`, inspect or change Agent settings by `key`, `target`, or `query` with confirmation, inspect public operator methods by summary or single method, inspect service posture or one service endpoint, and report connected-host capability and live readiness posture. CLI mirror modes are read-only catalog and parser inspection, and every supported top-level mirror reports the preferred in-process model route or current-conversation route; inside the main conversation, the model uses that returned route instead of launching hidden nested CLI processes. Panel modes expose catalog/open state and route visible panel/workspace changes through the current Agent shell bridge with confirmation. UI surface modes expose help, shortcuts, command browser, conversation search, prompt-history search, slash-command mode, file picker, block actions, context, runtime activity, live process output, bookmarks, model/provider/reasoning-effort pickers, TTS provider/voice pickers, session/profile pickers, the panel-picker compatibility route, security/knowledge/subscription operator surfaces, settings, MCP workspace, onboarding, and Agent workspace entrypoints; `open_ui_surface` is confirmation-gated and only performs visible shell navigation. Shortcut modes expose fixed runtime/editor controls plus the live resolved keybinding table; each keybinding descriptor reports its model operation route, `run_keybinding` executes only supported shell-safe equivalents with confirmation, and prompt-editor-only or terminal-selection shortcuts remain explicit direct user interaction. `set_keybinding` and `reset_keybinding` write the same `keybindings.json` file the user edits and require confirmation. Workspace action discovery can inline editor field schemas with `includeParameters:true`; every editor action descriptor reports `modelExecution` route metadata for local-registry, slash-command, direct local-create, prompt-returning, or first-class-tool execution; model tool discovery can inline JSON schemas with `includeParameters:true`; release evidence discovery can inline artifact source/data with `includeParameters:true`; release readiness discovery can inline source and quality detail with `includeParameters:true`; operator method discovery can inline parameter hints with `includeParameters:true`; service posture discovery can include reachability probes and a redacted log tail with `includeParameters:true`; single-action lookup and execution use the same user-facing search fields, return or preserve lookup metadata where the action result carries descriptors, and refuse ambiguous run requests with candidates; CLI mirror, panel, UI surface, keybinding, slash-command, model tool, release-evidence artifact, release-readiness item, operator method, service endpoint, setting, and connected-host capability lookup use their catalog search fields and refuse ambiguous route, schema, capability, or mutation requests with candidates; confirmed slash-command execution uses the same slash-command lookup and refuses ambiguous requests before any handler runs; profile editors use the current starter-template inventory, and routine schedule editors can prefill a selected local routine from `recordId`. Selection-based local workspace actions accept a local `recordId` so the model can use the same note promotion and local registry flows as the TUI. Direct local create editors for memory, notes, personas, skills, and routines can execute from submitted fields through `run_workspace_action` and `agent_local_registry` with confirmation. Command-backed editor actions execute through the shared slash-command registry with confirmation, while web research/fetch editor actions return the main-conversation prompt for the model to use directly. The `operator_methods` report exposes the allowlisted public operator and Agent Knowledge method catalog with owning first-class tools; `operator_method` inspects one method by `methodId`, `target`, or `query`, and still does not allow arbitrary route invocation. The `service_posture` report exposes the same endpoint binding, network-facing posture, issue, and redacted-log diagnostics used by status, doctor, and support bundles; `service_endpoint` inspects one endpoint by `endpointId`, `target`, or `query`. The `connected_host` report includes route families, allowed capabilities, blocked lifecycle/non-Agent surfaces, and availability for the first-class Agent tools; `connected_host_capability` inspects one allowed or blocked capability by id, target, or query with its route families and boundary. The `connected_host_status` report performs a read-only live check of the connected-host status route and the isolated Agent Knowledge status route, reports SDK compatibility, token posture, endpoint bindings, route readiness, and actionable findings, and still refuses connected-host lifecycle control. The model uses those first-class tools for product workflows where they exist, such as Agent Knowledge status/ask/search, source/node/issue libraries, item lookup, map review, connector inspection, local memory/notes/personas/skills/routines, channel sends, notifications, reminders, media generation, work plans, and connected-host operator actions.
+
+Direct `agent_harness` posture modes cover channel readiness (`channels`/`channel`), notification targets (`notifications`/`notification_target`), provider accounts (`provider_accounts`/`provider_account`), MCP servers (`mcp_servers`/`mcp_server`), setup/onboarding (`setup_posture`/`setup_item`), provider/model routing (`model_routing`/`model_route`), companion pairing (`pairing_posture`/`pairing_route`), explicit build delegation (`delegation_posture`/`delegation_route`), security/support bundles (`security_posture`, `security_finding`, `support_bundles`, `support_bundle`), voice/media (`media_posture`/`media_provider`), and sessions/bookmarks (`sessions`/`session`). These read-only modes return posture, safe ids, counts, route hints, and redacted diagnostics; delivery, setup apply, provider/model changes, pairing/manual-token display, delegation submissions, media generation, auth, trust, bundle, MCP, session, and bookmark mutations stay explicit visible user flows.
 
 The setup workspace surfaces discovered Agent-local persona, skill, and routine markdown files so day-one setup can import useful behavior instead of starting from blank records. It can also create one initial scratchpad note, local persona, skill, and routine directly during first-run setup; those records stay in Agent-local registries and never write to default knowledge or non-Agent segments.
 
@@ -74,7 +76,7 @@ In the Profiles workspace, choose Starter authoring guide to author custom profi
 
 Use the Profiles workspace form to turn reviewed discovered persona, skill, and routine files into a local starter template and isolated Agent profile in one confirmed flow. The scriptable equivalent is `profiles create-from-discovered <name> --yes`; `profiles templates from-discovered <id> --yes` is still available when you only want to save the starter first.
 
-The Knowledge area includes an in-workspace URL ingest form. It writes only to Agent Knowledge, requires typed confirmation, and dispatches the existing isolated `/knowledge ingest-url ... --yes` route.
+The Knowledge area includes an in-workspace URL ingest form. It writes only to Agent Knowledge, requires typed confirmation, and dispatches the existing isolated `/knowledge ingest-url ... --yes` route. Agent Knowledge calls fail closed if a connected-host response exposes default scope metadata or known non-Agent payload markers.
 
 The Research workspace submits web research and URL inspection requests back to the normal Agent conversation. These requests can use connected read-only web tools when the user asks, but they do not ingest sources into Agent Knowledge. Use the separate confirmed Agent Knowledge ingest actions when a reviewed source should become durable.
 
@@ -114,7 +116,7 @@ Start the owning GoodVibes host before launching Agent. Agent status and compani
 
 Use `--runtime-url http://host:port` for a one-off launch, or set `GOODVIBES_AGENT_RUNTIME_URL=http://host:port` when the connected host is not on the default local port. The legacy `GOODVIBES_AGENT_BASE_URL` env var is also accepted as an alias. These only change the connection target; Agent still does not host or start it.
 
-Agent reports unavailable, unauthenticated, or incompatible connected-host state from Agent Workspace -> Home through Host compatibility, Doctor diagnostics, and Review health. `goodvibes-agent status`, `goodvibes-agent doctor`, and `goodvibes-agent compat` are scriptable mirrors for install checks. The model-visible `agent_harness` mode `connected_host_status` exposes the same live readiness posture from the conversation without printing token values or exposing host lifecycle operations. Host lifecycle stays outside the Agent product.
+Agent reports unavailable, unauthenticated, or incompatible connected-host state from Agent Workspace -> Home through Host compatibility, Doctor diagnostics, and Review health. `goodvibes-agent status`, `goodvibes-agent doctor`, and `goodvibes-agent compat` are scriptable mirrors for install checks. The model-visible `agent_harness` modes `service_posture`, `service_endpoint`, and `connected_host_status` expose service endpoint posture and live readiness from the conversation without printing token values or exposing host lifecycle operations. Host lifecycle stays outside the Agent product.
 
 ## Product Boundary