Refresh agent instruction files

.claude/rules/workplan-convention.md

@@ -1,9 +1,28 @@
-# Workplan Convention
+## Workplan Convention (ADR-001)
 
-- Workplans live in `workplans/`.
-- Prefix new workplans with `IB-WP-`.
-- Use YAML frontmatter with `id`, `type`, `title`, `domain`, `repo`, `status`,
-  `owner`, `topic_slug`, `created`, and `updated`.
-- Include task blocks with stable IDs, status, priority, and optional State Hub
-  task IDs.
-- Keep workplans tied to this repo's PRD/FRS requirements and State Hub context.
+File location: `workplans/infospace-bench-WP-NNNN-<slug>.md`
+ID prefix: `INFOSPACE-WP`
+
+Work items originate as files in this repo **before** being registered in the hub.
+
+Canonical workplan/workstream frontmatter statuses are:
+`proposed`, `ready`, `active`, `blocked`, `backlog`, `finished`, `archived`.
+Use `proposed` for a newly drafted plan, `ready` after review against current
+repo state, and `finished` when implementation is complete. `stalled` and
+`needs_review` are derived health labels, not stored statuses.
+
+Closed workplans may be moved to `workplans/archived/` with a completion-date
+prefix: `YYMMDD-infospace-bench-WP-NNNN-<slug>.md`. The frontmatter id remains
+unchanged; the prefix is only for quick visual reference.
+
+Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
+`workplans/ADHOC-YYYY-MM-DD.md`, workstream slug `adhoc-YYYY-MM-DD`, and task ids
+`ADHOC-YYYY-MM-DD-T01`, `T02`, etc. Use adhocs only for low-risk work completed
+directly. Promote anything requiring analysis, design, approval, dependencies, or
+multiple planned phases into a normal workplan.
+
+Ecosystem todos from other agents arrive as `[repo:infospace-bench]` hub tasks —
+visible at session start. Pick one up by creating the workplan file, then registering
+the workstream.
+
+<!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->