agent-boardlisted

# Agent Board Use the local HTTP API at `http://localhost:8080`. Use direct `curl` requests; Agent Board has no CLI and stores no implicit agent context. ## Rules - Treat the API as the only source of task state. Never read or edit the SQLite database. - Provide every project ID, task ID, and session ID explicitly. Never infer ownership. - Use one stable, non-empty session ID for the full implementation attempt. - Claim only work that can be started immediately. Taking a task means claiming it and continuing its implementation, not stopping after the claim. - Inspect a task and its event history before changing code. - Keep lifecycle changes and progress notes in Agent Board. Do not create local context files. - Do not report Agent Board as unavailable from one sandboxed connection failure. Follow the service availability diagnosis before concluding that the service is down. - If a claim returns `409`, refresh the task list and choose other available work. - Use the owning session for edits, release, and completion of an `in_progress` task. - Act as the coordinator for the task. Own its board session, verification, commit, and lifecycle. - Delegate bounded implementation work to one or more executor subagents. Executors must not claim, transition, release, or complete the task, and must not commit. - Prefer exactly one final commit per task. Do not make intermediate or partial commits. Preserve unrelated user changes and exclude them from the task commit. ## Coordinator w