Skip to content

Operator runbooks and the two checklist holes left after 0.5.0 - #16

Merged
yellowgram merged 1 commit into
mainfrom
cursor/operator-runbooks-356c
Sep 26, 2026
Merged

yellowgram merged 1 commit into
mainfrom
cursor/operator-runbooks-356c

Conversation

@yellowgram

Copy link
Copy Markdown
Owner

Summary

PR #15 (3328052) was checked in the tree, not taken on its word. The proxy, dual-layer demo, policy refuse-start, support boundary, and pin story for l2-send-guard@0.5.0 are real. What was still missing was the operator pack, and two checklist items that were only half done: bug reports without a repro were closed by hand, and CI did not run current Node LTS (24).

This PR adds docs, templates, one offline workflow, and Node 24 on the existing CI matrix. No new proxy behavior. npm publish was not run. Version stays 0.5.0. No payee was invented.

Status matrix: REMAINING_GAPS.md. Design and review notes: docs/DESIGN_ITERS.md (section "Operator pack").

Closed in this PR

Checklist

#1–#14, #16–#17, #19–#25, #27–#30 were already present on main and were re-checked. #21 stays the pin story only (l2-send-guard@0.5.0); publish is held. #26 stays deferred (founder payee).

User needs (Guard-shippable docs that were absent)

Templates for fill-ins that stay user-owned: #5, #8, #9, #11, #15, #23, #25, #27, #35, #42, #47. Index: docs/OPERATOR.md.

Still open (on purpose)

  • Checklist #26 — founder payee. SUPPORT.md is the boundary. No Wise, Polar, USDT, or contact address.
  • Soft-WTP and out of charter (user needs 48–56): custody, Safe/Zodiac/ERC-7579, mainnet SLA, hosted SaaS, MEV. Not expanded.
  • True user-owned fill-ins: their RPC, keys, host, allowlist addresses, cap numbers, RACI names, burner capital, notify endpoint, log store, alert destination, and prompt text.

Design iterations

  1. Security / ops. Attack: runbooks that recommend a public bind, call policy ON safe, or invent a payee; a bot that closes vulnerability reports. Change: honesty lines required, bot scoped to bug / [bug], systemd sample binds 127.0.0.1.
  2. Maintainer / DX, attacking 1. Attack: a second decision table, a Node 24 claim without CI, an untested classifier that treats an empty template as filled. Change: short pages that link the existing table, Node 24 on the matrix, scripts/repro-triage.mjs under vitest, same-line field checks.
  3. Buyer / integrator, attacking 2. Attack: a reverting canary looks like a bad policy edit; kill switch inside Guard; staging read as mainnet; quoted bench milliseconds; closing a needs-repro issue whose body was later fixed. Change: canary lists -32080, kill switch stops the agent, both environments are Sepolia, stale pass clears a filled body.

Code reviews

  1. Security / ops. Empty template fields stole the next line via \\s (fixed). The template sentence "Vulnerability reports do not belong here" matched the security skip and would have exempted every bug (fixed). Poison-policy exit 1 plus restart: unless-stopped loops; systemd StartLimitBurst belongs in [Unit] (fixed and documented).
  2. Maintainer / DX. Direct-run guard so importing the classifier does not process.exit (fixed, CLI spawn test). tests/operator-docs.test.ts locks pages, npm files, relative links, and the absence of a payee or a safe-agent claim. Latency text matched src/sim/simulator.ts (fallback only after an uncertain primary eth_call).
  3. Buyer. Canary step now includes -32080. Halt sample comment states the in-memory 0x1111… map is not a policy file. No publish, no payee, version stays 0.5.0.

Tests

Offline, same shape as CI: npm test, npm run build, npm run policy:check, npm run demo:dual-layer, node examples/agent-viem-halt.mjs, npm run demo:offline. 140 tests on Node 22 and on Node v24.10.0. No public RPC.

Open in Web Open in Cursor 

PR #15 already shipped the proxy, dual-layer demo, and support boundary. Operators still had no change protocol, triage tree, incident labels, or upgrade/rollback notes, and bug reports without a repro were only closed by hand. This adds that pack, a needs-repro workflow, and Node 24 on the offline CI matrix. Version stays 0.5.0. npm publish is not run.

Co-authored-by: yellowgram <yellowgram@users.noreply.github.com>
@yellowgram
yellowgram marked this pull request as ready for review September 26, 2026 13:53
@yellowgram
yellowgram merged commit 035c643 into main Sep 26, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants