@coreplane/switchboard 0.0.0 → 1.18.0

package/dist/assets/deploy/cloudflare/wrangler.template.jsonc

@@ -0,0 +1,67 @@
+{
+  "$schema": "node_modules/wrangler/config-schema.json",
+  "name": "{{script}}",
+  "main": "worker.ts",
+  "compatibility_date": "2026-08-01",
+  // The installation's Cloudflare account (deploy/profile.json `account`) — every Worker deploys to it.
+  "account_id": "{{account}}",
+  // Custom domain on the installation's zone (profile `zone`; the state,
+  // resident and sandbox Workers sit beside it). Slack traffic is the
+  // container's outbound websocket; the inbound HTTP surface here is the cron
+  // keep-alive + the authed ingress/MCP endpoints + the live-view dashboard
+  // (/runs). workers.dev is DISABLED: the /runs dashboard must sit behind
+  // Cloudflare Access (SSO), and Access can only front a real zone domain —
+  // leaving the workers.dev URL up would expose an un-SSO'd copy of /runs.
+  "workers_dev": false,
+  "routes": [{ "pattern": "{{hostname}}", "custom_domain": true }],
+  // Non-secret, deploy-constant config for the container. PUBLIC_BASE_URL: the
+  // live-view link base — the dispatcher (in the container) reads
+  // process.env.PUBLIC_BASE_URL to put the /runs/<id>?t=… link on the status
+  // card; worker.ts forwards it into envVars. ACCESS_*: the Cloudflare Access
+  // app this bot sits behind (profile `access`) — the app-layer gate
+  // (src/channels/accessAuth.ts) verifies the Cf-Access-Jwt-Assertion JWT
+  // against this team's keys and AUD, fail-closed, so /runs is denied without
+  // a valid Access identity. Neither ACCESS_ value is a secret (forging a JWT
+  // needs Cloudflare's private key, not these). A profile without `access`
+  // renders neither var, and the gate then treats Access as not configured:
+  // every dashboard request is denied.
+  "vars": {
+    "PUBLIC_BASE_URL": "{{urls.publicBaseUrl}}",
+    // {{#if access}}
+    "ACCESS_TEAM_DOMAIN": "{{access.teamDomain}}",
+    "ACCESS_AUD": "{{access.aud}}",
+    // {{/if}}
+    // The state Worker (deploy/cloudflare-memory/): where worker.ts records each
+    // scheduled firing for the /runs Scheduled panel, with MEMORY_TOKEN.
+    // A profile without a memory Worker renders no var: firings go unrecorded.
+    // {{#if urls.stateWorkerUrl}}
+    "STATE_WORKER_URL": "{{urls.stateWorkerUrl}}"
+    // {{/if}}
+  },
+  "observability": { "enabled": true, "traces": { "enabled": true } },
+  "containers": [
+    {
+      "class_name": "SwitchboardServer",
+      // The profile's image mode decides (src/deploy/images.ts): `build` renders
+      // ../../Dockerfile (the same image docker-compose uses), built by wrangler
+      // at deploy time; `registry` renders the release's published image as
+      // copied into this account's registry by `deploy images`.
+      "image": "{{image}}",
+      "instance_type": "basic",
+      "max_instances": 1
+    }
+  ],
+  "durable_objects": {
+    "bindings": [{ "name": "SWITCHBOARD", "class_name": "SwitchboardServer" }]
+  },
+  "migrations": [{ "tag": "v1", "new_sqlite_classes": ["SwitchboardServer"] }],
+  // Every cron here IS a schedule in src/core/schedules.ts (the registry; a unit
+  // test fails when the two sets differ) and worker.ts looks each firing up there.
+  // "* * * * *": keep-alive (/healthz) — also what RESTARTS the container after a
+  // deploy rollout, a `deploy restart` (POST /admin/restart → DO stop()), or
+  // platform maintenance; the interval bounds the deaf window
+  // (Socket Mode events during downtime are lost, never redelivered). Not a run.
+  // "0 14 * * 1": the weekly self-improvement pass — POST /ingress as the
+  // `cron` identity with `friction propose`; an ordinary run on /runs.
+  "triggers": { "crons": ["* * * * *", "0 14 * * 1"] }
+}

