@stravica-ai/digital-operator-pa 0.1.51 → 0.1.52

package/dist/engineering-pa-cli/src/pa/work-cli.mjs

@@ -36,6 +36,11 @@ Usage:
 
 Notes:
   - status=done stamps \`completedAt\` to today (only if not already set).
+  - \`list\` defaults to the active-only scope (excludes done + archived).
+    An explicit \`--status <s>\` REPLACES that default and returns only
+    items with that status (so \`--status done\` prints done items).
+    \`--all\` means no status filter; \`--mine\`/\`--theirs\` compose with
+    either. \`--status\` wins over \`--all\` when both are given.
   - --mine resolves the PA name from operator/config/preferences.json
     (paName / agentName). Default: "pa".
   - --author sets the writer-scoped id's author token. Precedence:

package/dist/engineering-pa-cli/src/pa/work.mjs

@@ -228,6 +228,15 @@ export async function setWorkStatus(id, status) {
  * mine, theirs, all, paName (used for --mine resolution).
  * By default excludes done + archived (mirrors desk-list semantics).
  *
+ * An explicit `status` filter REPLACES the active-only default rather
+ * than being AND-ed with it: `--status done` returns only done items,
+ * `--status archived` returns only archived items, `--status in-progress`
+ * is unchanged (the AND was harmless for non-terminal statuses). The
+ * pre-0.1.52 AND made any terminal-status request unconditionally
+ * empty ("no work items match" for `--status done`), a confident false
+ * negative. `--all` still means "no status filter at all"; if both
+ * `--all` and `--status` are given, `--status` wins.
+ *
  * Reads any well-formed work item (both id forms). Skips files whose
  * filename does not parse as a work-item id at all — the same
  * skip-unparseable posture the original had, restated against the
@@ -248,10 +257,11 @@ export async function listWork(filters = {}) {
     }
   }
   let filtered = items;
-  if (!filters.all) {
+  if (filters.status) {
+    filtered = filtered.filter((w) => w.status === filters.status);
+  } else if (!filters.all) {
     filtered = filtered.filter((w) => !['done', 'archived'].includes(w.status));
   }
-  if (filters.status) filtered = filtered.filter((w) => w.status === filters.status);
   if (filters.category) filtered = filtered.filter((w) => w.category === filters.category);
   if (filters.project) filtered = filtered.filter((w) => w.projectId === filters.project);
   if (filters.owner) filtered = filtered.filter((w) => w.owner === filters.owner);

package/dist/engineering-pa-cli/src/scheduler/cli.mjs

@@ -33,10 +33,14 @@ Usage:
 Schedule files live at <repoRoot>/schedules/<id>.json. The canonical
 schema is bundled at @stravica-ai/engineering-pa-core/schema/schedule.json.
 
---agent (launchd only) targets a specific agent's label prefix
-(com.<agent>.<id>). A schedule file's own top-level "agent" field drives
-install; list/remove take it explicitly since they don't read a schedule
-file. Defaults to "dave" everywhere — omitting it is unchanged behaviour.
+--agent targets a specific agent's label / tag prefix. Install reads
+the agent from the schedule file's own top-level "agent" field. Since
+0.1.52 (w-2026-09-19-dave-001), list/remove resolve the agent from the
+invoking instance's "paName" in operator/config/preferences.json when
+--agent is omitted, and REFUSE (exit 2) when neither source produces a
+value — there is no hard-coded "dave" fallback. This is the fix for the
+colleague-laptop bug where the tools would list and touch another
+estate's schedules under a silent default.
 
 Host enforcement (install): a schedule's "host" field is matched against
 this machine's hostname (exact, then short-name-before-first-dot). A

package/dist/engineering-pa-cli/src/secrets/commands/init.mjs

@@ -85,7 +85,41 @@ function parseStdinJson(raw) {
 }
 
 export async function runInit(overrides = {}) {
-  const paths = overrides.paths || defaultPaths({ ...overrides, allowGitRootWithoutVault: true });
+  // 0.1.52 fix (w-2026-09-19-dave-001): `secrets init` CREATES an age
+  // key. The shared resolver in core/vault/require.mjs honours
+  // SOPS_AGE_KEY_FILE first, so with the variable exported the previous
+  // init generated the new key AT the env path — a stray key landed
+  // outside the instance, and on a colleague laptop that carried
+  // another estate's SOPS_AGE_KEY_FILE it would have written the new
+  // key into that estate's key file. The env override is a READ-path
+  // escape hatch; init must generate at the instance path (solo mode)
+  // or the per-user path (HQ mode) regardless of the variable.
+  //
+  // Strip SOPS_AGE_KEY_FILE from the env passed to `defaultPaths` only
+  // — every OTHER env-derived resolution (DAVE_ROOT / PA_ROOT walk,
+  // etc.) still uses the caller's real env. Print a one-line notice
+  // when the operator had the override set and the resolved
+  // key path does not match it, so subsequent reads that continue to
+  // consult the env override are not silently pointed at the old file.
+  const rawEnv = overrides.env;
+  const envOverride = rawEnv && typeof rawEnv.SOPS_AGE_KEY_FILE === 'string' && rawEnv.SOPS_AGE_KEY_FILE.length > 0
+    ? rawEnv.SOPS_AGE_KEY_FILE
+    : null;
+  let envForPaths = rawEnv;
+  if (envOverride !== null && !overrides.paths) {
+    envForPaths = { ...rawEnv };
+    delete envForPaths.SOPS_AGE_KEY_FILE;
+  }
+  const paths = overrides.paths || defaultPaths({
+    ...overrides,
+    env: envForPaths,
+    allowGitRootWithoutVault: true,
+  });
+  if (envOverride !== null && envOverride !== paths.keyFile) {
+    console.log(
+      `Note: SOPS_AGE_KEY_FILE is set to ${envOverride}; init writes the new key to ${paths.keyFile}. Reads will not see the new key until the variable is unset or repointed.`,
+    );
+  }
   const argv = overrides.argv || [];
   const flags = extractInitFlags(argv);
 

package/dist/engineering-pa-core/docs/commands/onboard.md

@@ -207,10 +207,12 @@ Otherwise, tell the operator what is happening in one short paragraph:
 
 > Standing up your instance's own SOPS+age vault. This is what
 > credentialed tools read their keys from. The vault lives in
-> `.vault/`, the age private key lives in
-> `~/.config/stravica-pa/age-key.txt` (never committed), and the
-> encrypted store is safe to commit. Values you enter here never leave
-> your laptop.
+> `.vault/`, the age private key lives inside the instance at
+> `.vault/age-key.txt` (never committed), and the encrypted store is
+> safe to commit. Values you enter here never leave your laptop.
+> HQ-mode instances keep a per-user key at
+> `~/.config/stravica-pa/age-key.txt` instead (shared across the
+> estate's canonical clones).
 
 Ask, in one turn, for the values the enabled tools declare. For the
 default atlassian install:

package/dist/engineering-pa-core/src/scheduler/install.mjs

@@ -562,7 +562,7 @@ function validateLaunchdDaveRoot(value) {
       + '(DAVE_ROOT unset at install time, falling back to the installed '
       + 'package\'s own directory, which is version-pinned and silently breaks '
       + 'on the next upgrade or package rename). Set DAVE_ROOT explicitly in '
-      + 'the shell running `pa scheduler install`, or set the schedule\'s '
+      + 'the shell running `pnpm exec scheduler install`, or set the schedule\'s '
       + 'environment.DAVE_ROOT to the real operator repo root.',
     );
     e.exitCode = 2;

package/dist/engineering-pa-core/src/scheduler/list.mjs

@@ -1,11 +1,21 @@
 #!/usr/bin/env node
 /**
- * list.mjs -- List all Dave-managed scheduled tasks for a given backend
+ * list.mjs -- List scheduled tasks belonging to the invoking instance
  *
  * Usage: node node_modules/@stravica-ai/engineering-pa-core/src/scheduler/list.mjs [backend]
  *
  * Backends: cron, launchd, systemd, schtasks
  * If no backend is specified, auto-detects and uses the first recommended.
+ *
+ * Agent-name resolution (0.1.52, w-2026-09-19-dave-001): the header,
+ * launchd label prefix, cron tag, systemd unit prefix, and schtasks
+ * name filter ALL derive from the invoking instance's `paName`
+ * (operator/config/preferences.json), or an explicit `--agent`
+ * override. There is no hard-coded fallback: a laptop that carries
+ * another estate's schedules would previously see them listed under
+ * this instance's `dave` default, and a subsequent `scheduler remove`
+ * would touch the wrong estate's plists. See ./resolve-agent.mjs for
+ * the resolution order and the escalation on failure.
  */
 
 import { readdirSync, readFileSync, existsSync, realpathSync } from 'node:fs';
@@ -15,54 +25,57 @@ import { execSync } from 'node:child_process';
 import { fileURLToPath } from 'node:url';
 import { detect } from './detect.mjs';
 import { launchdLabelPrefix } from './install.mjs';
+import { resolveAgent } from './resolve-agent.mjs';
 
 /**
- * Render the leading name for the listing header. Uses the agent id when
- * one is supplied, else a generic label so instances without an agent id
- * (rare, but possible for pre-scaffold flows) still get a sensible line.
- *
- * Tag prefixes on the crontab / launchd / systemd / schtasks side are NOT
- * renamed here \u2014 those are load-bearing for removal on existing installs
- * (they are still `dave-` for backward compat).
+ * Render the leading name for the listing header. Uses the resolved
+ * agent name so both the header and the label prefix agree on which
+ * estate is being reported.
  *
- * @param {string} [agent]
+ * @param {string} agent
  * @returns {string}
  */
 function headerName(agent) {
-  if (typeof agent === 'string' && agent.length > 0) return agent;
-  return 'Schedules';
+  return agent;
 }
 
 /**
  * List schedules for a given backend.
  * @param {string} backend - Backend name (cron, launchd, systemd, schtasks)
  * @param {object} [opts]
- * @param {string} [opts.agent] - The agent id used for the header AND, on
- *   launchd, the label prefix to filter by. Defaults to 'dave' for the
- *   launchd label prefix (unchanged pre-feature behaviour); header defaults
- *   to 'Schedules' when omitted.
+ * @param {string} [opts.agent] Explicit agent override. Falls back to
+ *   the invoking instance's `paName` (see ./resolve-agent.mjs).
+ * @param {string} [opts.repoRoot] Optional instance root override
+ *   (tests inject; production callers omit this).
  * @returns {string} Human-readable listing
  */
 export function list(backend, opts = {}) {
-  const agent = opts.agent;
+  // Validate the backend BEFORE resolving the agent name: an unknown
+  // backend is a usage error and needs to surface as "Unknown backend:
+  // <x>" regardless of whether the caller has a paName resolvable on
+  // this host. The prior ordering (agent first) turned a usage-shaped
+  // failure into a scheduler-config-shaped one, hiding the real cause.
+  if (backend !== 'cron' && backend !== 'launchd' && backend !== 'systemd' && backend !== 'schtasks') {
+    throw new Error(`Unknown backend: ${backend}`);
+  }
+  const { agent } = resolveAgent({ agent: opts.agent, repoRoot: opts.repoRoot });
   switch (backend) {
     case 'cron':     return listCron(agent);
     case 'launchd':  return listLaunchd(agent);
     case 'systemd':  return listSystemd(agent);
     case 'schtasks': return listSchtasks(agent);
-    default:
-      throw new Error(`Unknown backend: ${backend}`);
   }
 }
 
 function listCron(agent) {
-  const lines = [`${headerName(agent)} schedules (cron):`, '\u2500'.repeat(37)];
+  const lines = [`${headerName(agent)} schedules (cron):`, '─'.repeat(37)];
   let found = false;
+  const tag = `# ${agent}-`;
 
   try {
     const crontab = execSync('crontab -l 2>/dev/null', { encoding: 'utf8' });
     for (const line of crontab.split('\n')) {
-      if (line.includes('# dave-')) {
+      if (line.includes(tag)) {
         lines.push(`  ${line}`);
         found = true;
       }
@@ -76,7 +89,7 @@ function listCron(agent) {
 }
 
 function listLaunchd(agent) {
-  const lines = [`${headerName(agent)} schedules (launchd):`, '\u2500'.repeat(37)];
+  const lines = [`${headerName(agent)} schedules (launchd):`, '─'.repeat(37)];
   let found = false;
 
   const prefix = launchdLabelPrefix(agent);
@@ -104,13 +117,14 @@ function listLaunchd(agent) {
 }
 
 function listSystemd(agent) {
-  const lines = [`${headerName(agent)} schedules (systemd):`, '\u2500'.repeat(37)];
+  const lines = [`${headerName(agent)} schedules (systemd):`, '─'.repeat(37)];
   let found = false;
+  const tag = `${agent}-`;
 
   try {
     const output = execSync('systemctl --user list-timers --no-pager', { encoding: 'utf8' });
     for (const line of output.split('\n')) {
-      if (line.includes('dave-')) {
+      if (line.includes(tag)) {
         lines.push(`  ${line}`);
         found = true;
       }
@@ -124,13 +138,14 @@ function listSystemd(agent) {
 }
 
 function listSchtasks(agent) {
-  const lines = [`${headerName(agent)} schedules (schtasks):`, '\u2500'.repeat(37)];
+  const lines = [`${headerName(agent)} schedules (schtasks):`, '─'.repeat(37)];
   let found = false;
+  const tag = `${agent}-`;
 
   try {
     const output = execSync('schtasks.exe /Query /FO LIST', { encoding: 'utf8' });
     for (const line of output.split('\n')) {
-      if (line.includes('dave-')) {
+      if (line.includes(tag)) {
         lines.push(`  ${line}`);
         found = true;
       }
@@ -184,6 +199,6 @@ if (isDirectlyInvoked()) {
     console.log(list(backend));
   } catch (err) {
     console.error(`Error: ${err.message}`);
-    process.exit(1);
+    process.exit(err.exitCode || 1);
   }
 }

package/dist/engineering-pa-core/src/scheduler/remove.mjs

@@ -1,12 +1,21 @@
 #!/usr/bin/env node
 /**
- * remove.mjs -- Remove a Dave-managed scheduled task
+ * remove.mjs -- Remove a scheduled task belonging to the invoking instance
  *
  * Usage: node node_modules/@stravica-ai/engineering-pa-core/src/scheduler/remove.mjs <schedule-id> <backend> [--delete-file]
  *
  * Removes the scheduled task identified by <schedule-id> from the
  * specified backend. Also removes the schedule JSON from schedules/
  * if --delete-file is passed.
+ *
+ * Agent-name resolution (0.1.52, w-2026-09-19-dave-001): the launchd
+ * label, cron tag, systemd unit, and schtasks name ALL derive from
+ * the invoking instance's `paName` (operator/config/preferences.json)
+ * or an explicit `--agent` override. Pre-0.1.52 defaulted to the
+ * literal `"dave"`, which on a laptop carrying another estate's
+ * schedules would unload/delete THAT estate's plists. There is no
+ * hard-coded fallback now — refusal is the safe behaviour when
+ * neither source resolves a name. See ./resolve-agent.mjs.
  */
 
 import { existsSync, unlinkSync, realpathSync } from 'node:fs';
@@ -16,19 +25,20 @@ import { execSync } from 'node:child_process';
 import { fileURLToPath } from 'node:url';
 import { launchdLabelPrefix } from './install.mjs';
 import { findRepoRootSync } from '../instance-root/find.mjs';
+import { resolveAgent } from './resolve-agent.mjs';
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 
 // ── Backend removal functions ────────────────────────────────────────
 
-function removeCron(schedId) {
-  const tag = `# dave-${schedId}`;
+function removeCron(schedId, agent) {
+  const tag = `# ${agent}-${schedId}`;
   let existing = '';
   try {
     existing = execSync('crontab -l 2>/dev/null', { encoding: 'utf8' });
   } catch {
-    console.log(`No cron entry found for dave-${schedId}`);
+    console.log(`No cron entry found for ${agent}-${schedId}`);
     return;
   }
 
@@ -36,7 +46,7 @@ function removeCron(schedId) {
   const filtered = lines.filter(line => !line.includes(tag)).join('\n').replace(/^\n+|\n+$/g, '');
 
   if (filtered === existing.replace(/^\n+|\n+$/g, '')) {
-    console.log(`No cron entry found for dave-${schedId}`);
+    console.log(`No cron entry found for ${agent}-${schedId}`);
     return;
   }
 
@@ -46,7 +56,7 @@ function removeCron(schedId) {
     try { execSync('crontab -r', { stdio: 'pipe' }); } catch { /* already empty */ }
   }
 
-  console.log(`Removed cron schedule: dave-${schedId}`);
+  console.log(`Removed cron schedule: ${agent}-${schedId}`);
 }
 
 function removeLaunchd(schedId, agent) {
@@ -68,8 +78,8 @@ function removeLaunchd(schedId, agent) {
   }
 }
 
-function removeSystemd(schedId) {
-  const unitName = `dave-${schedId}`;
+function removeSystemd(schedId, agent) {
+  const unitName = `${agent}-${schedId}`;
   const unitDir = join(homedir(), '.config', 'systemd', 'user');
 
   // Stop and disable
@@ -95,8 +105,8 @@ function removeSystemd(schedId) {
   }
 }
 
-function removeSchtasks(schedId) {
-  const taskName = `dave-${schedId}`;
+function removeSchtasks(schedId, agent) {
+  const taskName = `${agent}-${schedId}`;
   try {
     execSync(`schtasks.exe /Delete /TN "${taskName}" /F`, { stdio: 'pipe' });
     console.log(`Removed schtasks schedule: ${taskName}`);
@@ -108,30 +118,41 @@ function removeSchtasks(schedId) {
 // ── Main ─────────────────────────────────────────────────────────────
 
 /**
- * Remove a Dave-managed schedule from the specified backend.
+ * Remove a schedule from the specified backend for the invoking
+ * instance (or an explicit `--agent` override).
  *
  * Same BUG-2-class fix as install(): this used to have no return
  * statement, so the CLI wrapper's `result.ok` check was reading
  * `undefined.ok`. Every path now returns a result object.
+ *
  * @param {string} schedId - Schedule identifier
  * @param {string} backend - Backend name (cron, launchd, systemd, schtasks)
  * @param {object} [options]
  * @param {boolean} [options.deleteFile=false] - Also delete the schedule JSON file
- * @param {string} [options.agent] - Agent whose launchd label prefix to target (launchd only). Defaults to 'dave'.
- * @returns {{ ok: boolean, id: string, backend: string }}
+ * @param {string} [options.agent] - Explicit agent override. Falls
+ *   back to the invoking instance's `paName` from preferences.json.
+ * @param {string} [options.repoRoot] - Optional instance root override
+ *   (tests inject; production callers omit this).
+ * @returns {{ ok: boolean, id: string, backend: string, agent: string }}
  */
 export function remove(schedId, backend, options = {}) {
+  // See list.mjs for the same ordering rationale: backend validation
+  // must run BEFORE agent resolution so an unknown backend is a
+  // usage-shaped error, not a scheduler-config-shaped one.
+  if (backend !== 'cron' && backend !== 'launchd' && backend !== 'systemd' && backend !== 'schtasks') {
+    throw new Error(`Unknown backend: ${backend}. Supported: cron, launchd, systemd, schtasks`);
+  }
+  const { agent } = resolveAgent({ agent: options.agent, repoRoot: options.repoRoot });
+
   switch (backend) {
-    case 'cron':     removeCron(schedId); break;
-    case 'launchd':  removeLaunchd(schedId, options.agent); break;
-    case 'systemd':  removeSystemd(schedId); break;
-    case 'schtasks': removeSchtasks(schedId); break;
-    default:
-      throw new Error(`Unknown backend: ${backend}. Supported: cron, launchd, systemd, schtasks`);
+    case 'cron':     removeCron(schedId, agent); break;
+    case 'launchd':  removeLaunchd(schedId, agent); break;
+    case 'systemd':  removeSystemd(schedId, agent); break;
+    case 'schtasks': removeSchtasks(schedId, agent); break;
   }
 
   if (options.deleteFile) {
-    const daveRoot = process.env.DAVE_ROOT || process.env.PA_ROOT || findRepoRootSync();
+    const daveRoot = process.env.DAVE_ROOT || process.env.PA_ROOT || options.repoRoot || findRepoRootSync();
     const schedFile = join(daveRoot, 'schedules', `${schedId}.json`);
     if (existsSync(schedFile)) {
       unlinkSync(schedFile);
@@ -139,7 +160,7 @@ export function remove(schedId, backend, options = {}) {
     }
   }
 
-  return { ok: true, id: schedId, backend };
+  return { ok: true, id: schedId, backend, agent };
 }
 
 // ── CLI entry point ──────────────────────────────────────────────────
@@ -172,6 +193,6 @@ if (isDirectlyInvoked()) {
     remove(positional[0], positional[1], { deleteFile });
   } catch (err) {
     console.error(`Error: ${err.message}`);
-    process.exit(1);
+    process.exit(err.exitCode || 1);
   }
 }

package/dist/engineering-pa-core/src/scheduler/resolve-agent.mjs

@@ -0,0 +1,56 @@
+// resolve-agent.mjs — shared agent-name resolution for list + remove.
+//
+// Pre-0.1.52, `scheduler list` and `scheduler remove` defaulted the
+// launchd label prefix (and the cron / systemd / schtasks tag prefix)
+// to the literal string `"dave"`. On a laptop that carried more than
+// one estate — the exact shape a colleague-hosted "demo then delete"
+// solo instance sits beside another estate — this made the tools list
+// and touch schedules belonging to OTHER estates. `install` had never
+// had that problem because it reads the label from the schedule file's
+// own `agent` field. `list` / `remove` have no schedule file at hand,
+// so this helper resolves the invoking instance's `paName` from
+// `operator/config/preferences.json` — the same source `install` and
+// the 0.1.50 workspace header already use.
+//
+// Resolution order:
+//   1. explicit `--agent <name>` override (unchanged);
+//   2. `paName` from the invoking instance's preferences (base +
+//      overlay via `readPreferencesSync`);
+//   3. no fallback — refuse with a message naming the preferences key
+//      and the `--agent` escape hatch. There is deliberately NO hard-
+//      coded `dave` fallback: silently defaulting is what caused this
+//      bug in the first place.
+
+import { readPreferencesSync } from '../preferences.mjs';
+import { findRepoRootSync } from '../instance-root/find.mjs';
+
+/**
+ * Resolve the agent name to use for launchd label prefixing / cron /
+ * systemd / schtasks tag filtering.
+ *
+ * @param {object} [opts]
+ * @param {string} [opts.agent] Explicit override (from `--agent`).
+ * @param {string} [opts.repoRoot] Optional instance root override
+ *   (tests inject; defaults to `findRepoRootSync()`).
+ * @returns {{ agent: string, source: 'explicit'|'preferences' }}
+ * @throws {Error} exitCode:2 when neither source resolves a value.
+ */
+export function resolveAgent(opts = {}) {
+  if (typeof opts.agent === 'string' && opts.agent.length > 0) {
+    return { agent: opts.agent, source: 'explicit' };
+  }
+  const repoRoot = opts.repoRoot || findRepoRootSync();
+  const prefs = readPreferencesSync(repoRoot);
+  if (prefs && typeof prefs.paName === 'string' && prefs.paName.length > 0) {
+    return { agent: prefs.paName, source: 'preferences' };
+  }
+  const err = new Error(
+    'scheduler: cannot resolve agent name. Set `paName` in '
+    + 'operator/config/preferences.json for this instance, or pass '
+    + '`--agent <name>` explicitly. No hard-coded fallback is used '
+    + '(0.1.52, w-2026-09-19-dave-001): a silent default would target '
+    + 'schedules belonging to another estate.',
+  );
+  err.exitCode = 2;
+  throw err;
+}

package/dist/engineering-pa-workspace/src/api.mjs

@@ -294,7 +294,12 @@ export function handleApi(req, res, url, repoRoot, deps = {}) {
       }
       if (backend) {
         try {
-          liveStatus = String(scheduler.list(backend)).trim();
+          // Thread the workspace's known instance root through so the
+          // agent-name resolver reads THIS instance's preferences.json
+          // (paName) rather than walking up from process.cwd(). See
+          // core/src/scheduler/resolve-agent.mjs (0.1.52,
+          // w-2026-09-19-dave-001).
+          liveStatus = String(scheduler.list(backend, { repoRoot })).trim();
         } catch (err) {
           schedulerError = 'scheduler list failed for backend "' + backend + '": ' + (err && err.message ? err.message : String(err));
         }

package/docs/onboarding-solo.md

@@ -110,17 +110,44 @@ Your PA has the `rcf-lite-engineer` role baked in. It builds greenfield applicat
 
 ## Removing an instance
 
-Before you delete the instance directory, remove every schedule the instance installed on your operating system. Deleting the directory does not unload the launchd job (macOS) or cron entry (Linux) the scheduler registered; the loaded job then keeps firing against a path that no longer exists, and its errors turn up in the system log with no easy trace back to the retired instance.
+Do everything below from inside the instance, in this order. Deleting the instance directory does not stop the workspace server, does not unload the launchd job (macOS) or cron entry (Linux) the scheduler registered, and does not remove the age key. A loaded schedule keeps firing against a path that no longer exists, its errors turn up in the system log with no easy trace back to the retired instance, and a running workspace server keeps its port bound after its own `node_modules` has been deleted.
 
-Two steps:
+The steps are ordered so that a stop or listing that fails does not orphan a running background process. If you already deleted the instance directory before reading this, jump to the fallbacks in step 1.
 
-1. From inside the instance, list its installed schedules:
+1. Stop the workspace server.
    ```
-   pnpm exec pa scheduler list
+   pnpm exec pa workspace stop
    ```
-2. For each id the list reports, remove it:
+   The stop command reads the pid and port from `.ws.pid` at the instance root, sends SIGTERM, and waits up to 5s before force-killing. Confirm with `pnpm exec pa workspace status`. If the instance directory is already gone (so `pnpm exec` is no longer runnable), find the process by port and kill it directly:
    ```
-   pnpm exec pa scheduler remove <id> --delete-file
+   cat .ws.pid                        # if .ws.pid still exists: {"pid":<N>,"port":<P>}
+   lsof -i :<P> | grep LISTEN         # macOS/Linux: process holding the port
+   pgrep -lf digital-operator-pa-workspace   # match the server's spawn command
+   kill <pid>                         # SIGTERM; kill -9 <pid> if it refuses
    ```
+   The server responds to `GET /__api/identity` with `{"server":"digital-operator-pa-workspace","repoRoot":"...","pid":<N>,...}`, so `curl -s http://127.0.0.1:<port>/__api/identity` will identify a rogue workspace server (and name the instance directory it was started from) before you kill it.
 
-Only after `pa scheduler list` returns nothing is it safe to delete the instance directory.
+2. List every schedule the instance installed. Since 0.1.52 (w-2026-09-19-dave-001) the tool filters by this instance's `paName` from `operator/config/preferences.json`, so it only ever reports schedules that belong here:
+   ```
+   pnpm exec scheduler list
+   ```
+   The correct bin is `scheduler` (not `pa scheduler`; there is no `pa scheduler` subcommand). If the tool refuses because it cannot resolve a `paName`, pass `--agent <name>` explicitly.
+
+3. Remove every id the list reports. `--delete-file` also removes the schedule JSON:
+   ```
+   pnpm exec scheduler remove <id> --delete-file
+   ```
+   Repeat per id.
+
+4. Confirm nothing this instance registered is still loaded. On macOS, `launchctl list` and `crontab -l` should carry no entries with the `com.<paName>.` prefix respectively `# <paName>-` tag:
+   ```
+   launchctl list | grep "com.<paName>\."   # macOS
+   crontab -l | grep "# <paName>-"           # cron backend
+   systemctl --user list-timers | grep "<paName>-"   # linux/systemd
+   ```
+
+5. Only now delete the instance directory:
+   ```
+   rm -rf $HOME/<pa-name>-instance
+   ```
+   The age private key lives inside the instance at `.vault/age-key.txt` and goes with the directory. If you want a portable copy of the secrets first, run `pnpm exec secrets backup` from inside the instance BEFORE step 5.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stravica-ai/digital-operator-pa",
-  "version": "0.1.51",
+  "version": "0.1.52",
   "description": "Digital Operator PA — single-bundled public package surface (bins + library) for the platform.",
   "type": "module",
   "main": "./index.mjs",