@pellux/goodvibes-agent 0.1.116 → 0.1.117

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)
-- [Connected Services](connected-services.md)
+- [Connected Host](connected-host.md)
 - [Release And Publishing](release-and-publishing.md)
 
 Important baseline constraints:
@@ -13,12 +13,13 @@ 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 GoodVibes services owned outside this product.
-- Agent does not start, stop, restart, install, uninstall, or own those connected GoodVibes services.
+- Agent connects to a GoodVibes host owned outside this product.
+- Agent does not start, stop, restart, install, uninstall, or own the connected GoodVibes host.
 - Agent Knowledge/Wiki uses only `/api/goodvibes-agent/knowledge/*`; there is no default Knowledge/Wiki or non-Agent product fallback.
 - 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 supports connected-host 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.
+- First-run setup can seed an initial local persona, skill, and routine without writing to connected-host knowledge or non-Agent segments.
 - 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.
 - Build/fix/review delegation to GoodVibes TUI must be explicit; WRFC is not the default Agent behavior.

package/docs/{connected-services.md → connected-host.md}

@@ -1,21 +1,21 @@
-# Connected Services
+# Connected Host
 
-GoodVibes Agent is a TUI client for connected GoodVibes services owned outside this package. The package exposes one executable:
+GoodVibes Agent is a TUI client for a connected GoodVibes host owned outside this package. The package exposes one executable:
 
 ```sh
 goodvibes-agent
 ```
 
-The installed command is backed by TypeScript-authored source with a Bun shebang. Package install smoke must verify:
+The installed command is backed by TypeScript-authored source with a Bun shebang. Package install smoke verifies the executable path:
 
 - `goodvibes-agent --help`
 - `goodvibes-agent --version`
 - `goodvibes-agent status --json`
 - `goodvibes-agent` launches the TUI in a real PTY
 
-## Service Prerequisite
+## Host Prerequisite
 
-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:
+Start the owning GoodVibes host before launching Agent. Agent expects that host to expose public operator routes and the isolated Agent Knowledge routes:
 
 ```text
 http://127.0.0.1:3421
@@ -24,10 +24,10 @@ http://127.0.0.1:3421
 /api/goodvibes-agent/knowledge/search
 ```
 
-If the GoodVibes 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 when launching the TUI:
 
 ```sh
-goodvibes-agent --runtime-url http://127.0.0.1:3421 status
+goodvibes-agent --runtime-url http://127.0.0.1:3421
 ```
 
 For a persistent shell/session override, set:
@@ -36,15 +36,23 @@ 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 connected GoodVibes API root; they do not make Agent own services.
+`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 host processes.
 
-If connected GoodVibes services are unavailable, unauthenticated, or on an incompatible SDK version, Agent commands report actionable diagnostics without printing token values.
+If the connected host is unavailable, unauthenticated, or on an incompatible SDK version, the Agent TUI reports actionable diagnostics without printing token values.
+
+Use the TUI first for those checks:
+
+- Agent Workspace -> Home -> Host compatibility
+- Agent Workspace -> Home -> Doctor diagnostics
+- Agent Workspace -> Home -> Review health
+
+`goodvibes-agent status --json`, `goodvibes-agent doctor`, and `goodvibes-agent compat` are scriptable equivalents for install checks and automation.
 
 ## 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 own connected-service lifecycle. It does not provide commands to install, expose, start, stop, restart, or mutate connected GoodVibes services.
+Agent does not own connected-host lifecycle. It does not provide commands to install, expose, start, stop, restart, or mutate the connected GoodVibes host.
 
 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,12 +5,12 @@ GoodVibes Agent is the installable public alpha of the personal operator assista
 ## Requirements
 
 - Bun `1.3.10` or newer
-- Connected GoodVibes services compatible with `@pellux/goodvibes-sdk@0.33.35`
-- A token/config path accepted by connected GoodVibes services
+- A connected GoodVibes host compatible with `@pellux/goodvibes-sdk@0.33.35`
+- A token/config path accepted by the connected host
 
-Agent does not launch connected GoodVibes services for you.
+Agent does not launch the connected host for you.
 
-Use the interactive TUI first. CLI subcommands are secondary support paths for install checks, setup inspection, and scriptable local Agent libraries.
+Use the interactive TUI first. CLI subcommands are secondary support paths for install checks, setup inspection, and scriptable mirrors of workflows that are already reachable from the workspace.
 
 ## Install From Package
 
@@ -18,10 +18,6 @@ Use the interactive TUI first. CLI subcommands are secondary support paths for i
 bun add -g @pellux/goodvibes-agent
 goodvibes-agent --help
 goodvibes-agent
-goodvibes-agent status
-goodvibes-agent personas list
-goodvibes-agent skills list
-goodvibes-agent memory list
 ```
 
 If the installed command is not found, add Bun's global bin directory to `PATH`:
