@pellux/goodvibes-agent 0.1.107 → 0.1.108

package/CHANGELOG.md

@@ -2,11 +2,38 @@
 
 All notable changes to GoodVibes Agent will be recorded here.
 
-## 0.1.107 - Unreleased
+## 0.1.108 - 2026-06-02
+
+- f6b278c Harden Agent install and briefing
+- 46fa071 Split Agent Knowledge CLI helpers
+- ec03fc0 Add Agent Knowledge connector ingest
+- 8c908ca Add Agent Knowledge connector inspection
+- 4dda70e Add Agent Knowledge browser history import
+- 95bbdbd Add Agent Knowledge file ingest
+- 2440959 Add discovered skill import workflow
+- 692c0fa Add confirmed reminder scheduling
+- a392cc0 Use connected services product language
+- 5843cb4 Clean Agent launch and service wording
+- ee31dac Open routine starts through command router
+- c9512e5 Use Agent-first connected service language
+- 2d8d7f4 Focus onboarding on Agent setup
+- 855ed91 Trim unused root package dependencies
+- d74ae6c Add profile starter workspace forms
+- 0f7e834 Add workspace forms for bookmarks media and skill bundles
+- c140c9d Tolerate SDK overflow fail-closed refs
+- 5093419 Add Agent Knowledge workspace query forms
+- c76b249 Add routine schedule workspace form
+- 8615c68 Tighten Agent runtime boundary wording
+- f4cb026 Add Agent Knowledge URL workspace form
+- f523594 Add Agent channel readiness command
+- 65f0bfd Make Agent help TUI first
+
+## 0.1.107 - 2026-06-01
 
-- Add `goodvibes-agent launch` and `goodvibes-agent start` as explicit aliases for starting the Agent TUI.
 - Open the Agent operator workspace automatically on normal TUI launch after first-run setup has been shown.
-- Document the Bun global install path with `goodvibes-agent launch` as the first interactive smoke.
+- Document the Bun global install path with bare `goodvibes-agent` as the interactive smoke.
+- Add an in-TUI `/channels` readiness command and workspace action for read-only channel setup review without sending messages or exposing token values.
+- Add a confirmed in-workspace Agent Knowledge URL ingest form that writes only through the isolated Agent Knowledge route.
 
 ## 0.1.106 - 2026-06-01
 
@@ -17,7 +44,7 @@ All notable changes to GoodVibes Agent will be recorded here.
 - Remove copied file-edit undo/redo behavior from Agent conversation commands.
 - Remove stale hidden-share shortcut guidance and keep diff/file operations delegation-oriented.
 - Make provider onboarding generic across provider routes, subscription sessions, and credential inventory while keeping OpenAI as an optional quick-start path.
-- Remove internal audit phrase leakage from source/package-facing guards and neutralize non-Agent knowledge wording.
+- Tighten package-facing language around isolated Agent Knowledge and non-Agent knowledge boundaries.
 - Shorten release workflow validation by relying on the single branch-CI gate run instead of duplicating release checks.
 
 ## 0.1.105 - 2026-06-01
@@ -97,7 +124,7 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 ## 0.1.88 - 2026-06-01
 
-- e97d2a2 Fix release test daemon port allocation
+- e97d2a2 Fix release test service port allocation
 
 ## 0.1.87 - 2026-06-01
 
@@ -115,13 +142,11 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 - 35dbf3d Show live external runtime status
 
-## Unreleased
+## 0.1.83 - 2026-06-01
 
 - Foregrounded live external-runtime reachability, SDK compatibility, operator-token state, and isolated Agent Knowledge readiness in `status`/`doctor` output.
 - Removed the deprecated `actions/cache@v4` setup step so future CI/CD runs avoid Node 20 deprecation annotations from the shared workflow setup action.
 
-## 0.1.83 - 2026-06-01
-
 - f5099c1 Hide runtime-owned settings from Agent workspace
 
 ## 0.1.82 - 2026-06-01
@@ -132,8 +157,8 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 - Added local Agent skill bundles so users can group related local skills, enable or disable the bundle, and inject the bundle's member procedures into the same serial assistant conversation.
 - Added `/agent-skills bundle ...` commands plus Agent workspace visibility for skill bundle counts, enabled bundle state, active skill count, and bundle membership.
