Add cross-project pattern registry for retrieval-augmented generalization

- Create patterns/ directory with README, manifest, and 10 initial patterns
  covering Ollama JSON fallback, API escaping, deprecation, PTY auth,
  queue-poll, LLM-as-parser, credential rotation, reverse proxy binding,
  human approval gates, and transient retry.
- Wire pattern loading into architecture/pipeline.js based on task tags.
- Update architecture/orchestrator.js to load patterns and surface them in
  the system prompt.
- Update MEMORY.md, ARCHITECTURE.md, and CONTEXT.md to document the registry
  and record the decision.

CONTEXT.md

@@ -123,9 +123,11 @@ node architecture/orchestrator.js "your request here" --verbose
 - [x] Deploy validation layer with safety checks
 - [x] Deploy format locker with auto-fix
 - [x] Integrate all components via orchestrator
+- [x] Implement cross-project pattern registry for retrieval-augmented generalization
 
 ### Decisions Log
 | Date | Decision | Rationale |
 |------|----------|-----------|
+| 2026-08-06 | Create a centralized `patterns/` registry and wire it into `architecture/pipeline.js` | Captures recurring technical lessons across projects; enables agents to generalize known solutions to new tasks as the first concrete component of a continual-learning layer. |
 | 2026-07-03 | Create dedicated dev team | Need scalable capacity for multiple internal app projects |
 | 2026-07-03 | Python/FastAPI + HTMX stack | Matches existing skills, FastAPI's type safety, HTMX keeps frontend simple |