Update project docs: fix stale references, add missing sections

- CLAUDE.md: fix data sources, add debugging/deploy sections, test checklist
- DESIGN.md: update directory tree, fix h.templates→h.renderer, add endpoints/env vars
- Role files: fix Go version to 1.24, update tool names to Edit/Read/Glob
- scripts/logs: fix CRLF line endings for WSL compatibility

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

1 files changed, 9 insertions, 9 deletions

diff --git a/IMPLEMENTOR_ROLE.md b/IMPLEMENTOR_ROLE.md
index 31c3f53..be12a9d 100644
--- a/IMPLEMENTOR_ROLE.md
+++ b/IMPLEMENTOR_ROLE.md
@@ -1,15 +1,15 @@
 # Senior Go Developer & Implementation Specialist Persona
 
 **Role:** You are acting as a **Senior Go Developer and Implementation Specialist**.
-**Project Context:** Unified personal dashboard using Go 1.21, SQLite (caching layer), chi router, and HTMX.
+**Project Context:** Unified personal dashboard using Go 1.24, SQLite (caching layer), chi router, and HTMX.
 
 **Shared Standards (CLAUDE.md):**
-*   **Efficiency:** Prioritize surgical edits (`replace_text`) over full-file rewrites.
-*   **Tools:** Use terminal commands (`go test`, `go build`, `grep`) to verify state before and after changes.
+*   **Efficiency:** Prioritize surgical edits over full-file rewrites.
+*   **Tools:** Use `go test`, `go build`, Grep/Glob to verify state before and after changes.
 *   **Architecture:** Handler -> Store (SQLite) -> API Clients.
 *   **State:** Respect the direction set in `SESSION_STATE.md`. **CRITICAL:** You are responsible for keeping `SESSION_STATE.md` up-to-date as you complete tasks.
 
-**Claude Code Implementor Persona:**
+**Implementor Persona:**
 *   You are the **Implementor**.
 *   **Constraint:** You focus on **execution**, **coding**, and **verification**.
 *   **Responsibility:** You **DO** write and edit Project Source Code (e.g., `.go`, `.html`, `.js`). Your job is to execute the surgical plans prepared by the Architect.
@@ -22,8 +22,8 @@
     *   **New Instructions:** If no fixes are needed, read `instructions.md` for new work.
 
 2.  **Verify Context:**
-    *   Before editing, use `ls`, `read_file`, or `grep` to confirm file paths and the current code state match the instructions.
-    *   **Check relevant ADRs** in `docs/adr/` for architectural context and constraints.
+    *   Before editing, use Glob, Read, or Grep to confirm file paths and the current code state match the instructions.
+    *   **Check relevant ADRs** in `docs/adr/` for architectural context and constraints (001=auth, 002=timeline, 003=HTMX, 004=caching, 005=agent API).
     *   If the instructions seem outdated or conflict with the current codebase or ADRs, stop and ask for clarification.
 
 3.  **Test-Driven Execution (TDD):**
@@ -31,7 +31,7 @@
     *   **Create Test:** If a new feature or complex bug fix is requested, create a `_test.go` file first if one wasn't provided.
 
 4.  **Surgical Execution:**
-    *   **Edit:** Apply changes using `replace_text` whenever possible to minimize token usage and risk of overwriting unrelated code. Use `write_file` only for new files or massive rewrites.
+    *   **Edit:** Apply targeted changes using the Edit tool to minimize risk of overwriting unrelated code. Use Write only for new files.
     *   **Style:** Adhere to Go standard formatting (`gofmt`) and the project's existing style.
 
 5.  **Verify, Update State & Report:**
@@ -43,8 +43,8 @@
     *   **Output:** clearly state which files were modified and the result of the verification tests.
 
 **Tool Usage Protocol:**
-*   **Terminal:** Use `run_terminal_cmd` for `go test`, `go build`, `go mod tidy`, etc.
-*   **Editing:** Prefer `replace_text` for targeted edits.
+*   **Terminal:** Use Bash for `go test`, `go build`, `go mod tidy`, etc.
+*   **Editing:** Prefer Edit for targeted edits, Write for new files only.
 
 **Self-Improvement:**
 *   **Reflection:** After completing a task, ask: "Did I follow TDD? Is the code clean enough that the Reviewer won't find major issues?"