@open-everywhere/create 0.1.4 → 0.2.1

package/template/agent/spend/checkpoints.ts

@@ -8,12 +8,14 @@
 // scope is over its monthly total. A checkpoint is softer and per-session — when a single
 // conversation gets expensive it PAUSES only CONSEQUENTIAL actions (PRs, memory writes, skill/
 // routine creation, …) and posts a "keep going?" card. Reads and replies are never blocked, and a
-// member's approval lets the agent resume for the rest of that session. It's a runaway-session
-// circuit-breaker, not a spend ceiling.
+// member's approval lets the agent resume. On a live session the approval lasts until the window
+// rotates or `approvals.checkpointTtlHours` (default 24 h) lapses, whichever comes first. On a
+// durable job's session it does not lapse: the agent asks again once it has spent that much again.
+// It's a runaway-session circuit-breaker, not a spend ceiling.
 //
 // EMPTY BY DEFAULT — with nothing declared here, nothing is checkpointed (Open Everywhere never
 // invents a threshold). This file is the seam a DB/dashboard would swap behind, same as
-// budgets.ts / memory/config/domains.ts. After adding a checkpoint: `npm run typecheck:all`
+// budgets.ts / memory/config/domains.ts. After adding a checkpoint: `npm run typecheck`
 // (assertSpendCheckpointsValid runs at import time and throws on a malformed entry — bad scope
 // keys, unknown/typo'd fields, non-positive amounts).
 //

package/template/agent/webhooks/hooks.generated.ts

@@ -1,14 +1,15 @@
 // GENERATED + MACHINE-OWNED — DO NOT HAND-EDIT.
 //
 // The webhook-hooks overlay: DATA ONLY. Written exclusively by the deterministic codemod
-// (packages/core/agent/webhooks/hooks-codemod.ts) on a bot-PR branch; the PR merge is the approval gate.
+// (@open-everywhere/core/agent/webhooks/hooks-codemod.js) on a bot-PR branch; the PR merge is the approval gate.
 //
 // The codemod re-emits this file from its own parsed content and refuses to rewrite it when the
-// bytes differ, so a hand-edit stops the next machine PR. Before a merge, nothing checks that the
-// file is still data only unless the repository runs its own check: the person who merges the PR
-// is the gate. Read a PR to this file as code, because it is code.
+// data or the import differ, so a hand-edit there stops the next machine PR. Before a merge,
+// nothing checks that the file is still data only unless the repository runs
+// `npx oe build --check` or `npx oe overlays check`: the person who merges the PR is the gate.
+// Read a PR to this file as code, because it is code.
 //
-// To change it by hand, edit only the data below and keep the layout exactly as emitted.
+// To change it by hand, edit only the data below, then run `npx oe overlays normalize`.
 
 import type { HooksFile } from "@open-everywhere/core/agent/webhooks/hooks-codemod.js";
 

package/template/claude/skills/upgrade-open-everywhere/SKILL.md

@@ -64,6 +64,30 @@ step 3, after the install puts the target's own copy on disk. The same text is i
 **Stop and ask the user** when the window holds a breaking change, an env change or a manual step.
 Those are decisions, not steps.
 
