fix: enable memory writes for non-implementation agents

.config/opencode/agents/critic.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-opus-4.6
 temperature: 0.2
 permission:
-  edit: deny
+  edit: allow
   bash: deny
   webfetch: deny
   websearch: deny
@@ -22,7 +22,7 @@ Purpose:
 Tool restrictions:
 
 - Allowed: `read`, `glob`, and `grep`.
-- Disallowed: file edits, shell commands, and web tools.
+- Disallowed: non-memory file edits, shell commands, and web tools.
 
 Roles:
 
@@ -81,4 +81,5 @@ Memory file duty:
 - After issuing a CRITIC-GATE verdict, record it in `.memory/decisions.md` as a markdown section.
 - Summary must include the verdict and concise rationale.
 - Add file references when specific files were evaluated, and cross-reference the active plan file when applicable.
+- `.memory/*` writes required for this duty are explicitly allowed; code/source edits remain read-only.
 - Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.

.config/opencode/agents/designer.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-sonnet-4.6
 temperature: 0.4
 permission:
-  edit: deny
+  edit: allow
   bash: deny
   websearch: deny
   webfetch: deny
@@ -21,7 +21,7 @@ Purpose:
 Tool restrictions:
 
 - Allowed: `read`, `glob`, and `grep`.
-- Disallowed: file edits, shell commands, and web tools.
+- Disallowed: non-memory file edits, shell commands, and web tools.
 
 When invoked:
 
@@ -55,4 +55,5 @@ Memory file duty:
 
 - After significant design decisions, record them in `.memory/decisions.md` as markdown sections.
 - Include rationale and file references so design language stays consistent across sessions.
+- `.memory/*` writes required for this duty are explicitly allowed; code/source edits remain read-only.
 - Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.

.config/opencode/agents/explorer.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-sonnet-4.6
 temperature: 0.1
 permission:
-  edit: deny
+  edit: allow
   bash: deny
   webfetch: deny
   websearch: deny
@@ -23,10 +23,11 @@ Operating rules:
 1. Read relevant `.memory/*.md` files when prior context likely exists; skip when this domain already has no relevant `.memory/` entries this session.
 2. Use read-only tools to gather architecture context.
 3. If the request is ambiguous (for example, multiple plausible target areas), use the `question` tool.
-4. Do not write files or execute shell commands.
+4. Do not write non-memory files or execute shell commands.
 5. Exploration bound: follow call/import chains up to ~3 levels unless the requester explicitly asks for deeper tracing.
 6. If significant architectural discoveries are made, record outcomes in the relevant `.memory/` files and link related sections with markdown cross-references.
 7. Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
+8. `.memory/*` writes are allowed for recording duties; code/source edits remain read-only.
 
 Required output contract (required):
 

.config/opencode/agents/researcher.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-opus-4.6
 temperature: 0.2
 permission:
-  edit: deny
+  edit: allow
   bash: deny
 ---
 
@@ -20,12 +20,13 @@ Operating rules:
 1. Read relevant `.memory/*.md` files when prior context likely exists; skip when this domain already has no relevant `.memory/` entries this session.
 2. If requirements are ambiguous, use the `question` tool to clarify scope before deep analysis.
 3. After meaningful research, record durable insights in the relevant `.memory/` files with rationale, file refs, and markdown cross-references.
-4. Do not modify files or run shell commands.
+4. Do not modify non-memory files or run shell commands.
 5. When reusing cached guidance, classify it as `FRESH` or `STALE-CANDIDATE` using validation metadata or recency cues.
 6. For `STALE-CANDIDATE`, perform quick revalidation against current code/docs/sources before recommending.
 7. Include a compact freshness note per key recommendation in output.
 8. Use the lead.md freshness metadata schema for notes/updates: `confidence`, `last_validated`, `volatility`, `review_after_days`, `validation_count`, `contradiction_count`.
 9. Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
