feat(system): seedgo v2 operational, full system audit, 14/15 branches at 99%

Three days of intensive work bringing seedgo to full operational status
and driving all branches through comprehensive standards compliance.

Seedgo v2.0.0:
- 22 checkers active (up from 20), standards pack fully operational
- New introspection standard researched from Dev-Pass, FPLAN-0017 open
- Bypass system for false positives (.seedgo config)
- Standards query and audit commands fully functional

System-wide audit (FPLAN-0016):
- All 14 auditable branches at 99%+ compliance
- CLI imports standardized across all branches (console from cli.apps.modules)
- handle_command(command, args) → bool contract added to all modules
- print_help() function naming fixed for checker pattern matching
- Handler extraction: large modules split, file I/O moved to handler layer
- New handlers created across ai_mail, backup, daemon, flow, skills, spawn, seedgo

Branch-specific highlights:
- ai_mail: email.py split 840→420 lines, 4 new handlers
- flow: dplan_flow.py 688→591 lines, 4 new handlers
- seedgo: massive restructure — standards moved to handlers/aipass_standards/,
  old standards/ tree removed, bypass system added, diagnostics module
- commons: database module added, CLI imports fixed
- skills: 5 handle_commands added, help function renamed
- trigger: error reporter handler, handle_command routing
- All branches: consistent architecture, clean drone routing

Culture doc (CLAUDE.md) added — documents AIPass philosophy, identity,
memory system, and collaboration principles.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/aipass/trigger/README.md

@@ -1,6 +1,17 @@
 # Trigger
 
-Event bus for AIPass. Branches fire events, registered handlers react. Decouples producers from consumers — the module that detects a condition doesn't need to know what should happen next.
+**Purpose:** Event bus for AIPass. Branches fire events, registered handlers react. Decouples producers from consumers — the module that detects a condition doesn't need to know what should happen next.
+**Module:** `aipass.trigger`
+**Last Updated:** 2026-03-08
+
+## Commands / Usage
+
+```bash
+drone @trigger fire <event> [data]              # Fire an event
+drone @trigger list                             # List registered events
+drone @trigger status                           # Event bus status
+drone @trigger --help                           # Full help
+```
 
 ## Usage
 
@@ -74,12 +85,34 @@ Built-in error monitoring subsystem. Watches logs for errors, fingerprints them
 ```
 trigger/
 ├── apps/
-│   ├── trigger.py         # Entry point (auto-discovers modules)
+│   ├── trigger.py             # Entry point (auto-discovers modules)
 │   ├── modules/
-│   │   ├── core.py        # Event bus (Trigger.fire/on/off)
-│   │   ├── errors.py      # Error registry + cross-branch API
-│   │   └── medic.py       # Error monitoring commands
+│   │   ├── core.py            # Event bus (Trigger.fire/on/off)
+│   │   ├── errors.py          # Error registry + cross-branch API
+│   │   ├── medic.py           # Error monitoring commands
+│   │   ├── branch_log_events.py  # Branch-level log event handling
+│   │   └── log_events.py     # System-wide log event processing
 │   └── handlers/
-│       └── events/        # One handler per event type
+│       └── events/            # One handler per event type
 └── tests/
 ```
+
+**Note:** `branch_log_events` and `log_events` are auto-discovered modules that handle log-based event detection at branch and system levels respectively.
+
+---
+
+## Integration Points
+
+### Depends On
+- `aipass.prax` — Logging via `system_logger`
+- `aipass.cli` — Console output and header formatting
+- Python stdlib (`sys`, `pathlib`, `importlib`)
+
+### Provides To
+- All modules — event bus (`Trigger.fire`, `Trigger.on`, `Trigger.off`)
+- All modules — cross-branch error reporting (`report_error`)
+- All modules — medic error monitoring and dispatch
+
+---
+
+*Last Updated: 2026-03-08*