@codyswann/lisa 3.31.2 → 3.31.4

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "3.31.2",
+  "version": "3.31.4",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/rules/reference/claim-time-guards.md

@@ -1,6 +1,6 @@
 # Claim-Time Guards
 
-Two guards that run when build-intake claims a ready item. Both come from geminisportsai's hand-rolled `sprint-loop` and both address failures actually observed there — an item built twice because it had already shipped, and a loop burning cycles re-attempting an item that was never going to succeed.
+Two guards that run when build-intake claims a ready item. Both come from acmeorgb's hand-rolled `sprint-loop` and both address failures actually observed there — an item built twice because it had already shipped, and a loop burning cycles re-attempting an item that was never going to succeed.
 
 It is a **single vendor-neutral contract** consumed by all three build-intake skills (`lisa-github-build-intake`, `lisa-jira-build-intake`, `lisa-linear-build-intake`). Each arm cites this slug in its claim step rather than growing its own copy, exactly as the arms cite `leaf-only-lifecycle`, `repo-scope-split`, `rejection-detection`, and `claim-archaeology`. One slug is what keeps a guard that fires on GitHub from being absent on Linear.
 

package/plugins/src/base/skills/lisa-detect-tooling/SKILL.md

@@ -57,7 +57,7 @@ Discovery only works if "what does this run" can be answered from shell text wit
 
 **`$( )` restarts the quoting context.** In `"$(printf '%s' "$JSON" | node -e '…')"`, quotes inside the substitution pair among themselves. A flat scanner falls out of phase on the first one and starts reporting the payload's own string literals.
 
-Against Lisa and the three TunnlAI repositories, what survives is `gitleaks`, `jq`, `gtimeout` and `eas` — every one a real, undeclared invocation, with no false positives.
+Against Lisa and the three AcmeOrgD repositories, what survives is `gitleaks`, `jq`, `gtimeout` and `eas` — every one a real, undeclared invocation, with no false positives.
 
 ## What it will not do
 

package/plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -162,7 +162,7 @@ ends in between — turns exhausted, job timeout, or you concluding the work whi
 checks are still pending — the latch stays off and nothing restores it. The PR is
 left WORSE OFF THAN IF THIS SKILL HAD NEVER RUN: it has lost the mechanism that
 merges it while no agent is watching, and the run reports success. Measured on
-`gunnertech/frontend#282`, the latch went off 14s before the fix commit and the
+`acmeorgc/frontend#282`, the latch went off 14s before the fix commit and the
 PR sat 26 minutes after going green, against ~3 minutes for PRs this skill never
 touched.
 
@@ -364,7 +364,7 @@ Ancestry proves your code is *in* the merged branch; it does **not** prove
 anything deployed. GitHub can **suppress the `on: push` event for a merge commit
 created by auto-merge or a bot token** (`GITHUB_TOKEN`), so the deploy workflow
 fires **zero** runs — no run, not even a `startup_failure` — while the ancestry