package/dist/assets/deploy/cloudflare/write-build.d.mts

@@ -0,0 +1,7 @@
+// Types for write-build.mjs (plain-Node ESM so the bot's `npm run deploy` needs
+// no build step). The file it writes is what `src/index.ts` reads as `BuildInfo`.
+export type BuildInfo = { commit: string; builtAt: string };
+export const COMMIT_ENV: "SWITCHBOARD_BUILD_COMMIT";
+export function buildInfo(input: { commit: string; dirty: boolean; now?: Date }): BuildInfo;
+export function readBuildInfo(env?: Record<string, string | undefined>, git?: (args: string[]) => string): BuildInfo;
+export function main(): number;

package/dist/assets/deploy/cloudflare/write-build.mjs

@@ -0,0 +1,53 @@
+#!/usr/bin/env node
+// Stamp the build identity into the bot image (docs/reference/specs/slack-channel.md item 8).
+//
+// `wrangler deploy` builds ../../Dockerfile from the CURRENT tree and exposes
+// no build args, so `npm run deploy` writes `<repo>/build.json` first and the
+// Dockerfile COPYs it (`COPY package.json build.jso[n] ./` — the glob makes the
+// file optional, so a bare `wrangler deploy` or docker-compose still builds and
+// the bot then reports `commit: "unknown"`). The bot reads it once at startup and
+// serves it on `GET /healthz` as `build: { commit, builtAt }`; `deploy:all`'s
+// live gate compares that commit to the one it deployed, so "deployed" is never
+// confused with "live". The file is gitignored: the tree stays clean.
+//
+// Dependency-free Node (child_process + fs). `buildInfo()` is pure given its
+// inputs; `main()` does the I/O.
+import { execFileSync } from "node:child_process";
+import { writeFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath, pathToFileURL } from "node:url";
+
+const REPO_ROOT = join(dirname(fileURLToPath(import.meta.url)), "..", "..");
+
+/** `{ commit, builtAt }` — `commit` gets a `-dirty` suffix when the tree has uncommitted changes. */
+export function buildInfo({ commit, dirty, now = new Date() }) {
+  return { commit: `${commit}${dirty ? "-dirty" : ""}`, builtAt: now.toISOString() };
+}
+
+/** The env var that names the commit when there is no tree to read — a deploy from the published npm
+ *  package (src/deploy/run.ts sets it; `../bin/build-stamp.mjs` reads the same variable). */
+export const COMMIT_ENV = "SWITCHBOARD_BUILD_COMMIT";
+
+/** The identity: the environment's commit when it names one (never `-dirty` — nothing was read from a tree), else git's. */
+export function readBuildInfo(
+  env = process.env,
+  git = (args) => execFileSync("git", args, { cwd: REPO_ROOT, encoding: "utf8" }).trim(),
+) {
+  const given = env[COMMIT_ENV]?.trim();
+  if (given) return buildInfo({ commit: given, dirty: false });
+  return buildInfo({ commit: git(["rev-parse", "HEAD"]), dirty: git(["status", "--porcelain"]) !== "" });
+}
+
+export function main() {
+  const info = readBuildInfo();
+  const path = join(REPO_ROOT, "build.json");
+  writeFileSync(path, `${JSON.stringify(info)}\n`);
+  console.log(`[build] ${path}: ${info.commit} @ ${info.builtAt}`);
+  return 0;
+}
+
+// Run only when executed directly (`node write-build.mjs`), not when imported.
+// pathToFileURL, not `file://${argv[1]}`, so the guard also holds on Windows paths.
+if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+  process.exitCode = main();
+}

package/dist/assets/deploy/cloudflare-docs/package.json