-- Restored the GitHub CI eval gate script and replaced the copied TUI/daemon release workflow with an Agent package release workflow that validates Bun global install, package contents, compiled binary launch, and optional npm publish.
-- Kept bundles Agent-local and reviewable with no daemon lifecycle behavior, hidden background agents, or non-Agent knowledge fallback.
+- Restored the GitHub CI eval gate script and replaced the copied release workflow with an Agent package release workflow that validates Bun global install, package contents, compiled binary launch, and optional registry publish.
+- Kept bundles Agent-local and reviewable with no connected-service lifecycle behavior, hidden background agents, or non-Agent knowledge fallback.
 
 ## 0.1.80 - 2026-06-01
 
@@ -226,7 +251,7 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 - Made the operator workspace more product-facing by replacing foundation/setup jargon with Agent profile, runtime status, voice/media, and browser-tool language.
 - Removed the remote-runner item from the first-run voice/media workspace so day-one setup stays focused on user-facing assistant capabilities.
-- Reworded settings, status panels, profile commands, and docs away from control-plane/runtime-profile terminology while preserving the same underlying contracts.
+- Reworded settings, status panels, profile commands, and docs away from internal runtime terminology while preserving the same underlying contracts.
 
 ## 0.1.64 - 2026-05-31
 
@@ -283,7 +308,7 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 ## 0.1.55 - 2026-05-31
 
-- d8f4eee Remove copied developer audit surfaces
+- d8f4eee Remove developer-only setup surfaces
 
 ## 0.1.54 - 2026-05-31
 
@@ -316,7 +341,7 @@ All notable changes to GoodVibes Agent will be recorded here.
 
 ## 0.1.48 - 2026-05-31
 
-- 67f8ce0 Remove audit remnants and surface setup checklist
+- 67f8ce0 Surface the Agent setup checklist
 - 34c3d0b Remove internal development-only surfaces
 
 ## 0.1.47 - 2026-05-31

package/README.md

@@ -5,7 +5,9 @@
 
 GoodVibes Agent is the personal operator assistant TUI for GoodVibes. It is built for day-to-day operator work: chat, setup, local profiles, routines, skills, personas, isolated Agent Knowledge, status review, approvals, automation visibility, and explicit build delegation.
 
-The Agent product connects to an already-running GoodVibes runtime. It does not install, start, stop, restart, or own runtime hosting.
+The Agent product connects to GoodVibes services owned outside this package. It does not install, start, stop, restart, or own those services.
+
+Most work happens in the interactive TUI. The installed CLI exists to launch that TUI, inspect setup, and script local Agent libraries when that is useful.
 
 ## Install
 
@@ -14,7 +16,7 @@ Install the public alpha package with Bun:
 ```sh
 bun add -g --trust @pellux/goodvibes-agent
 goodvibes-agent --help
-goodvibes-agent launch
+goodvibes-agent
 goodvibes-agent status
 goodvibes-agent profiles templates
 goodvibes-agent personas list
@@ -25,6 +27,15 @@ goodvibes-agent knowledge list --kind sources
 goodvibes-agent knowledge import-urls ./agent-sources.txt --yes
 ```
 
+The bare Bun global install path is also supported:
+
+```sh
+bun add -g @pellux/goodvibes-agent
+goodvibes-agent
+```
+
+If Bun reports blocked lifecycle scripts, the command should still install, but provider parsers and SDK helper dependencies may not be fully prepared until the package is trusted. Run the trust check and targeted trust command below.
+
 If `goodvibes-agent` is not found after installation, add Bun's global bin directory to `PATH`:
 
 ```sh
@@ -32,7 +43,7 @@ export PATH="$(bun pm bin -g):$PATH"
 goodvibes-agent --help
 ```
 
-`goodvibes-agent` and `goodvibes-agent launch` both start the interactive Agent TUI. On a fresh Agent home, the TUI opens Agent setup first.
+`goodvibes-agent` starts the interactive Agent TUI. On a fresh Agent home, the TUI opens Agent setup first.
 
 `--trust` lets Bun run the package lifecycle scripts required by the shipped SDK and parser dependencies during global install. A healthy install should report no pending lifecycle scripts:
 