@@ -44,74 +40,75 @@ bun run dev
 
 `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, 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.
+After setup has been applied 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.
 
-The setup workspace scans local Agent behavior folders and shows importable persona, skill, and routine files before asking you to create blank records. Use `/personas discover`, `/agent-skills discover`, and `/routines discover` to preview files, then use the matching import action in the workspace after review.
+The setup workspace scans local Agent behavior folders and shows importable persona, skill, and routine files before asking you to create blank records. It can also create one initial local persona, skill, and routine from the setup form. Use `/personas discover`, `/agent-skills discover`, and `/routines discover` to preview files, then use the matching import action in the workspace after review.
 
 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 `goodvibes-agent profiles create-from-discovered research-desk --yes` or the Profiles workspace form to assemble a local starter template and isolated Agent profile from reviewed discovered persona, skill, and routine files. Use `profiles templates from-discovered <id> --yes` only when you want to save the starter before creating a profile.
+Use the Profiles workspace form to assemble a local starter template and isolated Agent profile from reviewed discovered persona, skill, and routine files. Scriptable profile commands mirror the same flow for automation; use them only when you intentionally want a shell-driven setup path.
 
 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`.
+Use the Routines workspace receipt actions to review redacted local routine promotion history and reconcile those receipts with live connected schedules through public `schedules.list`. The `/schedule receipts` and `/schedule reconcile` commands are the power-user equivalents inside the TUI.
 
-The local behavior libraries are also available from the installed CLI:
+The local behavior libraries are configured in the TUI first:
 
-```sh
-goodvibes-agent personas create --name "Research Analyst" --description "Source-backed research" --body "Check sources and call out uncertainty" --use
-goodvibes-agent skills create --name "Morning Brief" --description "Daily briefing flow" --procedure "Check tasks, approvals, routines, and Agent Knowledge before summarizing" --enabled
-goodvibes-agent memory add fact "Prefers concise morning briefings" --scope project --tags preference
-goodvibes-agent routines list
-```
+- Memory & Skills -> Create memory or Capture learned behavior.
+- Personas -> Create persona, Use selected, Review selected, or Delete selected.
+- Skills -> Create skill, Create bundle, Enable selected, Review selected, or Delete selected.
+- Routines -> Create routine, Start selected, Enable selected, Promote to schedule, or Review receipts.
+
+The installed CLI mirrors these libraries for scripts, but it is not the primary user workflow.
 
 ## Isolated Agent Profiles
 
-Use a separate Agent home when you want isolated local state:
+Use a separate Agent home when you want isolated local state. The normal launch still opens the TUI:
 
 ```sh
-GOODVIBES_AGENT_HOME=/path/to/agent-home goodvibes-agent status
+GOODVIBES_AGENT_HOME=/path/to/agent-home goodvibes-agent
 ```
 
