chore: claw-code progress on #232

Refs #232

.claw/sessions/session-1775428216801-0.jsonl

@@ -0,0 +1,2 @@
+{"created_at_ms":1775428216801,"session_id":"session-1775428216801-0","type":"session_meta","updated_at_ms":1775428216801,"version":1}
+{"message":{"blocks":[{"text":"You are Code Claw running as the Gitea user claw-code.\n\nRepository: Timmy_Foundation/timmy-config\nIssue: #232 — [SMOKE] Add Code Claw local state dirs to .gitignore\nBranch: claw-code/issue-232\n\nRead the issue and recent comments, then implement the smallest correct change.\nYou are in a git repo checkout already.\n\nIssue body:\n## What\nAdd Code Claw local state dirs to `.gitignore` so local Qwen/OpenRouter runs do not pollute repo status.\n\n## Acceptance criteria\n- add `.claw-qwen36-openrouter/`\n- add `.claw-qwen36-gitea/`\n- no other repo changes\n\n\nRecent comments:\n🟠 Code Claw (OpenRouter qwen/qwen3.6-plus:free) picking up this issue via 15-minute heartbeat.\n\nTimestamp: 2026-04-05T22:26:31Z\n\nRules:\n- Make focused code/config/doc changes only if they directly address the issue.\n- Prefer the smallest proof-oriented fix.\n- Run relevant verification commands if obvious.\n- Do NOT create PRs yourself; the outer worker handles commit/push/PR.\n- If the task is too large or not code-fit, leave the tree unchanged.\n","type":"text"}],"role":"user"},"type":"message"}

code-claw-delegation.md

@@ -1,91 +0,0 @@
-# Code Claw delegation
-
-Purpose:
-- give the team a clean way to hand issues to `claw-code`
-- let Code Claw work from Gitea instead of ad hoc local prompts
-- keep queue state visible through labels and comments
-
-## What it is
-
-Code Claw is a separate local runtime from Hermes/OpenClaw.
-
-Current lane:
-- runtime: local patched `~/code-claw`
-- backend: OpenRouter
-- model: `qwen/qwen3.6-plus:free`
-- Gitea identity: `claw-code`
-- dispatch style: assign in Gitea, heartbeat picks it up every 15 minutes
-
-## Trigger methods
-
-Either of these is enough:
-- assign the issue to `claw-code`
-- add label `assigned-claw-code`
-
-## Label lifecycle
-
-- `assigned-claw-code` — queued
-- `claw-code-in-progress` — picked up by heartbeat
-- `claw-code-done` — Code Claw completed a pass
-
-## Repo coverage
-
-Currently wired:
-- `Timmy_Foundation/timmy-home`
-- `Timmy_Foundation/timmy-config`
-- `Timmy_Foundation/the-nexus`
-- `Timmy_Foundation/hermes-agent`
-
-## Operational flow
-
-1. Team assigns issue to `claw-code` or adds `assigned-claw-code`
-2. launchd heartbeat runs every 15 minutes
-3. Timmy posts a pickup comment
-4. worker clones the target repo
-5. worker creates branch `claw-code/issue-<num>`
-6. worker runs Code Claw against the issue context
-7. if work exists, worker pushes and opens a PR
-8. issue is marked `claw-code-done`
-9. completion comment links branch + PR
-
-## Logs and files
-
-Local files:
-- heartbeat script: `~/.timmy/uniwizard/codeclaw_qwen_heartbeat.py`
-- worker script: `~/.timmy/uniwizard/codeclaw_qwen_worker.py`
-- launchd job: `~/Library/LaunchAgents/ai.timmy.codeclaw-qwen-heartbeat.plist`
-
-Logs:
-- heartbeat log: `/tmp/codeclaw-qwen-heartbeat.log`
-- worker log: `/tmp/codeclaw-qwen-worker-<issue>.log`
-
-## Best-fit work
-
-Use Code Claw for:
-- small code/config/doc issues
-- repo hygiene
-- isolated bugfixes
-- narrow CI and `.gitignore` work
-- quick issue-driven patches where a PR is the desired output
-
-Do not use it first for:
-- giant epics
-- broad architecture KT
-- local game embodiment tasks
-- complex multi-repo archaeology
-
-## Proof of life
-
-Smoke-tested on:
-- `Timmy_Foundation/timmy-config#232`
-
-Observed:
-- pickup comment posted
-- branch `claw-code/issue-232` created
-- PR opened by `claw-code`
-
-## Notes
-
-- Exact PR matching matters. Do not trust broad Gitea PR queries without post-filtering by branch.
-- This lane is intentionally simple and issue-driven.
-- Treat it like a specialized intern: useful, fast, and bounded.