@@ -65,10 +76,12 @@ bun run package:install-check
 bun run publish:check
 ```
 
-After setup has been shown once, the Agent TUI opens directly into the operator workspace. You can also reopen it with `/agent`, `/home`, or `/operator`. It is the Agent-first fullscreen workspace for setup, status, knowledge, local memory/skills, work-plan/approval review, automation observability, and explicit build delegation to GoodVibes TUI.
+After setup has been shown once, the Agent TUI opens directly into the operator workspace. You can also reopen it with `/agent`, `/home`, or `/operator`. It is the Agent-first fullscreen workspace for setup, model/provider selection, isolated Agent Knowledge, local memory/skills/routines/personas, channel readiness, voice/media setup, work-plan/approval review, automation observability, and explicit build delegation to GoodVibes TUI.
 
 Inside the workspace, use `/agent-profile guide` to author custom profile starters without leaving the Agent TUI. The guided flow lists starters, exports starter JSON, imports edited local starters, and creates isolated Agent profiles from them.
 
+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.
+
 Use isolated Agent profiles when one machine needs separate operator identities or local state:
 
 ```sh
@@ -83,7 +96,7 @@ goodvibes-agent --agent-profile household status
 GOODVIBES_AGENT_HOME=/path/to/agent-home goodvibes-agent status
 ```
 
-Profiles isolate Agent-local config, sessions, local memory, personas, skills, routines, and setup state. Starter templates seed local personas, skills, and routines for household, research, travel, operations, and personal productivity profiles; exported starter JSON can be edited and re-imported as a local starter. The GoodVibes runtime is still external and shared unless the owning host is separately configured otherwise.
+Profiles isolate Agent-local config, sessions, local memory, personas, skills, routines, and setup state. Starter templates seed local personas, skills, and routines for household, research, travel, operations, and personal productivity profiles; exported starter JSON can be edited and re-imported as a local starter. Connected GoodVibes services remain shared unless the owning host is separately configured otherwise.
 
 The same local behavior libraries are available without opening the TUI: `goodvibes-agent personas ...`, `goodvibes-agent skills ...`, `goodvibes-agent memory ...`, and `goodvibes-agent routines ...` list, create, review, enable, stale, export/import where relevant, and delete local Agent records with explicit confirmation for destructive actions.
 
@@ -97,21 +110,24 @@ Local Agent behavior is editable from the TUI:
 /schedule promote-routine evening-review --cron "0 17 * * 1-5" --timezone America/Chicago --delivery-channel slack --yes
 /schedule receipts
 /schedule reconcile
+/channels
 /agent-skills create --name "Morning Brief" --description "Daily briefing flow" --procedure "Check tasks, approvals, calendar, and unread state before summarizing." --enabled true
 /skills local list
 /recall add fact Prefers concise morning briefings --scope project --tags preference
 /recall search morning
 ```
 
-Starting a routine records local usage and prints its steps; it does not spawn background agents or automation jobs. Promotion to an external schedule is separate and explicit: it calls the public `schedules.create` route only after `--yes`, can include explicit delivery targets such as `--delivery-channel slack`, records a redacted local receipt, and the generated scheduled prompt keeps Agent Knowledge isolated from default Knowledge/Wiki and non-Agent knowledge segments. Use `/schedule reconcile` to compare those local receipts against live external schedules through public `schedules.list`.
+Starting a routine records local usage and prints its steps; it does not spawn background agents or automation jobs. Promotion to a connected schedule is separate and explicit: it calls the public `schedules.create` route only after `--yes`, can include explicit delivery targets such as `--delivery-channel slack`, records a redacted local receipt, and the generated scheduled prompt keeps Agent Knowledge isolated from default Knowledge/Wiki and non-Agent knowledge segments. Use `/schedule reconcile` to compare those local receipts against live connected schedules through public `schedules.list`.
+
+Use `/channels` inside the TUI for a read-only channel readiness matrix. It shows enabled channels, missing config key names, delivery posture, and risk labels without sending messages or rendering token values.
 
-## Runtime Prerequisite
+## Connected Services
 
