feat: add L2PS messaging client and protocol types

.mycelium/.gitignore

@@ -4,3 +4,4 @@
 *.db-shm
 # Temporary files
 *.tmp
+.linear/

.serena/project.yml

@@ -132,3 +132,17 @@ line_ending:
 # list of regex patterns which, when matched, mark a memory entry as read‑only.
 # Extends the list from the global configuration, merging the two lists.
 read_only_memory_patterns: []
+
+# advanced configuration option allowing to configure language server-specific options.
+# Maps the language key to the options.
+# Have a look at the docstring of the constructors of the LS implementations within solidlsp (e.g., for C# or PHP) to see which options are available.
+# No documentation on options means no options are available.
+ls_specific_settings: {}
+
+# list of regex patterns for memories to completely ignore.
+# Matching memories will not appear in list_memories or activate_project output
+# and cannot be accessed via read_memory or write_memory.
+# To access ignored memory files, use the read_file tool on the raw file path.
+# Extends the list from the global configuration, merging the two lists.
+# Example: ["_archive/.*", "_episodes/.*"]
+ignored_memory_patterns: []

AGENTS.md

@@ -135,7 +135,6 @@ history/
 
 For more details, see README.md and QUICKSTART.md.
 
-
 ## Project Management with Mycelium
 
 This project uses [Mycelium](https://github.com/tcsenpai/mycelium) (`myc`) for task and epic management.
@@ -211,3 +210,55 @@ When working on this project:
 3. Create tasks for new work: `myc task create --title "..." --description "..." --epic N`
 4. Mark tasks complete when done: `myc task close N`
 5. Use `--format json` for machine-readable output: `myc task list --format json`
+
+## Mental Frameworks for Mycelium Usage
+
+### 1. INVEST — Task Quality Gate
+
+Before creating or updating any task, validate it against these criteria.
+A task that fails more than one is not ready to be written.
+
+| Criterion | Rule |
+|---|---|
+| **Independent** | Can be completed without unblocking other tasks first |
+| **Negotiable** | The *what* is fixed; the *how* remains open |
+| **Valuable** | Produces a verifiable, concrete outcome |
+| **Estimable** | If you cannot size it, it is too vague or too large |
+| **Small** | If it spans more than one work cycle, split it |
+| **Testable** | Has an explicit, binary done condition |
+
+> If a task fails **Estimable** or **Testable**, convert it to an Epic and decompose.
+
+---
+
+### 2. DAG — Dependency Graph Thinking
+
+Before scheduling or prioritizing, model the implicit dependency graph.
+
+**Rules:**
+- No task moves to `in_progress` if it has an unresolved upstream blocker
+- Priority is a function of both urgency **and fan-out** (how many tasks does completing this one unlock?)
+- Always work the **critical path** first — not the task that feels most urgent
+
+**Prioritization heuristic:**
+```
+score = urgency + (blocked_tasks_count × 1.5)
+```
+
+When creating a task, explicitly ask: *"What does this block, and what blocks this?"*
+Set dependency links in Mycelium before touching status.
+
+---
+
+### 3. Principle of Minimal Surprise (PMS)
+
+Mycelium's state must remain predictable and auditable at all times.
+
+**Rules:**
+- **Prefer idempotent operations** — update before you create; never duplicate
+- **Check before write** — search for an equivalent item before creating a new one
+- **Always annotate mutations** — every status change, priority shift, or reassignment must carry an explicit `reason` field
+- **No orphan tasks** — every task must be linked to an Epic; every Epic to a strategic goal
+- Deletions are a last resort; prefer `cancelled` status with a reason
+
+> The state of Mycelium after any operation must be explainable to another agent with zero context.