S56: spawn template overhaul + system-wide README push + .gitkeep cleanup (#129)

- Spawn template system rebuilt: regenerate-registry command (3-pass ID matching),
  registry 26→41 files, generate_branch_meta fixed, Phase 0 snapshot added
- System-wide push: 12/12 branches updated (227 additions, 0 errors)
- READMEs added to all standard directories across 15 branches
- .claude/settings.local.json tracked system-wide (deny rules)
- 35 .gitkeep files removed (replaced by READMEs)
- Bypass files updated across 13 branches
- Bugs fixed: manager citizen_class crash, backup rglob performance

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

src/aipass/trigger/.aipass/README.md

@@ -0,0 +1,3 @@
+# Branch Prompt
+
+AI context for `TRIGGER`. The `aipass_local_prompt.md` file is injected every turn, telling the AI who you are and how to work in your branch.

src/aipass/trigger/.claude/README.md

@@ -0,0 +1,5 @@
+# Claude Code Settings
+
+Claude Code configuration for `TRIGGER`.
+
+Contains `settings.local.json` with permission rules. Most branches are denied raw git commands and must use `drone @git` instead.

src/aipass/trigger/.claude/settings.local.json

@@ -0,0 +1,28 @@
+{
+  "permissions": {
+    "allow": [],
+    "deny": [
+      "Bash(git reset*)",
+      "Bash(git rebase*)",
+      "Bash(git merge*)",
+      "Bash(git config*)",
+      "Bash(git push --force*)",
+      "Bash(git push -f *)",
+      "Bash(git checkout -- *)",
+      "Bash(git checkout .*)",
+      "Bash(git restore --staged*)",
+      "Bash(git restore .*)",
+      "Bash(git clean*)",
+      "Bash(git branch -D*)",
+      "Bash(git stash drop*)",
+      "Bash(git stash clear*)",
+      "Bash(rm -rf*)",
+      "Bash(rm -r *)",
+      "Bash(git checkout -b*)",
+      "Bash(git commit*)",
+      "Bash(git push*)"
+    ],
+    "ask": []
+  },
+  "enabledMcpjsonServers": []
+}

src/aipass/trigger/.seedgo/README.md

@@ -0,0 +1,5 @@
+# Standards Bypass
+
+Seedgo audit bypass config for `TRIGGER`.
+
+When an audit flags a false positive that doesn't apply to your architecture, add a bypass entry in `bypass.json` with a reason explaining why it's justified.

src/aipass/trigger/.seedgo/bypass.json

@@ -14,7 +14,9 @@
     {
       "file": "apps/modules/core.py",
       "standard": "silent_catch",
-      "lines": [160],
+      "lines": [
+        160
+      ],
       "pattern": "except Exception: pass",
       "reason": "Intentional: handler callback runs inside event bus fire(). Logging here would cause infinite recursion (logger fires events via trigger)."
     },
@@ -75,105 +77,134 @@
     {
       "file": "apps/handlers/log_watcher.py",
       "standard": "handlers",
-      "lines": [75],
+      "lines": [
+        75
+      ],
       "reason": "log_watcher imports error_registry.report() for Medic v2 dedup. This is a deliberate handler-to-handler dependency — the registry IS the dedup backend."
     },
     {
       "file": "apps/handlers/error_reporter.py",
       "standard": "handlers",
-      "lines": [25, 45],
+      "lines": [
+        25,
+        45
+      ],
       "reason": "error_reporter imports error_registry for tracking and ai_mail for email delivery. These are its core dependencies — it's the dispatch endpoint of the error pipeline."
     },
     {
       "file": "apps/handlers/watchers/log_watcher.py",
       "standard": "handlers",
-      "lines": [242],
+      "lines": [
+        242
+      ],
       "reason": "Watcher imports trigger module to fire events. Handler→module import needed because watcher operates as standalone watchdog callback."
     },
     {
       "file": "apps/handlers/events/error_detected.py",
       "standard": "handlers",
-      "lines": [76],
+      "lines": [
+        76
+      ],
       "reason": "error_detected handler imports error_registry to query error details during dispatch. Core integration point for the error pipeline."
     },
     {
       "file": "apps/handlers/events/startup.py",
       "standard": "handlers",
-      "lines": [371],
+      "lines": [
+        371
+      ],
       "reason": "Startup handler imports memory rollover module to trigger memory checks on startup events. Cross-branch integration via modules layer public API."
     },
-
     {
       "file": "apps/config.py",
       "standard": "testing",
-      "lines": [31],
+      "lines": [
+        31
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/modules/core.py",
       "standard": "testing",
-      "lines": [160],
+      "lines": [
+        160
+      ],
       "pattern": "except Exception: pass",
       "reason": "Deferred event queue handler execution — logging would cause infinite recursion (logger fires events via trigger). Same as silent_catch bypass."
     },
     {
       "file": "apps/handlers/json/json_handler.py",
       "standard": "testing",
-      "lines": [24],
+      "lines": [
+        24
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/plan_file.py",
       "standard": "testing",
-      "lines": [58],
+      "lines": [
+        58
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_error() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/memory_threshold_exceeded.py",
       "standard": "testing",
-      "lines": [46],
+      "lines": [
+        46
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/error_logged.py",
       "standard": "testing",
-      "lines": [48],
+      "lines": [
+        48
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/bulletin_created.py",
       "standard": "testing",
-      "lines": [55],
+      "lines": [
+        55
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/error_detected.py",
       "standard": "testing",
-      "lines": [54],
+      "lines": [
+        54
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/startup.py",
       "standard": "testing",
-      "lines": [51],
+      "lines": [
+        51
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
     {
       "file": "apps/handlers/events/registry.py",
       "standard": "testing",
-      "lines": [28],
+      "lines": [
+        28
+      ],
       "pattern": "except Exception: pass",
       "reason": "Meta-logging helper _log_warning() — cannot log a failure to log. Same pattern as silent_catch bypass."
     },
-
     {
       "file": "apps/handlers/error_registry.py",
       "standard": "architecture",
@@ -189,32 +220,40 @@
     {
       "file": "apps/handlers/error_reporter.py",
       "standard": "architecture",
-      "lines": [153],
+      "lines": [
+        153
+      ],
       "pattern": "handler importing from parent module",
       "reason": "error_reporter imports trigger bus to fire error_detected events after reporting. Handler must access event bus to complete the error pipeline."
     },
     {
       "file": "apps/handlers/watchers/log_watcher.py",
       "standard": "architecture",
-      "lines": [244],
+      "lines": [
+        244
+      ],
       "pattern": "handler importing from parent module",
       "reason": "Log watcher imports trigger bus to fire error_logged/warning_logged events. Watchdog callback must access event bus to bridge file monitoring to event system."
     },
     {
       "file": "apps/handlers/events/error_detected.py",
       "standard": "architecture",
-      "lines": [153, 243],
+      "lines": [
+        153,
+        243
+      ],
       "pattern": "handler importing from parent module",
       "reason": "error_detected imports error_registry (line 76) and medic_state — core pipeline dependencies for dispatch gating. Already bypassed under handlers standard."
     },
     {
       "file": "apps/handlers/events/registry.py",
       "standard": "architecture",
-      "lines": [34],
+      "lines": [
+        34
+      ],
       "pattern": "handler importing from parent module",
       "reason": "Registry handler imports trigger module to wire event handlers via trigger.on(). The wiring function must reference the event bus."
     },
-
     {
       "file": "apps/handlers/events/warning_logged.py",
       "standard": "handlers",
@@ -230,11 +269,12 @@
     {
       "file": "apps/handlers/events/registry.py",
       "standard": "handlers",
-      "lines": [34],
+      "lines": [
+        34
+      ],
       "pattern": "handler imports modules",
       "reason": "Registry wiring function imports trigger module to call trigger.on(). Must access the event bus to register handlers — this IS its purpose."
     },
-
     {
       "file": "apps/handlers/error_registry.py",
       "standard": "naming",
@@ -271,14 +311,12 @@
       "pattern": "local variable naming",
       "reason": "Local variables inside startup handler functions, not module-level constants. Checker false positive on function-scoped assignments."
     },
-
     {
       "file": "apps/config.py",
       "standard": "imports",
       "pattern": "prax logger import",
       "reason": "config.py cannot import prax logger — circular dependency. Uses _log_warning() file-based pattern instead. Comment on line 26 documents this."
     },
-
     {
       "file": "apps/handlers/json/json_handler.py",
       "standard": "unused_function",
@@ -291,12 +329,12 @@
     "example": {
       "file": "apps/modules/logger.py",
       "standard": "cli",
+      "reason": "Circular dependency - logger cannot import CLI",
       "lines": [
         146,
         177
       ],
-      "pattern": "if __name__ == '__main__'",
-      "reason": "Circular dependency - logger cannot import CLI"
+      "pattern": "if __name__ == '__main__'"
     },
     "fields": {
       "file": "Relative path from branch root (required)",
@@ -306,4 +344,4 @@
       "reason": "Required - why this bypass exists"
     }
   }
-}
+}

src/aipass/trigger/apps/README.md

@@ -0,0 +1,8 @@
+# Apps
+
+Application layer for `TRIGGER`.
+
+- `trigger.py` — Entry point. Auto-discovers and routes commands to modules.
+- `modules/` — Business logic and orchestration. One module per command.
+- `handlers/` — Implementation details. Called by modules, never by CLI directly.
+- `plugins/` — Scheduled tasks and extensions.

src/aipass/trigger/apps/handlers/README.md

@@ -0,0 +1,5 @@
+# Handlers
+
+Implementation details for `TRIGGER`.
+
+Handlers do the actual work. They are called by modules, never directly by the CLI. Keep business logic in modules, implementation in handlers.

src/aipass/trigger/apps/modules/README.md

@@ -0,0 +1,5 @@
+# Modules
+
+Business logic for `TRIGGER`. One module per command.
+
+Modules orchestrate work by calling handlers. They are the public API of the branch — drone routes commands here.

src/aipass/trigger/apps/plugins/README.md

@@ -0,0 +1,5 @@
+# Plugins
+
+Scheduled tasks and extensions for `TRIGGER`.
+
+Plugins are standalone units of work that can be scheduled via the daemon. Each plugin handles one specific recurring task.

src/aipass/trigger/docs/README.md

@@ -0,0 +1,3 @@
+# Docs
+
+Documentation files for the `TRIGGER` branch.

src/aipass/trigger/templates/README.md

@@ -0,0 +1,5 @@
+# Templates
+
+Branch-specific templates for `TRIGGER`.
+
+Any templates this branch provides to the system or uses internally. Examples: plan templates (flow), trinity templates (memory), test templates (seedgo).

src/aipass/trigger/tests/README.md

@@ -0,0 +1,6 @@
+# Tests
+
+Pytest unit tests for `TRIGGER`.
+
+- `conftest.py` — Shared fixtures (temp dirs, mocks, sample data).
+- `test_*.py` — Test files. Standard tests cover JSON handler, CLI routing, and error resilience. Custom tests cover branch-specific domain logic.