fix: enable memory writes for non-implementation agents

.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: