docs: refresh context files and add project URLS

BOUNDARIES.md

@@ -14,6 +14,7 @@ Rules that apply in **every** project unless explicitly overridden in a project-
 | **Force-push to main/master** | Unless Fränky explicitly requests it — warn first |
 | **Destructive prod actions** | No prod DB drops, migrations, or deploys without explicit approval (project may define exceptions) |
 | **Modify code on question-only requests** | Questions get answers — not drive-by fixes |
+| **Bypass edit blocks via shell** | If Plan Mode or any restriction blocks file edits, **stop** — never implement via `echo`, heredoc, `sed -i`, `tee`, etc. |
 
 ---
 
@@ -52,6 +53,15 @@ Rules that apply in **every** project unless explicitly overridden in a project-
   - Debug loops (same error, same failed fix repeated)
   - Required software missing and not installable in context
   - Conflicting instructions you cannot resolve
+  - **Plan Mode / read-only mode** blocks file edits — see below
+
+### Plan Mode
+
+When **Plan Mode** (or any agent mode) **blocks file edits**:
+
+- **Stop.** Do not implement via shell workarounds (`echo >>`, heredoc to file, `sed -i`, `tee`, `python -c` to write files, …)
+- Tell Fränky clearly: edits are blocked; switch to Agent mode or disable Plan Mode
+- **Wait** for his input — do not proceed with implementation
 
 ---
 
@@ -65,13 +75,15 @@ Rules that apply in **every** project unless explicitly overridden in a project-
 
 ## Project-Local Overrides
 
-Add project-specific boundaries below when copying into a project:
+Add project-specific boundaries below when copying into a project.
+
+<!-- Delete these examples when filling in:
 
-```markdown
 ## Project-Specific
 
 - (example) Never touch the legacy PHP monolith in /old/
 - (example) Auto-deploy to staging is OK; prod requires manual approval
-```
+
+-->
 
 When Fränky says *"don't do X here"*, the agent should propose the right file (`BOUNDARIES.md`, `SOUL.md`, or `AGENTS.md`) and persist it.