Rename kanban board paths to workitems

Author: rcarmo

README.md

@@ -106,6 +106,20 @@ bun run build             # recompile TypeScript (optional — Bun runs .ts dire
 
 See [docs/install-from-repo.md](docs/install-from-repo.md) for scope and caveats.
 
+### Repo ownership rules
+
+The repo root is the maintainer/operator boundary; `runtime/` is the packaged implementation boundary.
+
+- `workitems/` — canonical project work-item store for this repo
+- `docs/` — repo/operator/architecture/install documentation
+- `runtime/docs/` — packaged/runtime-facing documentation only
+- `scripts/` — repo-level dev/operator entrypoints and audits
+- `runtime/scripts/` — packaged helper scripts that ship with piclaw
+- `artifacts/` — durable repo-level evidence and audit outputs
+- runtime-generated build/test output remains under `runtime/` until the later generated-output containment batch lands
+
+Intentional exceptions remain intentionally named `kanban` when they describe the visual/editor surface rather than the repo work-item store — for example `kanban-management` and `*.kanban.md`.
+
 ### Build from source
 
 > [!NOTE]
@@ -193,7 +207,7 @@ Then:
 > If `/model` shows no available models, finish `pi /login` first.
 
 > [!NOTE]
-> Provider login is currently **terminal-first**. Chat-level `/login` passthrough is still tracked in kanban.
+> Provider login is currently **terminal-first**. Chat-level `/login` passthrough is still tracked in `workitems/40-review/login-command-passthrough.md`.
 
 ## Web UI
 

docs/autoresearch-lite-design.md

@@ -440,4 +440,4 @@ Do **not** copy from upstream:
 - `docs/runtime-flows.md`
 - `docs/extension-ui-contract.md`
 - `docs/web-pane-extensions.md`
-- `kanban/10-next/timeline-launched-floating-generative-widget-pane.md`
+- `workitems/10-next/timeline-launched-floating-generative-widget-pane.md`

docs/broad-filesystem-reorg-map-2026-03-28.md

@@ -330,10 +330,10 @@ output paths.
 
 ## Related tickets
 
-- `kanban/20-doing/plan-broad-filesystem-reorg-from-audit.md`
-- `kanban/40-review/audit-project-filesystem-layout.md`
-- `kanban/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
-- `kanban/10-next/clarify-root-vs-runtime-ownership-boundaries.md`
-- `kanban/10-next/rationalize-runtime-generated-output-layout.md`
-- `kanban/10-next/namespace-internal-extensions-and-skills-paths.md`
-- `kanban/10-next/group-web-channel-flat-files.md`
+- `workitems/20-doing/plan-broad-filesystem-reorg-from-audit.md`
+- `workitems/40-review/audit-project-filesystem-layout.md`
+- `workitems/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
+- `workitems/10-next/clarify-root-vs-runtime-ownership-boundaries.md`
+- `workitems/10-next/rationalize-runtime-generated-output-layout.md`
+- `workitems/10-next/namespace-internal-extensions-and-skills-paths.md`
+- `workitems/10-next/group-web-channel-flat-files.md`

docs/filesystem-layout-audit-2026-03-28.md

@@ -105,13 +105,13 @@ And the UI/test adjacency is also good:
 
 Board lanes are explicit and conventional:
 
-- `kanban/00-inbox/`
-- `kanban/10-next/`
-- `kanban/20-doing/`
-- `kanban/30-blocked/`
-- `kanban/40-review/`
-- `kanban/50-done/`
-- `kanban/_templates/`
+- `workitems/00-inbox/`
+- `workitems/10-next/`
+- `workitems/20-doing/`
+- `workitems/30-blocked/`
+- `workitems/40-review/`
+- `workitems/50-done/`
+- `workitems/_templates/`
 
 That structure is clear, but the **name** `kanban/` now undersells the fact that this directory is the canonical project work-item store rather than just a board view.
 
@@ -217,8 +217,8 @@ are not governed by one obvious placement rule.
 
 Two layout concerns are already captured and should be treated as existing roadmap items rather than re-audited indefinitely:
 
-- `kanban/10-next/group-web-channel-flat-files.md`
-- `kanban/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
+- `workitems/10-next/group-web-channel-flat-files.md`
+- `workitems/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
 
 That is good news: not every audit finding requires a new ticket.
 
@@ -266,13 +266,13 @@ To avoid churn, these should be treated as acceptable unless fresh evidence says
 
 ### Already existing
 
-- `kanban/10-next/group-web-channel-flat-files.md`
-- `kanban/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
+- `workitems/10-next/group-web-channel-flat-files.md`
+- `workitems/10-next/rename-project-kanban-to-workitems-and-update-skilling.md`
 
 ### New from this audit
 
-- `kanban/10-next/clarify-root-vs-runtime-ownership-boundaries.md`
-- `kanban/10-next/rationalize-runtime-generated-output-layout.md`
+- `workitems/10-next/clarify-root-vs-runtime-ownership-boundaries.md`
+- `workitems/10-next/rationalize-runtime-generated-output-layout.md`
 
 ## Bottom line
 

docs/stage1-board-rename-reference-inventory-2026-03-28.md

@@ -97,4 +97,4 @@ A Stage 1 autoresearch run should use this inventory to avoid two common mistake
 
 - `docs/stage1-broad-filesystem-reorg-steplist-2026-03-28.md`
 - `docs/stage1-broad-filesystem-reorg-autoresearch-prompt-2026-03-28.md`
-- `kanban/20-doing/execute-stage1-board-rename-and-boundary-framing.md`
+- `workitems/20-doing/execute-stage1-board-rename-and-boundary-framing.md`

docs/stage1-broad-filesystem-reorg-autoresearch-prompt-2026-03-28.md

@@ -7,7 +7,7 @@ broad filesystem reorg.
 
 Work the Stage 1 broad filesystem reorg batch from:
 
-- `kanban/20-doing/execute-stage1-board-rename-and-boundary-framing.md`
+- `workitems/20-doing/execute-stage1-board-rename-and-boundary-framing.md`
 - `docs/stage1-broad-filesystem-reorg-steplist-2026-03-28.md`
 - `docs/broad-filesystem-reorg-map-2026-03-28.md`
 

docs/stage1-broad-filesystem-reorg-steplist-2026-03-28.md

@@ -33,7 +33,7 @@ Before changing anything:
 - the current source of truth docs exist:
   - `docs/filesystem-layout-audit-2026-03-28.md`
   - `docs/broad-filesystem-reorg-map-2026-03-28.md`
-  - `kanban/20-doing/plan-broad-filesystem-reorg-from-audit.md`
+  - `workitems/20-doing/plan-broad-filesystem-reorg-from-audit.md`
 
 ## Primary deliverables
 
@@ -108,7 +108,7 @@ Expected touch points include:
 - helper/render code
 - path constants
 - stage/review lane documentation
-- scaffolding under `skel/kanban/` (decide whether this also becomes `skel/workitems/` in the same step)
+- scaffolding under `skel/workitems/` (decide whether this also becomes `skel/workitems/` in the same step)
 
 ### Step 5 — handle skill/helper naming carefully
 

docs/tools-and-skills.md

@@ -76,7 +76,7 @@ Each skill keeps its script alongside its `SKILL.md` for portability. Current se
 | `bootstrap-container` | Validate required tools and install missing dependencies |
 | `extension-design` | Design and audit Pi extensions safely |
 | `extension-troubleshoot` | Diagnose and fix extension issues (imports, DB init, watcher perms) |
-| `kanban-management` | Manage kanban board: ideation, triage, quality scoring, definition-of-done tracking |
+| `kanban-management` | Manage the project workitems board: ideation, triage, quality scoring, definition-of-done tracking |
 | `adaptive-cards-authoring` | Author Adaptive Cards for structured web interactions |
 | `close-of-day` | End-of-day sweep: situate, backup, timeline cleanup, daily-notes summarisation |
 | `export-timeline-pdf` | Export a chat timeline to PDF via Playwright |
@@ -85,6 +85,8 @@ Each skill keeps its script alongside its `SKILL.md` for portability. Current se
 | `timeline-cleanup` | Delete low-value timeline messages by keyword patterns |
 | `proxmox-management` | Manage Proxmox VM lifecycle, USB mapping passthrough, and backup-restore moves |
 
+`kanban-management` intentionally keeps its public name for now, but repo-local board paths in this project now live under `workitems/`. Visual/editor semantics such as `*.kanban.md` remain intentionally named.
+
 The packaged Proxmox helper now lives at `runtime/scripts/proxmox.ts` and can be invoked from the repo with:
 
 ```bash

docs/turn-mechanism-audit.md

@@ -890,7 +890,7 @@ User clicks Steer button on queue stack item
    Stored as a terminal bot message and broadcast via `agent_response`.
 
 2. ~~**183 MB session file**~~ **Tracked**: Created kanban ticket
-   `kanban/00-inbox/session-file-rotation.md` covering size monitoring, rotation,
+   `workitems/00-inbox/session-file-rotation.md` covering size monitoring, rotation,
    archival, and queue validation during rotation. Includes acceptance criteria
    to verify queued messages are preserved and that rotation does not occur
    during inflight turns.