spur-board 0.8.2 → 0.9.0

package/dist/mcp.mjs

@@ -1,6 +1,6 @@
-import { j as ERRORS, s as OPERATIONS, u as renderMcpError } from "./src-g7u1onIP.mjs";
-import { i as CliError, n as requestOperation } from "./client-D4cveOHQ.mjs";
-import { a as memoryVerdictCache, r as compareCatalogs, s as loadClientConfig, t as checkCatalog } from "./config-B1fVOLzp.mjs";
+import { N as ERRORS, f as renderMcpError, l as OPERATIONS } from "./src-C-NNf__4.mjs";
+import { i as CliError, n as requestOperation } from "./client-Co0Pogjy.mjs";
+import { a as memoryVerdictCache, r as compareCatalogs, s as loadClientConfig, t as checkCatalog } from "./config-DL_Tm7un.mjs";
 import { randomUUID } from "node:crypto";
 import { readFileSync } from "node:fs";
 import { z } from "zod";

package/dist/{src-g7u1onIP.mjs → src-C-NNf__4.mjs}

@@ -2696,4 +2696,22 @@ var AdapterError = class extends Error {
 	}
 };
 //#endregion
-export { taskKeySchema as A, requiredSecretKeys as B, sessionFactsSchema as C, errorCodeOf as D, encodeActorId as E, DEFAULT_HTTP_PORT as F, DEFAULT_SLACK_APP_NAME as I, DEFAULT_SLACK_COMMAND as L, errorContextSchema as M, errorEnvelopeSchema as N, parseActorId as O, successEnvelopeSchema as P, RESERVED_PROJECT as R, prRefSchema as S, actorIdSchema as T, SLACK_BOT_SCOPES as V, EVENT_KINDS as _, buildCatalogSnapshot as a, SESSION_STATUSES as b, renderHttpProblem as c, SPACE_IDS as d, conversationRefSchema as f, userIdSchema as g, messageRefSchema as h, sourceCursorSchema as i, ERRORS as j, parseRef as k, renderJsonError as l, interactionRefSchema as m, batchSchema as n, roleCanUseOperation as o, inboundEventSchema as p, entityRefSchema as r, OPERATIONS as s, AdapterError as t, renderMcpError as u, eventPayloadSchemas as v, ticketFactsSchema as w, prFactsSchema as x, SESSION_HEALTH_STATES as y, configSchema as z };
+//#region ../contracts/src/systemd.ts
+/**
+* systemd user-unit policy shared by the CLI unit writer and the daemon's board tick.
+*
+* The daemon notifies systemd by spawning `systemd-notify`, so the notifying process is a child
+* of the main PID: the unit needs `NotifyAccess=all`. `WATCHDOG_MS` is three board ticks, so a
+* single slow or failed tick does not restart the daemon.
+*/
+const BOARD_TICK_MS = 6e4;
+const SYSTEMD_SERVICE_SETTINGS = [
+	"Type=notify",
+	"NotifyAccess=all",
+	`WatchdogSec=${String(3 * BOARD_TICK_MS)}ms`,
+	"Restart=on-failure",
+	"RestartSec=5s",
+	"TimeoutStopSec=15s"
+];
+//#endregion
+export { parseActorId as A, RESERVED_PROJECT as B, prFactsSchema as C, actorIdSchema as D, ticketFactsSchema as E, errorEnvelopeSchema as F, requiredSecretKeys as H, successEnvelopeSchema as I, DEFAULT_HTTP_PORT as L, taskKeySchema as M, ERRORS as N, encodeActorId as O, errorContextSchema as P, DEFAULT_SLACK_APP_NAME as R, SESSION_STATUSES as S, sessionFactsSchema as T, SLACK_BOT_SCOPES as U, configSchema as V, messageRefSchema as _, entityRefSchema as a, eventPayloadSchemas as b, roleCanUseOperation as c, renderJsonError as d, renderMcpError as f, interactionRefSchema as g, inboundEventSchema as h, batchSchema as i, parseRef as j, errorCodeOf as k, OPERATIONS as l, conversationRefSchema as m, SYSTEMD_SERVICE_SETTINGS as n, sourceCursorSchema as o, SPACE_IDS as p, AdapterError as r, buildCatalogSnapshot as s, BOARD_TICK_MS as t, renderHttpProblem as u, userIdSchema as v, prRefSchema as w, SESSION_HEALTH_STATES as x, EVENT_KINDS as y, DEFAULT_SLACK_COMMAND as z };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spur-board",
-  "version": "0.8.2",
+  "version": "0.9.0",
   "license": "MIT",
   "engines": {
     "node": "^24.12.0 || ^26.0.0"

package/skills/setup/references/update.md

@@ -6,6 +6,6 @@ Use this when the installed package is older than the intended release. Keep com
 2. Install the newer package with the Node and user prefix visible to live Spur sessions. Verify `board --version` there. Do not reinstall a matching package.
 3. If skills are older, ask before writing agent skill folders, run `board skills install`, and verify both installed copies. Record the install time so older live sessions can be identified.
    For a local same-version trial, compare packed and installed bytes too; a matching stamp can hide old content.
-4. Compare the unit's absolute Node and daemon paths with the newly selected Node and installed package. If either path changed, run the new package's `board service install`; it rewrites the unit, reloads systemd, and restarts an active service. If paths are unchanged but the daemon version changed, run `board service restart`. Do not restart twice or restart an unchanged service.
+4. Before installing, note whether `board service status` reports `active` as `active`. Then run the new package's `board service install`: it rewrites the unit only when it differs, reloads systemd, starts a stopped service, and restarts an active service only when the unit changed. Run `board service restart` only when the service was active before install, install reported `changed` as `false`, and the daemon version changed. Do not restart twice or restart an unchanged service.
 5. Run `board doctor --json` until no blocking check remains. Report live sessions that still use the older skill and ask the operator to restart those sessions. Do not assume an existing agent or MCP process reloaded updated files.
 6. Never rewrite settled config, reissue an operator token, uninstall the service, or revoke a token as part of an update.