-Start or restart the GoodVibes runtime from GoodVibes TUI or the owning host before launching Agent. Agent status and companion/knowledge routes connect to that external runtime, normally on `http://127.0.0.1:3421`.
+Start connected GoodVibes services from GoodVibes TUI or the owning host before launching Agent. Agent status and companion/knowledge routes normally connect on `http://127.0.0.1:3421`.
 
-Use `--runtime-url http://host:port` for a one-off launch, or set `GOODVIBES_AGENT_RUNTIME_URL=http://host:port` when the runtime API 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 external runtime connection target; Agent still does not host or start the runtime.
+Use `--runtime-url http://host:port` for a one-off launch, or set `GOODVIBES_AGENT_RUNTIME_URL=http://host:port` when connected GoodVibes services are 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 services.
 
-Agent reports unavailable, unauthenticated, or incompatible runtime state through `goodvibes-agent status`, `goodvibes-agent doctor`, and the TUI status views. It does not provide runtime hosting commands.
+Agent reports unavailable, unauthenticated, or incompatible connected-service state through `goodvibes-agent status`, `goodvibes-agent doctor`, and the TUI status views. Service lifecycle commands remain outside the Agent product.
 
 ## Product Boundary
 
@@ -128,7 +144,7 @@ GoodVibes TUI owns coding execution: file edits, git/worktree workflows, coding
 Package-facing docs:
 
 - [Getting Started](docs/getting-started.md)
-- [Runtime Connection](docs/runtime-connection.md)
+- [Connected Services](docs/connected-services.md)
 - [Release And Publishing](docs/release-and-publishing.md)
 
 The package-facing Agent documentation is limited to the docs listed above.

package/docs/README.md

@@ -5,7 +5,7 @@ These are the package-facing docs for GoodVibes Agent, the personal operator ass
 Current package docs:
 
 - [Getting Started](getting-started.md)
-- [Runtime Connection](runtime-connection.md)
+- [Connected Services](connected-services.md)
 - [Release And Publishing](release-and-publishing.md)
 
 Important baseline constraints:
@@ -13,11 +13,11 @@ Important baseline constraints:
 - Agent installs one executable: `goodvibes-agent`.
 - Agent uses Bun and TypeScript-authored source.
 - Agent depends on `@pellux/goodvibes-sdk@0.33.35`.
-- Agent connects to an externally managed GoodVibes runtime.
-- Agent does not start, stop, restart, install, uninstall, or own runtime hosting.
+- Agent connects to GoodVibes services owned outside this product.
+- Agent does not start, stop, restart, install, uninstall, or own those connected GoodVibes services.
 - Agent Knowledge/Wiki uses only `/api/goodvibes-agent/knowledge/*`; there is no default Knowledge/Wiki or non-Agent product fallback.
-- Agent supports isolated runtime homes with `GOODVIBES_AGENT_HOME=<path>` and named profile homes with `goodvibes-agent profiles create <name> --template <starter> --yes` plus `--agent-profile <name>`.
-- Agent supports external runtime URL overrides with `--runtime-url http://host:port` or `GOODVIBES_AGENT_RUNTIME_URL=http://host:port`; these do not make Agent own runtime hosting.
+- Agent supports isolated Agent homes with `GOODVIBES_AGENT_HOME=<path>` and named profile homes with `goodvibes-agent profiles create <name> --template <starter> --yes` plus `--agent-profile <name>`.
+- Agent supports connected-service URL overrides with `--runtime-url http://host:port` or `GOODVIBES_AGENT_RUNTIME_URL=http://host:port`; these only change the Agent connection target.
 - Agent ships starter profile templates for household, research, travel, operations, and personal productivity local state; `profiles templates export/import` and `/agent-profile guide` support local custom starters.
 - Local memory, personas, routines, and Agent skills are stored under the Agent home and are injected only into the serial Agent conversation.
 - Normal assistant chat is not coding-session delegation.

package/docs/{runtime-connection.md → connected-services.md}

@@ -1,6 +1,6 @@
-# Runtime Connection
+# Connected Services
 
-GoodVibes Agent is a TUI client for an already-running GoodVibes runtime. The package exposes one executable:
+GoodVibes Agent is a TUI client for connected GoodVibes services owned outside this package. The package exposes one executable:
 
 ```sh
 goodvibes-agent
@@ -13,9 +13,9 @@ The installed command is backed by TypeScript-authored source with a Bun shebang
 - `goodvibes-agent status --json`
 - `goodvibes-agent` launches the TUI in a real PTY
 
-## Runtime Prerequisite
+## Service Prerequisite
 
-Start the GoodVibes runtime from the owning GoodVibes host before launching Agent. Agent expects the runtime to expose public operator routes and the isolated Agent Knowledge routes:
+Start connected GoodVibes services from GoodVibes TUI or the owning host before launching Agent. Agent expects those services to expose public operator routes and the isolated Agent Knowledge routes:
 
 ```text
 http://127.0.0.1:3421
@@ -24,7 +24,7 @@ http://127.0.0.1:3421
 /api/goodvibes-agent/knowledge/search
 ```
 
-If the runtime API is on a different host or port, use a one-off override:
+If the GoodVibes API is on a different host or port, use a one-off override:
 
 ```sh
 goodvibes-agent --runtime-url http://127.0.0.1:3421 status
@@ -36,15 +36,15 @@ For a persistent shell/session override, set:
 export GOODVIBES_AGENT_RUNTIME_URL=http://127.0.0.1:3421
 ```
 
-`GOODVIBES_AGENT_BASE_URL` is accepted as a legacy alias. These values only select the external runtime API root; they do not enable runtime hosting inside Agent.
+`GOODVIBES_AGENT_BASE_URL` is accepted as a legacy alias. These values only select the connected GoodVibes API root; they do not make Agent own services.
 
-If the runtime is unavailable, unauthenticated, or on an incompatible SDK version, Agent commands report actionable diagnostics without printing token values.
+If connected GoodVibes services are unavailable, unauthenticated, or on an incompatible SDK version, Agent commands report actionable diagnostics without printing token values.
 
 ## Product Boundary
 
 Agent owns the operator assistant TUI, local profiles, local memory/routines/skills/personas, isolated Agent Knowledge calls, companion chat, approvals/automation visibility, and explicit build delegation.
 
-Agent does not host runtime connectivity. It does not provide commands to install, expose, start, stop, restart, or mutate the runtime host.
+Agent does not own connected-service lifecycle. It does not provide commands to install, expose, start, stop, restart, or mutate connected GoodVibes services.
 
 Agent Knowledge/Wiki is its own product segment. Agent uses `/api/goodvibes-agent/knowledge/*` only and must not fall back to default Knowledge/Wiki or other product-specific knowledge routes.
 

package/docs/getting-started.md

@@ -5,23 +5,34 @@ GoodVibes Agent is the installable public alpha of the personal operator assista
 ## Requirements
 
 - Bun `1.3.10` or newer
-- An already-running GoodVibes runtime compatible with `@pellux/goodvibes-sdk@0.33.35`
-- A runtime token/config path accepted by that external runtime
+- Connected GoodVibes services compatible with `@pellux/goodvibes-sdk@0.33.35`
+- A token/config path accepted by connected GoodVibes services
 
-Agent does not launch the runtime for you.
+Agent does not launch connected GoodVibes services for you.
+
+Use the interactive TUI first. CLI subcommands are secondary support paths for install checks, setup inspection, and scriptable local Agent libraries.
 
 ## Install From Package
 
 ```sh
 bun add -g --trust @pellux/goodvibes-agent
 goodvibes-agent --help
-goodvibes-agent launch
+goodvibes-agent
 goodvibes-agent status
 goodvibes-agent personas list
 goodvibes-agent skills list
 goodvibes-agent memory list
 ```
 
+The exact bare Bun command is supported too:
+
+```sh
+bun add -g @pellux/goodvibes-agent
+goodvibes-agent
+```
+
+If Bun blocks lifecycle scripts during the bare install, the executable should still be present. Run `bun pm -g untrusted` and trust the listed GoodVibes/parser dependencies before relying on provider parsing, native parser helpers, or SDK postinstall setup.
+
 If the installed command is not found, add Bun's global bin directory to `PATH`:
 
 ```sh
@@ -53,13 +64,15 @@ bun run dev
 
 `bun run dev` starts the Agent TUI. The same entrypoint backs the installed `goodvibes-agent` command.
 
-`goodvibes-agent` and `goodvibes-agent launch` both start the interactive Agent TUI. On a fresh Agent home, the TUI opens Agent setup first.
+`goodvibes-agent` starts the interactive Agent TUI. On a fresh Agent home, the TUI opens Agent setup first.
 
-After setup has been shown once, the TUI opens directly into the Agent operator workspace. You can also reopen it with `/agent`, `/home`, or `/operator`. That fullscreen workspace is the current front door for setup/config, knowledge status, local memory and skills, read-only work/approval/automation views, and explicit GoodVibes TUI build delegation.
+After setup has been shown once, the TUI opens directly into the Agent operator workspace. You can also reopen it with `/agent`, `/home`, or `/operator`. That fullscreen workspace is the current front door for setup/config, provider/model selection, Agent Knowledge, local memory/skills/routines/personas, channel readiness, voice/media setup, read-only work/approval/automation views, and explicit GoodVibes TUI build delegation.
 
 Use `/agent-profile guide` inside that workspace to walk through starter-profile authoring. It lists built-in and local starters, exports a JSON starter for editing, imports the edited starter back into this Agent home, and creates isolated profiles from the result.
 
-Use `/schedule receipts` to review redacted local routine promotion history and `/schedule reconcile` to compare those receipts with live external schedules through public `schedules.list`.
+Use the Knowledge area in that workspace to ingest a source URL without leaving the TUI. The form requires typed confirmation and writes only to the isolated Agent Knowledge segment.
+
+Use `/schedule receipts` to review redacted local routine promotion history and `/schedule reconcile` to compare those receipts with live connected schedules through public `schedules.list`.
 
 The local behavior libraries are also available from the installed CLI:
 
@@ -89,7 +102,7 @@ goodvibes-agent --agent-profile household status
 goodvibes-agent --agent-profile household
 ```
 
-Named profiles isolate Agent-local config, sessions, memory, personas, skills, routines, and setup state under a profile-specific home. Starter templates seed local personas, skills, and routines for household, research, travel, operations, and personal productivity profiles; exported starter JSON can be edited and re-imported as a local starter. They do not start or isolate the external GoodVibes runtime by themselves.
+Named profiles isolate Agent-local config, sessions, memory, personas, skills, routines, and setup state under a profile-specific home. Starter templates seed local personas, skills, and routines for household, research, travel, operations, and personal productivity profiles; exported starter JSON can be edited and re-imported as a local starter. They do not start or isolate connected GoodVibes services by themselves.
 
 ## Local Memory, Personas, Routines, And Skills
 
@@ -102,6 +115,7 @@ Memory, personas, routines, and reusable Agent skills are local to GoodVibes Age
 /routines create --name "Evening Review" --description "Review open work before shutdown" --steps "Check work plan, approvals, and Agent Knowledge status before summarizing." --enabled true
 /routines start evening-review
 /schedule promote-routine evening-review --cron "0 17 * * 1-5" --timezone America/Chicago --yes
+/channels
 /agent-skills create --name "Morning Brief" --description "Daily briefing flow" --procedure "Check tasks, approvals, calendar, and unread state before summarizing." --enabled true
 /agent-skills enabled
 /skills local list
@@ -111,9 +125,11 @@ Memory, personas, routines, and reusable Agent skills are local to GoodVibes Age
 
 The active persona plus enabled Agent routines, reviewed memory, and skills are injected into the main serial assistant conversation. Starting a routine records local usage and prints its steps; it does not spawn background agents or automation jobs. Promoting a routine to a schedule is an explicit `schedules.create` call, requires `--yes`, writes a local redacted promotion receipt, and preserves the rule that Agent Knowledge never falls back to default Knowledge/Wiki or non-Agent knowledge segments.
 
-## External Runtime
+Use `/channels` inside the TUI for a read-only channel readiness matrix. It shows enabled channels, missing config key names, delivery posture, and risk labels without sending messages or rendering token values.
+
+## Connected GoodVibes Services
 
-Start the runtime from GoodVibes TUI or the owning host before using runtime-backed Agent features. Agent expects the runtime to expose the public operator/Agent routes, including:
+Start connected GoodVibes services from GoodVibes TUI or the owning host before using service-backed Agent features. Agent expects those services to expose the public operator/Agent routes, including:
 
 - `/status`
 - `/api/goodvibes-agent/knowledge/status`
@@ -121,11 +137,11 @@ Start the runtime from GoodVibes TUI or the owning host before using runtime-bac
 - `/api/goodvibes-agent/knowledge/search`
 - `/api/goodvibes-agent/knowledge/ingest/url`
 
-If the runtime API is not on `http://127.0.0.1:3421`, use `goodvibes-agent --runtime-url http://host:port status` for a one-off check or set `GOODVIBES_AGENT_RUNTIME_URL=http://host:port` before launching the TUI.
+If the GoodVibes API is not on `http://127.0.0.1:3421`, use `goodvibes-agent --runtime-url http://host:port status` for a one-off check or set `GOODVIBES_AGENT_RUNTIME_URL=http://host:port` before launching the TUI.
 
 Agent Knowledge/Wiki is an Agent-owned product segment. Agent commands must not fall back to default Knowledge/Wiki or other product-specific knowledge spaces.
 
-Runtime-hosting commands are not part of GoodVibes Agent. Use `goodvibes-agent status`, `goodvibes-agent doctor`, and the Agent TUI status views for diagnostics.
+Service-hosting commands are not part of GoodVibes Agent. Use `goodvibes-agent status`, `goodvibes-agent doctor`, and the Agent TUI status views for diagnostics.
 
 ## Current Product Notes
 

package/docs/release-and-publishing.md

@@ -9,7 +9,7 @@ GoodVibes Agent's current installable public alpha version is recorded in `packa
 - SDK dependency: exact pin to `@pellux/goodvibes-sdk@0.33.35`
 - runtime: Bun
 - source language: TypeScript
-- runtime ownership: external only
+- connected services ownership: outside Agent
 
 End users install and run GoodVibes Agent with Bun:
 
@@ -52,16 +52,16 @@ Also run the package install smoke from a packed artifact. It must prove:
 - `goodvibes-agent --help` works
 - `goodvibes-agent --version` reports the package version
 - the installed TUI launches in a PTY and does not exit immediately
-- runtime-backed commands fail clearly when the external GoodVibes runtime is unavailable or unauthenticated
+- connected-service commands fail clearly when GoodVibes services are unavailable or unauthenticated
 - no token value is printed
 
 ## Do Not Ship
 
-Do not publish if package-facing docs or install commands refer to another package name, another executable, or Agent-owned runtime lifecycle.
+Do not publish if package-facing docs or install commands refer to another package name, another executable, or Agent-owned connected-service lifecycle.
 
 Do not publish if Agent Knowledge commands can fall back to default Knowledge/Wiki or another product-specific knowledge route. Agent Knowledge must use the isolated `/api/goodvibes-agent/knowledge/*` segment.
 
-Do not ship runtime host binaries from this package. If Agent later gets compiled artifacts, they must use Agent artifact names and remain separate from runtime ownership.
+Do not ship GoodVibes service binaries from this package. If Agent later gets compiled artifacts, they must use Agent artifact names and remain separate from connected-service ownership.
 
 ## Product Rule
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pellux/goodvibes-agent",
-  "version": "0.1.107",
+  "version": "0.1.108",
   "private": false,
   "description": "GoodVibes personal operator assistant TUI with a proactive Agent product brain, isolated Agent Knowledge, local profiles, routines, skills, personas, and explicit build delegation.",
   "type": "module",
@@ -22,7 +22,7 @@
     "CHANGELOG.md",
     "docs/README.md",
     "docs/getting-started.md",
-    "docs/runtime-connection.md",
+    "docs/connected-services.md",
     "docs/release-and-publishing.md"
   ],
   "scripts": {
@@ -82,17 +82,7 @@
     "bun": ">=1.3.10"
   },
   "dependencies": {
-    "@agentclientprotocol/sdk": "^0.16.1",
-    "@anthropic-ai/bedrock-sdk": "^0.28.1",
-    "@anthropic-ai/sdk": "^0.82.0",
-    "@anthropic-ai/vertex-sdk": "^0.16.0",
-    "@aws/bedrock-token-generator": "^1.1.0",
     "@pellux/goodvibes-sdk": "0.33.35",
-    "fuse.js": "^7.1.0",
-    "graphql": "^16.13.2",
-    "jszip": "^3.10.1",
-    "node-edge-tts": "^1.2.10",
-    "openai": "^6.29.0",
     "sql.js": "^1.14.1",
     "sqlite-vec": "^0.1.9",
     "zustand": "^5.0.12"

package/src/agent/reminder-schedule-format.ts

@@ -0,0 +1,75 @@
+import {
+  REMINDER_SCHEDULE_METHOD,
+  type ReminderScheduleFailure,
+  type ReminderSchedulePreview,
+  type ReminderScheduleSuccess,
+} from './reminder-schedule.ts';
+
+function isRecord(value: unknown): value is Record<string, unknown> {
+  return Boolean(value) && typeof value === 'object' && !Array.isArray(value);
+}
+
+function readString(record: Record<string, unknown>, key: string): string | null {
+  const value = record[key];
+  return typeof value === 'string' ? value : null;
+}
+
+function scheduleValue(preview: ReminderSchedulePreview): string {
+  if (preview.payload.kind === 'cron') {
+    return `${preview.payload.cron}${preview.payload.timezone ? ` [${preview.payload.timezone}]` : ''}`;
+  }
+  if (preview.payload.kind === 'every') return String(preview.payload.every);
+  return String(preview.payload.at);
+}
+
+export function formatReminderSchedulePreview(preview: ReminderSchedulePreview): string {
+  const delivery = preview.payload.delivery;
+  const deliveryTargetCount = delivery?.targets.length ?? 0;
+  return [
+    'GoodVibes schedule preview for Agent reminder',
+    `  route: ${preview.method} ${preview.route}`,
+    `  name: ${String(preview.payload.name ?? '(service default)')}`,
+    `  reminder: ${preview.message}`,
+    `  schedule: ${preview.payload.kind} ${scheduleValue(preview)}`,
+    `  enabled: ${preview.payload.enabled === false ? 'no' : 'yes'}`,
+    `  delivery: ${delivery?.mode ?? 'none'}${deliveryTargetCount > 0 ? ` (${deliveryTargetCount} target${deliveryTargetCount === 1 ? '' : 's'})` : ''}`,
+    '  target: connected GoodVibes services/main conversation route',
+    '  policy: reminder delivery only; isolated Agent Knowledge only; no default wiki/non-Agent fallback',
+    '  next: rerun with --yes to create this connected reminder schedule',
+  ].join('\n');
+}
+
+export function formatReminderScheduleSuccess(result: ReminderScheduleSuccess): string {
+  const record: Record<string, unknown> = isRecord(result.schedule) ? result.schedule : {};
+  const id = readString(record, 'id') ?? '(unknown)';
+  const status = readString(record, 'status') ?? (record.enabled === false ? 'paused' : 'enabled');
+  return [
+    'Created GoodVibes schedule for Agent reminder',
+    `  schedule: ${id}`,
+    `  status: ${status}`,
+    `  route: ${result.kind} ${result.route}`,
+    `  reminder: ${result.message}`,
+    '  next: inspect with /schedule list',
+  ].join('\n');
+}
+
+export function formatReminderScheduleFailure(failure: ReminderScheduleFailure): string {
+  return [
+    `GoodVibes reminder schedule error: ${failure.kind}`,
+    `  ${failure.error}`,
+    failure.baseUrl ? `  service: ${failure.baseUrl}` : null,
+    `  route: ${REMINDER_SCHEDULE_METHOD} ${failure.route}`,
+    failure.kind === 'version_mismatch' && failure.daemonVersion && failure.expectedSdkVersion
+      ? `  versions: service=${failure.daemonVersion} expected=${failure.expectedSdkVersion}`
+      : null,
+    failure.kind === 'auth_required'
+      ? '  next: pair/authenticate with connected GoodVibes services, then retry with --yes.'
+      : null,
+    failure.kind === 'daemon_unavailable'
+      ? '  next: make connected GoodVibes services available outside Agent, then retry.'
+      : null,
+    failure.kind === 'version_mismatch' || failure.kind === 'daemon_route_unavailable'
+      ? '  next: update connected GoodVibes services so public schedules.create is available.'
+      : null,
+  ].filter((line): line is string => Boolean(line)).join('\n');
+}