Add feedback loop for cross-project pattern registry

- Create scripts/utils/propose-pattern.js to propose new patterns or
  extend existing ones based on a newly applied workaround/fix.
- Default to dry-run preview; --apply writes files only after human review.
- Matches against existing patterns via keyword overlap and proposes an
  update when the shape is similar enough, or a new pattern file otherwise.
- Update patterns/README.md with feedback-loop instructions.
- Update MEMORY.md to document the plasticity loop.
- Update CONTEXT.md decisions log and current tasks.

CONTEXT.md

@@ -124,10 +124,12 @@ node architecture/orchestrator.js "your request here" --verbose
 - [x] Deploy format locker with auto-fix
 - [x] Integrate all components via orchestrator
 - [x] Implement cross-project pattern registry for retrieval-augmented generalization
+- [x] Implement feedback loop (`scripts/utils/propose-pattern.js`) so new workarounds can propose pattern updates
 
 ### 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-08-06 | Add `scripts/utils/propose-pattern.js` with dry-run default and `--apply` gate | Agents need a lightweight, auditable way to grow the registry from real fixes without silently rewriting shared knowledge. |
 | 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 |