-check above stays green. Incident of record: TunnlAI/frontend **TUN-186** (PR #67)
+check above stays green. Incident of record: AcmeOrgD/frontend **TUN-186** (PR #67)
 merged to `dev` via auto-merge; the merge commit `1b3f836` produced **no**
 `deploy.yml` run, and only the next human push `d1fe18c` (which carries `1b3f836`
 as an ancestor) actually shipped it. **Never report shipped on ancestry alone.**
@@ -423,7 +423,7 @@ of section 2 are diagnose-only).
 
 Linear's GitHub integration completes a linked Issue on merge to **any** branch
 — branch-name linkage alone triggers it, even when the PR body carries only the
-non-closing `Linear: <ID>` reference form (incident of record: TunnlAI backend
+non-closing `Linear: <ID>` reference form (incident of record: AcmeOrgD backend
 PR #207 merged to `dev`; TUN-256 auto-completed and had to be manually
 reverted). Run this step **as soon as the PR reports `MERGED`**, before the
 deploy-run verification above can terminate the flow — a `blocked:deploy`

package/plugins/src/base/skills/lisa-secrets-access/SKILL.md

@@ -239,7 +239,7 @@ An org secret defaults to `--visibility private`. `all` reaches public repositor
 ```json
 "propagating": [
   "LINEAR_API_KEY",
-  { "name": "NPM_TOKEN", "targets": ["TunnlAI", "TunnlAI/wiki"] }
+  { "name": "NPM_TOKEN", "targets": ["AcmeOrgD", "AcmeOrgD/wiki"] }
 ]
 ```
 

package/plugins/src/base/skills/lisa-secrets-access/scripts/materialize-secrets.mjs

@@ -248,8 +248,8 @@ export function installAwsProfiles(bundle, options = {}) {
   // Refuse to write a profile name the operator already uses outside our block.
   //
   // AWS does not error on a duplicate `[profile x]` — it resolves one and
-  // ignores the other. So writing `tunnl-dev` next to an operator's existing SSO
-  // `tunnl-dev` would silently run some calls as the wrong identity, which is
+  // ignores the other. So writing `acmeorgd-dev` next to an operator's existing SSO
+  // `acmeorgd-dev` would silently run some calls as the wrong identity, which is
   // worse than either winning outright. Merging protects their sections from
   // being deleted; this protects them from being shadowed.
   //

package/plugins/src/base/skills/lisa-setup-notion/SKILL.md

@@ -51,7 +51,7 @@ Print instructions for the user:
 
 The user picks a stable identifier for this workspace. Two options:
 
-- **Workspace name** (human-readable, e.g., `Gemini Sports`). Easy to recognize, can be ambiguous if a workspace is renamed in Notion. Recommended.
+- **Workspace name** (human-readable, e.g., `AcmeOrgB`). Easy to recognize, can be ambiguous if a workspace is renamed in Notion. Recommended.
 - **Workspace UUID** (returned by Notion's API). Stable but opaque.
 
 Default to the workspace name. After the user stores the token (Step 4), Step 5's `/users/me` call surfaces the actual `bot.workspace_name`; if it differs from what the user typed (capitalization, trailing whitespace), prompt to confirm.
@@ -60,7 +60,7 @@ Default to the workspace name. After the user stores the token (Step 4), Step 5'
 WORKSPACE=$(jq -r '.notion.workspaceId // empty' .lisa.config.json 2>/dev/null)
 if [ -z "$WORKSPACE" ]; then
   # Prompt the user — accept any non-empty string. They pick the slug; we just store it.
-  read -p "Workspace identifier (any stable slug, e.g. 'gemini-sports'): " WORKSPACE
+  read -p "Workspace identifier (any stable slug, e.g. 'acme-org-b'): " WORKSPACE
 fi
 ```
 

package/scripts/lisa-assert-eas-profile.mjs

@@ -21,7 +21,7 @@
  * ## Why this does not use `JSON.parse`, and does not read one profile
  *
  * `eas.json` is not required to be strict JSON — trailing commas are common
- * and EAS accepts them. A real consumer file (`geminisportsai/frontend-v2`)
+ * and EAS accepts them. A real consumer file (`acmeorgb/frontend-v2`)
  * has one on line 16, so a strict parse would crash this guard on the very
  * repository the standard was extracted from.
  *

package/typescript/copy-overwrite/scripts/check-nightly-e2e-health.mjs

@@ -73,8 +73,8 @@
  * because it is the right vocabulary. What is NOT kept is gemini's
  * `unknown`-passes-with-a-warning: that is a fail-open path, and here `unknown`
  * fails once bootstrap closes. The bypass model and the context-pinning
- * discipline come from tunnl (TUN-525 / TUN-402). The job-name filter comes from
- * propswap's `nightly-e2e-lib.sh`, whose unbounded bootstrap is what §4 of the
+ * discipline come from acmeorgd (TUN-525 / TUN-402). The job-name filter comes from
+ * acmeorga's `nightly-e2e-lib.sh`, whose unbounded bootstrap is what §4 of the
  * contract time-boxes.
  *
  * @module scripts/check-nightly-e2e-health
@@ -549,7 +549,7 @@ export function validateSuites(raw) {
         days > BOOTSTRAP_ABSOLUTE_MAX_DAYS
       ) {
         throw new GateConfigError(
-          `${where}: \`grace_days\` must be a number in (0, ${BOOTSTRAP_ABSOLUTE_MAX_DAYS}]. A grace that outlives the bootstrap ceiling IS propswap's forever-bootstrap, whatever it is called — rejected rather than clamped, so widening it is a reviewable act.`
+          `${where}: \`grace_days\` must be a number in (0, ${BOOTSTRAP_ABSOLUTE_MAX_DAYS}]. A grace that outlives the bootstrap ceiling IS acmeorga's forever-bootstrap, whatever it is called — rejected rather than clamped, so widening it is a reviewable act.`
         );
       }
     }
@@ -695,7 +695,7 @@ export function assessSuite(suite, observation, context) {
     // `platform: android` leaves the iOS job skipped while the run still
     // concludes `success`. Read as a run conclusion alone, that filtered
     // dispatch cleared a required merge gate for an arm that never executed —
-    // propswap's trap, a suite declaring itself green on evidence it never
+    // acmeorga's trap, a suite declaring itself green on evidence it never
     // gathered. The same shape reaches the CRON path: with
     // `require_prerequisites: false` and no EXPO_TOKEN, every job skips and the
     // run is still `success`.
@@ -829,7 +829,7 @@ export function resolveBootstrap(until, maxDays, now) {
   const days = (parsed - now.getTime()) / 86_400_000;
   if (days > maxDays) {
     throw new GateConfigError(
-      `\`bootstrap_until\` (${until}) is ${Math.ceil(days)} days out, beyond \`bootstrap_max_days\` (${maxDays}). A bootstrap window that can be extended by editing one string is propswap's forever-bootstrap: a suite that never runs passes forever. Raise the cap deliberately, in the same review, or bring the date in.`
+      `\`bootstrap_until\` (${until}) is ${Math.ceil(days)} days out, beyond \`bootstrap_max_days\` (${maxDays}). A bootstrap window that can be extended by editing one string is acmeorga's forever-bootstrap: a suite that never runs passes forever. Raise the cap deliberately, in the same review, or bring the date in.`
     );
   }
   return Object.freeze({
@@ -849,7 +849,7 @@ export function resolveBootstrap(until, maxDays, now) {
  * audited bypass. Neither is proportionate to the routine act of adding a
  * suite, and both teach people that the gate is something to get around.
  *
- * What keeps this from becoming propswap's forever-bootstrap is the ANCHOR.
+ * What keeps this from becoming acmeorga's forever-bootstrap is the ANCHOR.
  * The window is not a date somebody picks; it is `first_seen + grace_days`,
  * and `first_seen` MAY NOT BE IN THE FUTURE. A future anchor would make this a
  * hand-typed expiry under another name, extendable by one string edit forever —
@@ -1279,7 +1279,7 @@ export function formatReport(verdict, context) {
  * implied. The reporter asks it separately and on purpose: closing a tracking
  * issue is a stronger claim than letting a pull request through — it announces
  * that a suite is healthy — and it is the one action that must never fire on a
- * run that skipped part of itself. propswap's trap, in their words: *one spec
+ * run that skipped part of itself. acmeorga's trap, in their words: *one spec
  * reporting success would close the tracking issue while the failures that
  * opened it went unrun.* Asking the question here means a future loosening of
  * row 26 cannot silently re-open that hole.

package/typescript/copy-overwrite/scripts/check-skipped-required-checks.mjs

@@ -6,7 +6,7 @@
  * check-skipped-required-checks — refuse a required status check that satisfies
  * without proving anything.
  *
- * Shipped by Lisa (copy-overwrite). Generalized from tunnl's TUN-402 guard: the
+ * Shipped by Lisa (copy-overwrite). Generalized from acmeorgd's TUN-402 guard: the
  * logic is Lisa's and gets updated fleet-wide, the two REVIEWED SNAPSHOTS it
  * rests on are per-repo and live in `.github/required-checks.json` (create-only,
  * yours to edit).
@@ -88,7 +88,7 @@
  * nobody ever ran.
  *
  * This is measured, not theoretical, in at least two repositories in this
- * portfolio — tunnl (`🔍 Quality Checks / 🧪 Run E2E Tests`, TUN-402) and gemini
+ * portfolio — acmeorgd (`🔍 Quality Checks / 🧪 Run E2E Tests`, TUN-402) and gemini
  * (ruleset 14297996 requiring `🔍 Quality Checks / 🎭 Playwright E2E Tests`,
  * which `ci.yml` skipped unconditionally, so the ruleset enforced nothing).
  *
@@ -108,7 +108,7 @@
  * That mutual policing has one blind spot, and `--remote` exists for it: two
  * snapshots in one repo can only catch each other drifting from the CODE.
  * Neither can see the ruleset itself change in the admin console — which is
- * exactly how tunnl's list silently went from ten contexts to eleven, with every
+ * exactly how acmeorgd's list silently went from ten contexts to eleven, with every
  * test still green, because the "independent" transcription was made from the
  * same reading at the same moment.
  *
@@ -1032,7 +1032,7 @@ export function fetchLiveRequiredContexts(ruleset) {
  * Diffs the committed snapshot against the live ruleset, in BOTH directions.
  *
  * Both directions matter. A context added in the admin console makes the
- * snapshot UNDER-detect (tunnl's ten-to-eleven drift, unnoticed for a day with
+ * snapshot UNDER-detect (acmeorgd's ten-to-eleven drift, unnoticed for a day with
  * every test green). A context removed there makes it OVER-detect, and the
  * obvious fix for a false alarm is to weaken the guard.
  *

package/typescript/copy-overwrite/scripts/nightly-e2e-suites.schema.json

@@ -51,7 +51,7 @@
           "type": "number",
           "exclusiveMinimum": 0,
           "maximum": 30,
-          "description": "How many days after `first_seen` this suite's grace window lasts. Default 14. Requires `first_seen` — a grace length with no anchor forgives nothing and reads as though it forgives everything. Bounded by the same ceiling as the bootstrap window (`bootstrap_max_days`, hard ceiling 30): per-suite grace spends from the same forgiveness budget, and a grace that could outlive that ceiling is propswap's forever-bootstrap wearing a per-suite hat."
+          "description": "How many days after `first_seen` this suite's grace window lasts. Default 14. Requires `first_seen` — a grace length with no anchor forgives nothing and reads as though it forgives everything. Bounded by the same ceiling as the bootstrap window (`bootstrap_max_days`, hard ceiling 30): per-suite grace spends from the same forgiveness budget, and a grace that could outlive that ceiling is acmeorga's forever-bootstrap wearing a per-suite hat."
         }
       }
     },