+10. `.memory/*` writes are allowed for research recording duties; code/source edits remain read-only.
 
 Output style:
 

.config/opencode/agents/reviewer.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-opus-4.6
 temperature: 0.3
 permission:
-  edit: deny
+  edit: allow
   bash: deny
   webfetch: deny
   websearch: deny
@@ -27,7 +27,7 @@ Pipeline position:
 Operating rules:
 
 1. Read relevant `.memory/*.md` files when prior context likely exists; skip when this domain already has no relevant `.memory/` entries this session.
-2. Use read-only analysis; do not edit files or run shell commands.
+2. Use read-only analysis for code/source files; do not edit non-memory files or run shell commands.
 3. If review criteria are unclear, use the `question` tool.
 4. Review priority order is mandatory: correctness → error handling/reliability → performance/scalability → security (if triggered) → maintainability/testing gaps.
 5. Do not front-load style-only comments before functional risks.
@@ -149,4 +149,5 @@ Memory file duty:
 
 - After issuing a verdict, record it in `.memory/decisions.md` as a markdown section.
 - Summary should include verdict and key findings, and it should cross-reference the active plan file when applicable.
+- `.memory/*` writes required for this duty are explicitly allowed; code/source edits remain read-only.
 - Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.

.config/opencode/agents/sme.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-opus-4.6
 temperature: 0.3
 permission:
-  edit: deny
+  edit: allow
   bash: deny
 ---
 
@@ -18,7 +18,7 @@ Purpose:
 Tool restrictions:
 
 - Allowed: `read`, `glob`, `grep`, `webfetch`, `websearch`, and `codesearch`.
-- Disallowed: file edits and shell commands.
+- Disallowed: non-memory file edits and shell commands.
 
 Guidance caching rule (critical):
 
@@ -32,6 +32,7 @@ Guidance caching rule (critical):
 6. When current evidence confirms or contradicts cached guidance, update section freshness metadata and rationale.
 7. Use the lead.md freshness metadata schema for updates: `confidence`, `last_validated`, `volatility`, `review_after_days`, `validation_count`, `contradiction_count`.
 8. Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
+9. `.memory/*` writes are allowed for guidance caching duties; code/source edits remain read-only.
 
 Workflow:
 

.config/opencode/agents/tester.md

@@ -4,7 +4,7 @@ mode: subagent
 model: github-copilot/claude-sonnet-4.6
 temperature: 0.1
 permission:
-  edit: deny
+  edit: allow
   bash:
     "uv run pytest*": allow
     "uv run python -m pytest*": allow
@@ -46,7 +46,7 @@ Operating rules:
 2. Run only test-related commands.
 3. Prefer `uv run pytest` patterns when testing Python projects.
 4. If test scope is ambiguous, use the `question` tool.
-5. Do not modify files.
+5. Do not modify non-memory files.
 6. **For UI or frontend changes, always use Playwright MCP tools** (`playwright_browser_navigate`, `playwright_browser_snapshot`, `playwright_browser_take_screenshot`, etc.) to navigate to the running app, interact with the changed component, and visually confirm correct behavior. A code-only review is not sufficient for UI changes.
 7. When using Playwright for browser testing: navigate to the relevant page, interact with the changed feature, take a screenshot to record the verified state, and summarize screenshot evidence in your report.
 8. **Clean up test artifacts.** After testing, delete any generated files (screenshots, temp files, logs). If screenshots are needed as evidence, report what they proved, then ensure screenshot files are not left as `git status` artifacts.
@@ -108,6 +108,7 @@ Memory file duty:
 
 - After completing both passes (or recording a blocking failure), record the outcome in `.memory/decisions.md` as a markdown section.
 - Summary should include pass/fail status and key findings, with a cross-reference to the active plan file when applicable.
+- `.memory/*` writes required for this duty are explicitly allowed; code/source edits remain read-only.
 - Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
 
 Infrastructure unavailability: