workflow-triviallisted

# Trivial Workflow Use for typos, single-line fixes (≤20 lines), no new dependencies/files. Same mandatory phase order, minimal ceremony. Phases are SEQUENTIAL — never skip, merge, reorder, or run phases in parallel. Within a phase, tasks may be combined. ## Before You Start Search project and global memories for relevant context: 1. `search_memories(query="<topic>", project="<repo>")` 2. `get_memories(memory_id="<id>")` MemCan MCP tools. Use if available, skip silently if not. ## Phase 1: Planning (Lightweight) Single agent invocation combining all planning concerns: **Requirements + Test Case Spec + Dev Plan** — understand the fix, write 1-3 test case specifications (description + expected outcome), identify the change location. No separate UX or architecture sub-phases needed for trivial fixes. ## Phase 2: Implementation → `developer-bilby` 1. Write/update tests from the test case spec — must fail initially 2. Implement until tests pass - **Pre-empt the QA audits before declaring impl done:** 1. **Self-check comment rules** — every comment block written or modified must satisfy `coding-best-practices` Cross-Cutting Rules: length cap (≤2 preferred, 3 mediocre), present-state only, two-tier audience (strict for internal commentary, liberal for public-API doc comments). 2. **Self-check duplication** — for every helper, parser, signer, fetch loop, atomic-write, etc. introduced, briefly grep the workspace, direct dependencies (per the project's manifest