@@ -0,0 +1,18 @@
+{
+  "name": "switchboard-docs-worker",
+  "private": true,
+  "type": "module",
+  "engines": {
+    "node": ">=22"
+  },
+  "scripts": {
+    "build": "npm --prefix ../../docs run build",
+    "deploy": "npm --prefix ../.. run --silent deploy:gen && npm run build && wrangler deploy",
+    "verify": "npm --prefix ../.. run --silent deploy:gen && wrangler deploy --dry-run",
+    "dev": "wrangler dev",
+    "tail": "wrangler tail"
+  },
+  "devDependencies": {
+    "wrangler": "^4.129.0"
+  }
+}

package/dist/assets/deploy/cloudflare-docs/wrangler.template.jsonc

@@ -0,0 +1,30 @@
+{
+  "$schema": "node_modules/wrangler/config-schema.json",
+  // THE PROJECT'S WEBSITE, not a Worker of an installation: the script name is
+  // `<name>-docs` and the hostname the host of `docs`, both from project.json
+  // (src/deploy/wranglerTemplate.ts `siteView`) — an installation never deploys
+  // a copy of the site, and the bot's /docs sends everyone to the published one.
+  "name": "{{script}}",
+  "compatibility_date": "2026-08-01",
+  // The account the project's own CI deploys the site to: the one value the
+  // deployment profile (deploy/profile.json `account`) contributes here.
+  "account_id": "{{account}}",
+  // ASSETS ONLY: no `main`, so there is no Worker script, no Durable Object,
+  // and no container. Nothing here can be mid-rollout or draining, which is
+  // exactly why CI may deploy it on every docs change, while the four runtime
+  // Workers deploy on the release, preflighted and in order (AGENTS.md,
+  // docs/reference/specs/docs-site.md, docs/reference/specs/release-and-deploy.md).
+  "assets": {
+    "directory": "../../docs/.vitepress/dist",
+    // VitePress emits clean URLs (`/reference/cli.html`), so /reference/cli must
+    // resolve to it; a miss serves the built 404 page, not an empty 404.
+    "html_handling": "auto-trailing-slash",
+    "not_found_handling": "404-page"
+  },
+  // workers.dev is DISABLED so the site has exactly one hostname, the one
+  // project.json publishes. The site is public: no Access application fronts
+  // it, and nothing here is an installation's to gate.
+  "workers_dev": false,
+  "routes": [{ "pattern": "{{hostname}}", "custom_domain": true }],
+  "observability": { "enabled": true }
+}

package/dist/assets/deploy/cloudflare-memory/package.json

@@ -0,0 +1,25 @@
+{
+  "name": "switchboard-memory-worker",
+  "private": true,
+  "type": "module",
+  "engines": {
+    "node": ">=22"
+  },
+  "scripts": {
+    "deploy": "node ../bin/build-stamp.mjs",
+    "dev": "wrangler dev",
+    "typecheck": "tsc --noEmit -p tsconfig.json",
+    "test": "vitest run",
+    "verify": "npm --prefix ../.. run --silent deploy:gen && npm run typecheck && npm test",
+    "typegen": "wrangler types",
+    "tail": "wrangler tail",
+    "secrets": "npm --prefix ../.. run --silent cli -- deploy secrets memory"
+  },
+  "devDependencies": {
+    "@cloudflare/vitest-pool-workers": "^0.22.0",
+    "@cloudflare/workers-types": "^5.20260904.1",
+    "typescript": "^5.9.3",
+    "vitest": "^4.1.11",
+    "wrangler": "^4.129.0"
+  }
+}

package/dist/assets/deploy/cloudflare-memory/tsconfig.json

@@ -0,0 +1,17 @@
+{
+  // Scoped config so `npm run typecheck` here checks worker.ts (and the shared
+  // src/core/memory engine it imports by relative path) — without it, tsc
+  // silently falls back to the repo-root tsconfig, which excludes this dir.
+  "compilerOptions": {
+    "target": "esnext",
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "lib": ["esnext"],
+    "types": ["@cloudflare/workers-types/experimental", "@cloudflare/vitest-pool-workers/types"],
+    "strict": true,
+    "noEmit": true,
+    "skipLibCheck": true,
+    "allowImportingTsExtensions": true
+  },
+  "include": ["worker.ts", "worker.test.ts", "friction.test.ts", "schedules.test.ts", "test-env.d.ts"]
+}