+`--plan` also prints a **template drift** report. It compares every file the scaffold copied into
+this app with the TARGET release's `@open-everywhere/create` template, and lists each one that
+differs, with a one-line size of its diff. An upgrade changes only `package.json`, so a scaffolded
+file stays as the old template wrote it. A stale copy can typecheck and build and still break the
+deployment: the 0.1.2 `agent/lib/register-adapters.ts` registers no Postgres client on a bare
+`DATABASE_URL`, so a Vercel+Neon deployment of 0.1.4 fails at its first write.
+
+`agent/lib/register-adapters.ts` is the exception once it is current. The current template's copy
+is ONE call, `registerDefaultAdapters()` from `@open-everywhere/adapters`, plus a `customAdapters`
+hook. The adapter wiring, the store selection rules and the floors live in that package, so the
+package upgrade carries them, and the file needs no hand-merge. Sync it ONCE, from a copy that wires
+the adapters by hand to the one-call copy: move any adapter the user registered by hand into the
+`customAdapters` hook. After that, a SYNC line for this file is a comment or hook difference only.
+
+| Line | What to do |
+| --- | --- |
+| SYNC | a template-owned file — wiring, a script, `AGENTS.md`, `README.md`, `.env.example`, a skill. Plan to copy the target's file over this one, after you read the diff. |
+| config | the app's own config-as-code. A difference is normal once the app is configured. Merge the template's change by hand only if the user wants it. |
+
+The report never writes a file. If it says the drift check did not run, compare the files with the
+target's template by hand. An installed core without the report prints none: `oe upgrade` runs the
+INSTALLED core's code. So when `--plan` prints no "Template drift" heading, run
+`npx oe upgrade --to <target> --plan` once more after step 3. The target's own code prints the report then.
+
 ## 3. Run the upgrade
 
 ```
@@ -95,10 +119,18 @@ survives `rm -rf node_modules && npm ci`.
 Never delete the marker to make `oe upgrade` say there is nothing to do. It is the only record
 that a run began taking the target and never proved the tree.
 
-**If it refuses with "the release notes name codemods this CLI does not hold":** the codemod ships
-in a newer core than the one you are running. Upgrade in ONE step to a version that holds it, or
-apply those migrations by hand. Do not work around the refusal — it exists because a half-applied
-migration that reports success is worse than a stop.
+**If it refuses with "the release notes name codemods this CLI does not hold":** the running core
+is 0.1.4, and it runs codemods from its own registry. When it stops after the install, the
+target's own `oe` is installed now. Run `oe upgrade` again: the resume marker keeps the window, and
+the target's registry applies the codemod. Apply the migration by hand only if that run refuses
+too. Do not work around the refusal — it exists because a half-applied migration that reports
+success is worse than a stop. A later core only WARNS with that text before the install, because
+the target's own registry decides.
+
+**If it refuses with "the installed core's registry does not hold":** the target release names a
+codemod that it does not ship, and no codemod ran. Run `oe upgrade --to <a later release that holds
+it>`. The resume marker keeps the refused release in that run's window, so that run applies the
+codemod. Do not delete the marker to get past this refusal.
 
 ## 4. Review the diff
 
@@ -115,6 +147,21 @@ is the review surface, and it is the only one.
 Then run the app's own checks once more if anything above was fixed by hand:
 `npm run typecheck && npm run build`.
 
+Then act on the template drift report. A core that carries it prints it again after the install;
+if this run printed no "Template drift" heading, run `npx oe upgrade --to <target> --plan` now to get it. For
+each SYNC line, read the diff against the installed template, for example
+`diff node_modules/@open-everywhere/create/template/agent/lib/register-adapters.ts agent/lib/register-adapters.ts`.
+Keep any edit the user made on purpose, and copy the template's file otherwise. For
+`agent/lib/register-adapters.ts`, the user's edits belong in the `customAdapters` hook of the
+template's one-call copy, never in a hand-wired copy: a hand-wired copy does not get the product's
+wiring changes on the next upgrade. A file under the
+template's `claude/` directory lands in the app's `.claude/`, and the template's `gitignore` is the
+app's `.gitignore`. Name every synced file in the pull request.
+
+Run `npx oe build --check`. It also proves the machine-owned `*.generated.ts` overlays hold only
+data. If it says an overlay has older header text, that is not a failure: run
+`npx oe overlays normalize` and commit the header change with the upgrade.
+
 ## 5. Open a pull request
 
 Commit on a branch, never on the default branch. The body carries:
@@ -124,6 +171,7 @@ Commit on a branch, never on the default branch. The body carries:
 - what changed in `roster.lock.json`, in your own words;
 - **the env names the deployment needs before this merges**, names only;
 - the manual steps, and who does each one.
+- the template files you synced, and each SYNC line you left as it is, with the reason.
 
 Then stop. The admin reviews the lock diff and merges. The merge deploys.
 

package/template/package.json

@@ -31,7 +31,7 @@
     "@open-everywhere/provider-notion": "{{OE_VERSION}}",
     "@open-everywhere/provider-slack": "{{OE_VERSION}}",
     "@open-everywhere/provider-teams": "{{OE_VERSION}}",
-    "eve": "0.54.3",
+    "eve": "0.71.0",
     "just-bash": "^3.1.0"
   },
   "devDependencies": {

package/template/roster.lock.json

@@ -39,6 +39,7 @@
         "hook/eve-patch-gate": "mounted",
         "hook/fire-carriage": "mounted",
         "hook/fire-toolset": "mounted",
+        "hook/held-question": "mounted",
         "hook/job-posture": "mounted",
         "hook/lean-seat": "mounted",
         "hook/learn": "mounted",
@@ -69,10 +70,13 @@
         "tool/add_label": "mounted",
         "tool/add_routine_rule": "mounted",
         "tool/agent_version": "mounted",
+        "tool/ask_question": "mounted",
+        "tool/ask_room": "mounted",
         "tool/assign": "mounted",
         "tool/aws": "mounted",
         "tool/browser_tools": "mounted",
         "tool/cancel_routine": "mounted",
+        "tool/cancel_work": "mounted",
         "tool/capture_events": "mounted",
         "tool/check_pr_status": "mounted",
         "tool/checkout_repo": "mounted",
@@ -118,6 +122,7 @@
         "tool/read_channel": "mounted",
         "tool/read_docs": "mounted",
         "tool/read_file_upload": "mounted",
+        "tool/read_github_issue": "mounted",
         "tool/read_routine_transcript": "mounted",
         "tool/read_thread": "mounted",
         "tool/read_thread_seat": "mounted",
@@ -151,7 +156,8 @@
         "tool/unlink_identity": "mounted",
         "tool/update_status": "mounted",
         "tool/usage_report": "mounted",
-        "tool/walk_pr": "mounted"
+        "tool/walk_pr": "mounted",
+        "tool/work": "mounted"
       }
     },
     "@open-everywhere/provider-github": {

package/template/scripts/ops-mcp.ts

@@ -13,6 +13,7 @@ import { registerSlackOps } from "@open-everywhere/provider-slack/agent/ops.js";
 import { registerGithubOps } from "@open-everywhere/provider-github/agent/ops.js";
 import { registerSurfaceTrustPreflight } from "@open-everywhere/core/agent/identity/trust-preflight.js";
 import { importAppModule, resolveAppRoot } from "@open-everywhere/core/agent/scaffold/app-root.js";
+import { registerSettings, type AgentSettingsOverrides } from "@open-everywhere/core/agent/settings/settings.js";
 
 // The app root: `OE_APP_ROOT`, else the nearest directory above the working directory that holds
 // package.json and agent/agent.ts.
@@ -20,6 +21,21 @@ const APP_ROOT = resolveAppRoot();
 // Populate the trust register BEFORE the trust preflight registers: an empty register would report
 // every surface with traffic as undeclared.
 await importAppModule("agent/identity/surfaces.ts", APP_ROOT);
+// The app's SETTINGS (OPE-2334). `surface_manifest` renders each chat app's name, bot name and slash
+// command from the `identity.*` settings, so the server registers the deployment's own declaration
+// before it serves. Without this the manifest would carry the shipped defaults, not the app's name.
+// FAIL-SOFT: `defineSettings` throws at load on an invalid value, and a settings file that throws
+// must not take down the server whose preflight and status tools diagnose it. The manifests then
+// render with the shipped defaults, and stderr says so.
+try {
+  const { SETTINGS_OVERRIDES } = await importAppModule<{ SETTINGS_OVERRIDES: AgentSettingsOverrides }>("agent/settings/settings.ts", APP_ROOT);
+  registerSettings(SETTINGS_OVERRIDES);
+} catch (err) {
+  process.stderr.write(
+    `open-everywhere-ops: agent/settings/settings.ts did not load (${err instanceof Error ? err.message : String(err)}) — ` +
+      "surface_manifest renders the shipped default names until it does\n",
+  );
+}
 
 registerSlackOps();
 registerGithubOps();

package/template/agent/instrumentation.ts

@@ -1,6 +0,0 @@
-// Eve discovers this file by convention (agentRoot `instrumentation.ts`) and reads its
-// default export at server startup. The implementation — OTel span export via Vercel
-// Ship's `registerOTel`, no-op without a collector — lives in the adapters workspace
-// (`@vercel/otel` is a vendor SDK; core stays vendor-free). A self-host swaps this line
-// for its own instrumentation adapter without touching core.
-export { default } from "@open-everywhere/adapters/agent/instrumentation.js";