-Use named Agent profiles for repeatable local identities:
+Use named Agent profiles for repeatable local identities from Agent Workspace -> Profiles. The workspace can browse starter templates, create isolated Agent profiles, set or clear the default profile for the next launch, and export/import starter JSON.
+
+Scriptable equivalents for automation and setup scripts:
 
 ```sh
 goodvibes-agent profiles templates
 goodvibes-agent profiles create household --template household --yes
+goodvibes-agent profiles use household --yes
+goodvibes-agent
 goodvibes-agent profiles templates export research ./research-starter.json --yes
 goodvibes-agent profiles templates import ./research-starter.json --yes
 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 connected GoodVibes services by themselves.
+Named profiles isolate Agent-local config, sessions, memory, personas, skills, routines, and setup state under a profile-specific home. `profiles use <name> --yes` makes one profile the default for the next plain `goodvibes-agent` launch; `--agent-profile <name>` still overrides it for one launch, and `profiles default clear --yes` returns plain launches to the base Agent 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 connected host by themselves.
 
 ## Local Memory, Personas, Routines, And Skills
 
-Memory, personas, routines, and reusable Agent skills are local to GoodVibes Agent. They do not write into default Knowledge/Wiki or non-Agent knowledge segments.
-
-```text
-/personas list
-/personas create --name Research --description "Source-backed research" --body "Check sources, call out uncertainty, keep answers concise."
-/personas use research
-/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 list
-/memory add fact "Prefers concise morning briefings" --scope project --tags preference
-/memory search morning
-```
+Memory, personas, routines, and reusable Agent skills are local to GoodVibes Agent. First-run setup, TUI workspace forms, and CLI commands all write them to Agent-local registries. They do not write into default Knowledge/Wiki or non-Agent knowledge segments.
+
+Use `Capture learned behavior` in the Agent workspace after reviewing a repeated workflow, lesson, or operating style. It saves one local skill, routine, or persona from the TUI and does not call connected-host mutation routes.
+
+Day-one local behavior setup should stay in the fullscreen workspace:
+
+- Personas -> Create persona, then Use selected.
+- Routines -> Create routine, Start selected, or Promote to schedule after entering real timing and confirmation.
+- Skills -> Create skill, Enable selected, and review setup requirements.
+- Memory & Skills -> Create memory or Search memory.
+- Channels -> inspect readiness before enabling notification delivery.
+
+Typed slash commands are available for repeat users, but they are not required for the first-run workflow.
 
-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.
+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 launch local workers 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.
 
 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
+## Connected GoodVibes Host
 
-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:
+Start the owning GoodVibes host before using connected Agent features. Agent expects that host to expose the public operator/Agent routes, including:
 
 - `/status`
 - `/api/goodvibes-agent/knowledge/status`
@@ -119,11 +116,11 @@ Start connected GoodVibes services from GoodVibes TUI or the owning host before
 - `/api/goodvibes-agent/knowledge/search`
 - `/api/goodvibes-agent/knowledge/ingest/url`
 
-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.
+If the GoodVibes API is not on `http://127.0.0.1:3421`, pass `--runtime-url http://host:port` for a one-off TUI launch 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.
 
-Service-hosting commands are not part of GoodVibes Agent. Use `goodvibes-agent status`, `goodvibes-agent doctor`, and the Agent TUI status views for diagnostics.
+Host lifecycle commands are not part of GoodVibes Agent. Use Agent Workspace -> Home -> Host compatibility, Doctor diagnostics, and Review health for diagnostics. CLI status/doctor/compat commands are scriptable mirrors for install checks.
 
 ## 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
-- connected services ownership: outside Agent
+- connected host ownership: outside Agent
 
 End users install and run GoodVibes Agent with Bun:
 
@@ -36,6 +36,8 @@ git diff --check
 
 `bun run publish:package` publishes from a staged package directory to the package registry. If `NPM_CONFIG_USERCONFIG` is already set, the registry publish command uses it. Otherwise the script creates a temporary 0600 registry userconfig from `NODE_AUTH_TOKEN` or `NPM_TOKEN`, uses it for that publish command, and removes it with the staging directory. The publish script is idempotent for reruns: if the exact package version is already present on the registry, it reports that state and exits successfully instead of failing the release retry.
 
+`bun run release` requires product release notes instead of raw git-log output. Pass `--notes-file ./release-notes.md` or set `GOODVIBES_AGENT_RELEASE_NOTES` before a real release. Release notes should describe what changed for Agent users: TUI behavior, setup, Agent Knowledge, local behavior libraries, connected-host compatibility, package/install behavior, and safety policy. Do not use commit hashes as the shipped changelog content.
+
 The GitHub release workflow publishes to npm only when the repository variable `PUBLISH_NPM` is `true` and the repository secret `NPM_TOKEN` is configured. Without those repository settings, the workflow still validates and creates the GitHub release, but npm publish must be run from a local environment with an exported token.
 
 Branch CI is the only workflow that runs the full test suite and release gates. It runs `bun run test` once for the release SHA, along with typecheck, architecture, performance, build, publish, and packed install checks. The release workflow must not run tests or duplicate those gates; it verifies that branch CI passed for the exact checked-out SHA and then performs only package packing, GitHub Release creation, and optional npm publish.
