feat(system): registry glob discovery, drone stderr fix, pyright OOM fix (#38)

Registry discovery (drone, spawn, seedgo) now globs for *_REGISTRY.json
with CWD-first walk-up — enabling project isolation without hardcoded
filenames. Drone stderr crash fixed (Rich Console). Pyright OOM fixed
via pyrightconfig excludes. AIPASS.md simplified for universal use.
Global prompt updated with flow commands. DPLAN-003 added for
AIPass-as-OS design vision.

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

src/aipass/devpulse/.aipass/aipass_local_prompt.md

@@ -35,6 +35,7 @@ When a task belongs to a specialist, send it there. Don't burn context doing the
 drone @ai_mail send @target "Subject" "Body" --dispatch   # Task email
 drone @ai_mail dispatch wake @target                       # Wake branch
 drone @flow create . "Subject"                             # Create FPLAN
+drone @flow create . "Subject" dplan                       # Create DPLAN (dplan template)
 drone @flow list                                           # Active plans
 drone systems                                              # All branches
 ```

src/aipass/devpulse/dplan-003/README.md

@@ -0,0 +1,15 @@
+# DPLAN-003 Working Directory
+
+Research, mapping, and planning files for "AIPass as Operating System."
+
+Parent plan: `AIPass/DPLAN-003_aipass_as_operating_system_2026-03-13.md`
+
+## Files
+
+| File | Purpose | Status |
+|------|---------|--------|
+| `registry_discovery_map.md` | Every find_registry() call, file, line number | Pending |
+| `registry_refactor_plan.md` | Shared commons function design, migration steps | Pending |
+| `aipass_init_spec.md` | What `aipass init` creates, CLI design, templates | Pending |
+| `drone_help_spec.md` | `drone aipass help` module design | Pending |
+| `portability_audit.md` | Full investigation results (session 24) | Done |

src/aipass/devpulse/dplan-003/portability_audit.md

@@ -0,0 +1,31 @@
+# Portability Audit — Session 24 Results
+
+## Summary
+
+| Tool | Registry Discovery | CWD-Aware | Portable | Hardcoded |
+|------|-------------------|-----------|----------|-----------|
+| Drone | Walk-up + env var | No (uses registry) | Yes | Registry filename |
+| Spawn | Walk-up + env var | No (uses registry) | Partial | Template location |
+| Prax | Walk-up (no env) | No (sys logs at repo) | Partial | System logs dir |
+| AI_Mail | Walk-up (no env) | No (inbox per branch) | Yes | Inbox location |
+| Flow | Walk-up (no env) | Yes (plan creation) | Hybrid | Plan registry |
+
+## Key Findings
+
+- All tools use walk-up strategy to find `AIPASS_REGISTRY.json`
+- Registry-relative path resolution already works (move registry + dirs = works)
+- `AIPASS_REGISTRY` env var supported by drone and spawn
+- System logs hardcoded to `{repo_root}/system_logs/`
+- Spawn templates hardcoded to `{spawn_package}/templates/`
+- Walk-up doesn't stop at project boundaries — finds nearest registry up the tree
+
+## The Core Fix
+
+Change `find_registry()` to:
+1. Walk up from CWD looking for `*_REGISTRY.json` (glob, not hardcoded name)
+2. Stop at first match — that's the project boundary
+3. If none found, return error ("No AIPass project. Run `aipass init`")
+
+## Source
+
+Full investigation transcript: background agent session 24, 42 tool calls across drone/spawn/ai_mail/flow/prax.