@@ -52,16 +54,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
-- connected-service commands fail clearly when GoodVibes services are unavailable or unauthenticated
+- connected-host commands fail clearly when GoodVibes host is 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 connected-service lifecycle.
+Do not publish if package-facing docs or install commands refer to another package name, another executable, or Agent-owned connected-host 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 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.
+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-host ownership.
 
 ## Product Rule
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pellux/goodvibes-agent",
-  "version": "0.1.116",
+  "version": "0.1.117",
   "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",
@@ -17,13 +17,14 @@
     "!src/test",
     "!src/**/*.test.ts",
     "!src/**/__tests__",
+    "!src/cli/package-verification.ts",
     "!src/verification",
     "tsconfig.json",
     "README.md",
     "CHANGELOG.md",
     "docs/README.md",
     "docs/getting-started.md",
-    "docs/connected-services.md",
+    "docs/connected-host.md",
     "docs/release-and-publishing.md"
   ],
   "scripts": {
@@ -54,7 +55,6 @@
     "build:all": "bun run scripts/build.ts --all",
     "perf:check": "bun run scripts/perf-check.ts",
     "architecture:check": "bun run scripts/check-architecture.ts",
-    "foundation:artifacts": "bun run scripts/export-foundation-artifacts.ts",
     "verification:ledger": "bun run scripts/verification-ledger.ts",
     "verification:live": "bun run scripts/verify-live.ts"
   },

package/src/agent/behavior-discovery-summary.ts

@@ -126,12 +126,10 @@ function definitions(shellPaths: Pick<ShellPathService, 'workingDirectory' | 'ho
     roots: [
       { root: join(cwd, '.goodvibes', 'personas'), origin: 'project-local' },
       { root: join(cwd, '.goodvibes', GOODVIBES_AGENT_SURFACE_ROOT, 'personas'), origin: 'project-local' },
-      { root: join(cwd, '.goodvibes', 'agents'), origin: 'project-local' },
       { root: join(homeDir, '.goodvibes', 'personas'), origin: 'global' },
       { root: join(homeDir, '.goodvibes', GOODVIBES_AGENT_SURFACE_ROOT, 'personas'), origin: 'global' },
-      { root: join(homeDir, '.goodvibes', 'agents'), origin: 'global' },
     ],
-    markers: ['PERSONA.md', 'persona.md', 'AGENT.md', 'agent.md'],
+    markers: ['PERSONA.md', 'persona.md'],
     frontmatterBodyKey: 'system_prompt',
   };
   const skills: DiscoveryKindDefinition = {

package/src/agent/persona-discovery.ts

@@ -14,7 +14,7 @@ export interface DiscoveredPersonaRecord {
   readonly frontmatter: Record<string, string>;
 }
 
-const DIRECTORY_MARKERS: readonly string[] = ['PERSONA.md', 'persona.md', 'AGENT.md', 'agent.md'];
+const DIRECTORY_MARKERS: readonly string[] = ['PERSONA.md', 'persona.md'];
 
 function parseFrontmatter(content: string): Record<string, string> {
   const match = content.match(/^---\n([\s\S]*?)\n---/);
@@ -33,10 +33,8 @@ function getPersonaDirectories(cwd: string, homeDir: string): Array<{ root: stri
   return [
     { root: join(cwd, '.goodvibes', 'personas'), origin: 'project-local' },
     { root: join(cwd, '.goodvibes', GOODVIBES_AGENT_SURFACE_ROOT, 'personas'), origin: 'project-local' },
-    { root: join(cwd, '.goodvibes', 'agents'), origin: 'project-local' },
     { root: join(homeDir, '.goodvibes', 'personas'), origin: 'global' },
     { root: join(homeDir, '.goodvibes', GOODVIBES_AGENT_SURFACE_ROOT, 'personas'), origin: 'global' },
-    { root: join(homeDir, '.goodvibes', 'agents'), origin: 'global' },
   ];
 }
 

package/src/agent/persona-registry.ts

@@ -158,14 +158,16 @@ function formatStore(store: PersonaStoreFile): string {
   return `${JSON.stringify(store, null, 2)}\n`;
 }
 
-export function personaStorePath(shellPaths: ShellPathService): string {
+type AgentLocalStorePaths = Pick<ShellPathService, 'resolveUserPath'>;
+
+export function personaStorePath(shellPaths: AgentLocalStorePaths): string {
   return shellPaths.resolveUserPath(GOODVIBES_AGENT_SURFACE_ROOT, 'personas', 'personas.json');
 }
 
 export class AgentPersonaRegistry {
   public constructor(private readonly storePath: string) {}
 
-  public static fromShellPaths(shellPaths: ShellPathService): AgentPersonaRegistry {
+  public static fromShellPaths(shellPaths: AgentLocalStorePaths): AgentPersonaRegistry {
     return new AgentPersonaRegistry(personaStorePath(shellPaths));
   }
 
@@ -374,6 +376,6 @@ export function buildActivePersonaPrompt(shellPaths: ShellPathService): string |
     '',
     active.body,
     '',
-    'Apply this persona inside the same serial assistant conversation. Do not spawn background agents because a persona is active.',
+    'Apply this persona inside the same serial assistant conversation. Do not launch local workers because a persona is active.',
   ].join('\n');
 }

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

@@ -33,7 +33,7 @@ export function formatReminderSchedulePreview(preview: ReminderSchedulePreview):
     `  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',
+    '  target: connected GoodVibes host/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');
@@ -57,19 +57,19 @@ export function formatReminderScheduleFailure(failure: ReminderScheduleFailure):
   return [
     `GoodVibes reminder schedule error: ${failure.kind}`,
     `  ${failure.error}`,
-    failure.baseUrl ? `  service: ${failure.baseUrl}` : null,
+    failure.baseUrl ? `  host: ${failure.baseUrl}` : null,
     `  route: ${REMINDER_SCHEDULE_METHOD} ${failure.route}`,
     failure.kind === 'version_mismatch' && failure.daemonVersion && failure.expectedSdkVersion
-      ? `  versions: service=${failure.daemonVersion} expected=${failure.expectedSdkVersion}`
+      ? `  versions: host=${failure.daemonVersion} expected=${failure.expectedSdkVersion}`
       : null,
     failure.kind === 'auth_required'
-      ? '  next: pair/authenticate with connected GoodVibes services, then retry with --yes.'
+      ? '  next: pair/authenticate with the connected GoodVibes host, then retry with --yes.'
       : null,
     failure.kind === 'daemon_unavailable'
-      ? '  next: make connected GoodVibes services available outside Agent, then retry.'
+      ? '  next: make the connected GoodVibes host 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.'
+      ? '  next: update the connected GoodVibes host so public schedules.create is available.'
       : null,
   ].filter((line): line is string => Boolean(line)).join('\n');
 }

package/src/agent/reminder-schedule.ts

@@ -468,7 +468,7 @@ export async function createReminderSchedule(
     return {
       ok: false,
       kind: 'auth_required',
-      error: `No daemon operator token found at ${connection.tokenPath}`,
+      error: `No connected-host operator token found at ${connection.tokenPath}`,
       route: REMINDER_SCHEDULE_ROUTE,
       baseUrl: connection.baseUrl,
     };

package/src/agent/routine-registry.ts

@@ -3,9 +3,18 @@ import { dirname } from 'node:path';
 import type { ShellPathService } from '@/runtime/index.ts';
 import { GOODVIBES_AGENT_SURFACE_ROOT } from '../config/surface.ts';
 import { assertNoSecretLikeText } from './persona-registry.ts';
+import {
+  evaluateAgentSkillReadiness,
+  formatAgentSkillRequirement,
+  normalizeAgentSkillRequirements,
+  type AgentSkillReadiness,
+  type AgentSkillRequirement,
+} from './skill-registry.ts';
 
 export type AgentRoutineSource = 'user' | 'agent' | 'imported' | 'system';
 export type AgentRoutineReviewState = 'fresh' | 'reviewed' | 'stale';
+export type AgentRoutineRequirement = AgentSkillRequirement;
+export type AgentRoutineReadiness = AgentSkillReadiness;
 
 export interface AgentRoutineRecord {
   readonly id: string;
@@ -14,6 +23,7 @@ export interface AgentRoutineRecord {
   readonly steps: string;
   readonly triggers: readonly string[];
   readonly tags: readonly string[];
+  readonly requirements: readonly AgentRoutineRequirement[];
   readonly enabled: boolean;
   readonly source: AgentRoutineSource;
   readonly provenance: string;
@@ -32,6 +42,7 @@ export interface AgentRoutineCreateInput {
   readonly steps: string;
   readonly triggers?: readonly string[];
   readonly tags?: readonly string[];
+  readonly requirements?: readonly AgentRoutineRequirement[];
   readonly enabled?: boolean;
   readonly source?: AgentRoutineSource;
   readonly provenance?: string;
@@ -43,6 +54,7 @@ export interface AgentRoutineUpdateInput {
   readonly steps?: string;
   readonly triggers?: readonly string[];
   readonly tags?: readonly string[];
+  readonly requirements?: readonly AgentRoutineRequirement[];
   readonly provenance?: string;
 }
 
@@ -72,6 +84,18 @@ function readStringArray(value: unknown): string[] {
   return value.filter((entry): entry is string => typeof entry === 'string').map((entry) => entry.trim()).filter(Boolean);
 }
 
+function readRequirementArray(value: unknown): readonly AgentRoutineRequirement[] {
+  if (!Array.isArray(value)) return [];
+  const requirements = value
+    .filter(isRecord)
+    .map((entry) => ({
+      kind: entry.kind === 'command' ? 'command' as const : 'env' as const,
+      name: readString(entry.name).trim(),
+      description: readString(entry.description).trim() || undefined,
+    }));
+  return normalizeAgentSkillRequirements(requirements);
+}
+
 function readNonNegativeInteger(value: unknown): number {
   const parsed = typeof value === 'number' ? value : Number(value);
   return Number.isInteger(parsed) && parsed > 0 ? parsed : 0;
@@ -123,6 +147,7 @@ function parseRoutine(value: unknown): AgentRoutineRecord | null {
     steps,
     triggers: readStringArray(value.triggers),
     tags: readStringArray(value.tags),
+    requirements: readRequirementArray(value.requirements),
     enabled: value.enabled === true,
     source,
     provenance: readString(value.provenance, source).trim() || source,
@@ -151,14 +176,16 @@ function formatStore(store: RoutineStoreFile): string {
   return `${JSON.stringify(store, null, 2)}\n`;
 }
 
-export function routineStorePath(shellPaths: ShellPathService): string {
+type AgentLocalStorePaths = Pick<ShellPathService, 'resolveUserPath'>;
+
+export function routineStorePath(shellPaths: AgentLocalStorePaths): string {
   return shellPaths.resolveUserPath(GOODVIBES_AGENT_SURFACE_ROOT, 'routines', 'routines.json');
 }
 
 export class AgentRoutineRegistry {
   public constructor(private readonly storePath: string) {}
 
-  public static fromShellPaths(shellPaths: ShellPathService): AgentRoutineRegistry {
+  public static fromShellPaths(shellPaths: AgentLocalStorePaths): AgentRoutineRegistry {
     return new AgentRoutineRegistry(routineStorePath(shellPaths));
   }
 
@@ -200,7 +227,8 @@ export class AgentRoutineRegistry {
     const description = input.description.trim();
     const steps = input.steps.trim();
     this.validateRequired(name, description, steps);
-    assertNoSecretLikeText([name, description, steps, ...(input.tags ?? []), ...(input.triggers ?? [])]);
+    const requirements = normalizeAgentSkillRequirements(input.requirements);
+    assertNoSecretLikeText([name, description, steps, ...(input.tags ?? []), ...(input.triggers ?? []), ...requirements.flatMap((requirement) => [requirement.name, requirement.description ?? ''])]);
     const duplicate = store.routines.find((routine) => routine.name.toLowerCase() === name.toLowerCase());
     if (duplicate) throw new Error(`Routine already exists: ${duplicate.id}`);
     const timestamp = nowIso();
@@ -211,6 +239,7 @@ export class AgentRoutineRegistry {
       steps,
       triggers: normalizeList(input.triggers),
       tags: normalizeList(input.tags),
+      requirements,
       enabled: input.enabled === true,
       source: input.source ?? 'user',
       provenance: input.provenance?.trim() || input.source || 'user',
@@ -231,7 +260,8 @@ export class AgentRoutineRegistry {
     const description = input.description === undefined ? existing.description : input.description.trim();
     const steps = input.steps === undefined ? existing.steps : input.steps.trim();
     this.validateRequired(name, description, steps);
-    assertNoSecretLikeText([name, description, steps, ...(input.tags ?? []), ...(input.triggers ?? [])]);
+    const requirements = input.requirements === undefined ? existing.requirements : normalizeAgentSkillRequirements(input.requirements);
+    assertNoSecretLikeText([name, description, steps, ...(input.tags ?? []), ...(input.triggers ?? []), ...requirements.flatMap((requirement) => [requirement.name, requirement.description ?? ''])]);
     const duplicate = store.routines.find((routine) => routine.id !== existing.id && routine.name.toLowerCase() === name.toLowerCase());
     if (duplicate) throw new Error(`Routine already exists: ${duplicate.id}`);
     const updated: AgentRoutineRecord = {
@@ -241,6 +271,7 @@ export class AgentRoutineRegistry {
       steps,
       triggers: input.triggers === undefined ? existing.triggers : normalizeList(input.triggers),
       tags: input.tags === undefined ? existing.tags : normalizeList(input.tags),
+      requirements,
       provenance: input.provenance === undefined ? existing.provenance : input.provenance.trim() || existing.provenance,
       reviewState: 'fresh',
       staleReason: undefined,
@@ -370,6 +401,13 @@ export class AgentRoutineRegistry {
   }
 }
 
+export function evaluateAgentRoutineReadiness(
+  routine: Pick<AgentRoutineRecord, 'requirements'>,
+  options: Parameters<typeof evaluateAgentSkillReadiness>[1] = {},
+): AgentRoutineReadiness {
+  return evaluateAgentSkillReadiness(routine, options);
+}
+
 export function buildEnabledRoutinesPrompt(shellPaths: ShellPathService): string | null {
   const enabled = AgentRoutineRegistry.fromShellPaths(shellPaths).snapshot().enabledRoutines;
   if (enabled.length === 0) return null;
@@ -382,6 +420,7 @@ export function buildEnabledRoutinesPrompt(shellPaths: ShellPathService): string
       `Description: ${routine.description}`,
       `Review state: ${routine.reviewState}`,
       `Triggers: ${routine.triggers.join(', ') || '(manual)'}`,
+      `Readiness: ${evaluateAgentRoutineReadiness(routine).ready ? 'ready' : `missing ${evaluateAgentRoutineReadiness(routine).missing.map(formatAgentSkillRequirement).join(', ')}`}`,
       routine.steps,
       '',
     ]),

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

@@ -111,13 +111,13 @@ export function formatRoutineScheduleCorrelation(result: RoutineScheduleCorrelat
       result.baseUrl ? `  runtime: ${result.baseUrl}` : null,
       `  route: ${ROUTINE_SCHEDULE_LIST_METHOD} ${result.route}`,
       result.kind === 'auth_required'
-        ? '  next: pair/authenticate with connected GoodVibes services, then retry.'
+        ? '  next: pair/authenticate with the connected GoodVibes host, then retry.'
         : null,
       result.kind === 'daemon_unavailable'
-        ? '  next: make connected GoodVibes services available outside Agent, then retry.'
+        ? '  next: make the connected GoodVibes host available outside Agent, then retry.'
         : null,
       result.kind === 'version_mismatch' || result.kind === 'daemon_route_unavailable'
-        ? '  next: update connected GoodVibes services so public schedules.list is available.'
+        ? '  next: update the connected GoodVibes host so public schedules.list is available.'
         : null,
     ].filter((line): line is string => Boolean(line)).join('\n');
   }
@@ -166,13 +166,13 @@ export function formatRoutineScheduleFailure(failure: RoutineSchedulePromotionFa
       ? `  versions: runtime=${failure.daemonVersion} expected=${failure.expectedSdkVersion}`
       : null,
     failure.kind === 'auth_required'
-      ? '  next: pair/authenticate with connected GoodVibes services, then retry with --yes.'
+      ? '  next: pair/authenticate with the connected GoodVibes host, then retry with --yes.'
       : null,
     failure.kind === 'daemon_unavailable'
-        ? '  next: make connected GoodVibes services available outside Agent, then retry.'
+        ? '  next: make the connected GoodVibes host 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.'
+      ? '  next: update the connected GoodVibes host so public schedules.create is available.'
       : null,
   ].filter((line): line is string => Boolean(line)).join('\n');
 }

package/src/agent/routine-schedule-promotion.ts

@@ -416,7 +416,7 @@ export async function promoteRoutineToDaemonSchedule(
     return {
       ok: false,
       kind: 'auth_required',
-      error: `No daemon operator token found at ${connection.tokenPath}`,
+      error: `No connected-host operator token found at ${connection.tokenPath}`,
       route: ROUTINE_SCHEDULE_ROUTE,
       baseUrl: connection.baseUrl,
     };