@caddis/cli 0.4.65 → 0.4.67

package/bundles/antigravity-plugin/skills/catchup/SKILL.md

@@ -70,6 +70,10 @@ on is worse than one sentence admitting there is nothing to recap.
 
 ## Workstreams and open work
 
+Open items live in three stores (the 3-store model): this session's tasks (saved at handoff to
+`.caddis/relay/<name>.tasks.md`), the open parking-lot items (`/caddis:park`), and the roadmap and the plan
+Tracker for the order of work. Catchup reads those three and nothing else.
+
 **No argument:** this is the last step of the catchup procedure above, not a separate one.
 After the list, add the workstream index and the open work:
 0. The roadmap on origin is the order of work. List the roadmaps, then show each one's status line:
@@ -82,10 +86,8 @@ After the list, add the workstream index and the open work:
 1. Refresh and show the index: `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_workstreams.py" render-index`,
    then display `.caddis/relay.md`. If it refuses a legacy `.caddis/relay.md`, display that file
    as it is and suggest `/handoff`, which migrates it.
-2. Show open work for the current workstream:
-   ```
-   python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_todo.py" open-work
-   ```
+2. Show the open parking-lot items, the durable backlog: follow `/caddis:park list` (List mode). Print its table
+   and its counts; if the repo has no `.caddis/parking-lot/`, say `No parking-lot items.` and go on.
 Before saying `Nothing is parked.`, check for an old `/digress` stack: if `.caddis/workstreams.json`
 exists, run `caddis_workstreams.py migrate-legacy` (it keeps a backup and reports conflicts
 instead of overwriting), then show the index again. Only with no relays and no old stack, state:
@@ -97,7 +99,11 @@ instead of overwriting), then show the index again. Only with no relays and no o
    `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_relay_git.py" fetch <name>`. It reads only
    `refs/caddis/relay/<name>`, never checks out or merges, and refuses to replace a different local
    relay. Pass `--replace` only if the user confirms the local one may be overwritten.
-3. Restate where you were and resume the workstream.
+3. Load the saved tasks, the same way `/caddis:fleet-open` does: if `.caddis/relay/<name>.tasks.md` exists (table
+   `| Old # | Status | Subject |`), make one `TaskCreate` per row with the Subject as its subject, then a
+   `TaskUpdate` to `in_progress` for each row with Status `in_progress`. No file means 0 tasks. If this session
+   already holds tasks (`TaskList`), do not create a row whose subject is already there. Count them.
+4. Restate where you were and resume the workstream; name the number of tasks you loaded.
 
 ## Rules
 - **Never** run a destructive or history-rewriting git action (no `git checkout`, `git reset`, `git stash`,

package/bundles/antigravity-plugin/skills/cloud-phases/SKILL.md

@@ -37,10 +37,10 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 - **On `SHARED: no`,** do the steps as written, in this checkout.
 - **On `SHARED: yes`,** never move this checkout. Leave its changes as they are, and report them. Instead:
-  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name>)" <branch>`, then
+  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name> --record --purpose "rebase <name>")" <branch>`, then
     `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
   - **Pull a branch to test it:** `git fetch origin`, then
-    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name>)" origin/<branch>` (for the default branch,
+    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
     `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
   - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
     `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
@@ -50,7 +50,8 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 `<name>` is the branch name with each `/` written as `-`. `caddis_worktree_root.py` prints the path of a new worktree:
 `$CADDIS_WORKTREE_ROOT/<repo>/<short-name>`, else `<parent of the main checkout>/.worktrees/<repo>/<short-name>`. Never `%TEMP%`: Windows
-cleanup can empty it. The caddis guard checks only the `Shared checkout: yes` line in
+cleanup can empty it. `--record --purpose "<why>"` also writes the path to this
+session's created list (`caddis_created.py`), so `/handoff` can remove the worktree later. The caddis guard checks only the `Shared checkout: yes` line in
 `AGENTS.md`, not a dirty tree: with that line, it asks before a tree move, and denies it in a headless session.
 <!-- /checkout-safety -->
 

package/bundles/antigravity-plugin/skills/feature-plan/SKILL.md

@@ -375,7 +375,7 @@ A `risk: high` phase gets two independent review runs: run by the roadmap/plan r
 
 Small work that does not meet a trigger skips its block.
 
-**Trigger: Always.** Add one open-work row for the plan in `.caddis/open-work.md`. Set its cells with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_rows.py" set --file <open-work.md> --id <row id> --col Status=todo`, never with a regex edit.
+**Trigger: Always.** The plan's own Tracker is its row of record: give every phase one Tracker row, and when the repo has a roadmap (`caddis_roadmap.py list` prints a slug), name the plan in a roadmap milestone through `/caddis:roadmap` (a docs PR). Work the plan defers on purpose goes to a parking-lot item with `/caddis:park`, and its Tracker row names the file. Open items live in three stores (the 3-store model): the session task list, parking-lot items, and the roadmap and Tracker. The older to-do and repo-backlog stores are retired: do not create them.
 
 **Trigger: The plan records a decision.** Record it with `/caddis:decide`.
 

package/bundles/antigravity-plugin/skills/handoff/SKILL.md

@@ -33,13 +33,14 @@ them into its commit, so check first, before Step 1.
    `WORKTREE: <path>`. That worktree is this session's only; no other session's edits can enter it.
    Then, in the steps below:
    - Step 1: tell the `knowledge-transfer` subagent to edit files ONLY under the `WORKTREE:` path.
-   - Step 3, point 4: run `caddis_rows.py set --file <worktree>/.caddis/open-work.md ...`, and make the
-     plan's Tracker edit in `<worktree>/.caddis/plans/<feature>.md`, not in this checkout.
+   - Step 3, point 4: make the plan's Tracker edit in `<worktree>/.caddis/plans/<feature>.md`, and write
+     any new parking-lot item under `<worktree>/.caddis/parking-lot/`, not in this checkout.
    - Step 4: skip `caddis_tidy.py --apply` (report `skipped: shared checkout`).
-   - Step 6: skip `caddis_todo.py reconcile` (report `skipped: shared checkout`; it writes tracked
-     `.caddis/todo-list/` files and has no worktree option).
+   - Step 6: retired; nothing to skip (row 8 reports `skipped: retired (see the 3-store model)`).
    - Step 6b: skip `session_state.py prune` (report `skipped: shared checkout`).
    - Step 6c: run `--reindex` in the worktree (it edits the tracked `DOC-MAP.md`).
+   - Step 6d: runs as written. It never writes a file in this checkout; it only removes worktrees and
+     scratch folders this session recorded.
    - The relay stays in this checkout: `.caddis/relay/` is local and gitignored.
    After Step 6c, run:
    ```
@@ -52,25 +53,29 @@ them into its commit, so check first, before Step 1.
 
 ## Checklist
 The handoff is a fixed checklist. Every row ends as `done`, `skipped: <reason>` or `failed: <error>`, and
-Step 8 prints all 13 in this order. Never drop a row from the report, even when its step did not apply.
+Step 8 prints all 14 in this order. Never drop a row from the report, even when its step did not apply.
+Rows 3 and 8 are retired (the 3-store model, 21 Oct 2026): they stay in the list so the row numbers do not
+move for a fleet that mixes caddis versions, and each always reports
+`skipped: retired (see the 3-store model)`. A later release removes them with their scripts.
 
 | # | Row | What it is | Shared checkout (Step 0) |
 |---|---|---|---|
 | 1 | `knowledge-transfer` | Step 1 | edits only in the Step 0 worktree |
 | 2 | `plan-tracker` | the plan's Tracker row (Rules) | edit in the Step 0 worktree |
-| 3 | `open-work-row` | Step 3, point 4: `caddis_rows.py set` | `--file <worktree>/...` |
+| 3 | `open-work-row` | retired: always `skipped: retired (see the 3-store model)` | never runs |
 | 4 | `relay` | Step 3: the relay, written from scratch with current state only | the relay is local; runs |
 | 5 | `tasks-file` | Step 3c | runs |
 | 6 | `kb-index` | Step 6c: refresh the KB index | in the Step 0 worktree |
 | 7 | `violations-report` | Step 6c: report standing violations, each with a one-line fix command | runs (report only) |
-| 8 | `todo-reconcile` | Step 6: `caddis_todo.py reconcile` | `skipped: shared checkout` |
+| 8 | `todo-reconcile` | retired: always `skipped: retired (see the 3-store model)` | never runs |
 | 9 | `usage-record` | Step 6b: `session_state.py usage` | runs |
 | 10 | `tidy-apply` | Step 4: `caddis_tidy.py --apply` | `skipped: shared checkout` |
 | 11 | `state-prune` | Step 6b: `session_state.py prune` | `skipped: shared checkout` |
 | 12 | `prune-list` | Step 6b: `caddis_tidy.py --prune`, list only | runs (lists, never applies) |
 | 13 | `handover-check` | Step 5 | runs |
+| 14 | `own-cleanup` | Step 6d: `caddis_created.py cleanup --apply` removes this session's merged, clean worktrees and scratch folders; lists the rest with a reason | runs (only this session's recorded worktrees and scratch) |
 
-`tidy-apply`, `state-prune` and `todo-reconcile` run only on `SHARED: no`. Handoff never runs
+`tidy-apply` and `state-prune` run only on `SHARED: no`. Handoff never runs
 `caddis_tidy.py --prune --apply` on its own, in any checkout; only the user can ask for it (Step 6b). In a
 shared checkout the report also lists every tracked file Step 1 changed, under `Docs PR needed:`.
 
@@ -157,15 +162,19 @@ history, and the relay has a 4,000-character budget (`caddis_budget.py`).
 >    to the user and stop.
 > 3. **Read the stored version's hash** before you compose: `caddis_workstreams.py hash <name>`
 >    (prints `none` for a new workstream).
-> 4. **Open-work rows** (only when `.caddis/open-work.md` exists and its frontmatter says
->    `type: open-work`): first set each row this session
->    finished, by id and column name, never by hand:
->    `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_rows.py" set --file .caddis/open-work.md --id <row id> --col Status=done --col Evidence=<evidence>`.
->    In a shared checkout (Step 0), use `--file <worktree>/.caddis/open-work.md` instead.
->    When the file is missing or has no `type: open-work` frontmatter, report row 3 exactly as
->    `skipped: no open-work.md with type: open-work (session tasks are saved by row 5)`, or, for a
->    file without the frontmatter, `skipped: open-work.md has no type: open-work frontmatter (session
->    tasks are saved by row 5)`. open-work.md is a repo backlog; this session's own tasks go to row 5.
+> 4. **Place every open item in its store (the 3-store model).** An open item lives in the store that
+>    matches how long it lives:
+>    - **This session's own tasks:** the native task list. Step 3c saves it to
+>      `.caddis/relay/<name>.tasks.md`, a snapshot that the next handoff replaces. It is never a backlog.
+>    - **An item that must outlive the next handoff** (an owner decision, deferred work, a watch item):
+>      file it with `/caddis:park`, once, and name its slug in the relay's `## Open questions / blockers`.
+>      Park only work we will do later (`park.md` Step 1). A parking-lot file is tracked, so in a shared
+>      checkout (Step 0) write it in the Step 0 worktree.
+>    - **The order of work:** the plan Tracker and the roadmap (below). Set the Tracker row of each phase this
+>      session finished (Rules).
+>    Row 3 (`open-work-row`) is retired: report it exactly as `skipped: retired (see the 3-store model)`.
+>    The `.caddis/open-work.md` and `.caddis/todo-list/` stores are retired. Never write them. A repo that
+>    still holds an old file keeps it as its own document; caddis no longer reads or writes it.
 >    **Order of work:** when the repo has a roadmap (`caddis_roadmap.py list` prints a slug), the
 >    roadmap on origin is the order of work. Write the relay's "Next step (exact)" as
 >    `next: top open item of roadmap <slug> (caddis_roadmap.py status --roadmap <slug>)`. Never copy a
@@ -213,7 +222,8 @@ Paths are relative to the repo root.
 <Commands run this session and their result: pass / fail / not-run. Be honest.>
 
 ## Open questions / blockers
-<Decisions needed, ambiguities, anything unverified. "None" if truly none.>
+<Decisions needed, ambiguities, anything unverified. "None" if truly none. An item that must outlive the
+next handoff is filed with `/caddis:park`: name its slug here, never copy its text.>
 
 ## Learnings captured
 knowledge-transfer: <✓ ran → files written | ✗ skipped → reason>
@@ -232,7 +242,7 @@ STATUS: <CONTINUE | OWNER-GATE <P>-OG<n> | BLOCKED <owner> | FAILED <reason>>
 
 Small work that does not meet a trigger skips its block.
 
-**Trigger: Always.** The relay ends with a status line, the last non-empty line, and it is exactly one of `STATUS: CONTINUE`, `STATUS: OWNER-GATE <P>-OG<n>`, `STATUS: BLOCKED <owner>` or `STATUS: FAILED <reason>`. In Step 3, point 5, write the relay with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_workstreams.py" put <name> <temp-file> --require-status --expected-hash <hash>` instead of `write` (in short: put --require-status), with the same hash Step 3 read, so a peer's newer relay is never overwritten. It rejects a relay with no valid status line, and renders the index. When the repo has `.caddis/open-work.md` with `type: open-work` in its frontmatter, also set each open-work row's status with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_rows.py" set --file <open-work.md> --id <row id> --col Status=<status>` (in a shared checkout, the copy in the Step 0 worktree). When the status is `done`, also pass `--col Evidence=<commit, PR or test>`: caddis_rows.py refuses `done` with no Evidence.
+**Trigger: Always.** The relay ends with a status line, the last non-empty line, and it is exactly one of `STATUS: CONTINUE`, `STATUS: OWNER-GATE <P>-OG<n>`, `STATUS: BLOCKED <owner>` or `STATUS: FAILED <reason>`. In Step 3, point 5, write the relay with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_workstreams.py" put <name> <temp-file> --require-status --expected-hash <hash>` instead of `write` (in short: put --require-status), with the same hash Step 3 read, so a peer's newer relay is never overwritten. It rejects a relay with no valid status line, and renders the index.
 
 ## Step 3c - Save the open tasks
 The task list dies with the session unless it is saved. Write this session's open tasks beside
@@ -262,7 +272,7 @@ be blocked by a script it does not have. Include its report in your output. A **
 (`done/<name>` already exists) is reported by the script, not fatal — surface it, do not fail the
 handoff over it. Exit 2 means a plan is held because its Tracker still has open rows (`held (open Tracker rows): ...` lines, from Phase 3): show those lines; finish, park (`.caddis/parking-lot/<file>.md` in the row) or mark the rows `dropped: <reason>`, or set the plan status back. Do not fail the handoff over it.
 
-After step 4, for each item this session closed (a phase `<plan>#<n>`, a plan slug, or an open-work row id), run `mentions` to check whether another relay's Next step still names it:
+After step 4, for each item this session closed (a phase `<plan>#<n>`, a plan slug, or a parking-lot slug), run `mentions` to check whether another relay's Next step still names it:
 ```
 python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_workstreams.py" mentions --item "<item>" --except <name>
 ```
@@ -284,12 +294,10 @@ incoming session looking for a prompt that was never written. Fix what it lists,
 It also notes any generated artefact committed before its generator last changed. That is advisory,
 not blocking — but do not quote a report the note names without rebuilding it first.
 
-## Step 6 — reconcile task rows from session-state
-Run task reconciliation against the newest session-state file:
-```
-python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_todo.py" reconcile --session-state .caddis/session-state/<session-id>.md
-```
-This marks ad-hoc to-do items done by metadata ID; it never edits the Tracker and ignores phase rows.
+## Step 6 — retired (task reconcile)
+This step is retired. It used to reconcile the `todo-list/` store, which is retired too (the 3-store model),
+so the step does nothing: do not run any script for it. Report row 8 (`todo-reconcile`) as
+`skipped: retired (see the 3-store model)`. The script stays in place for older installs only.
 
 ## Step 6b — record usage and tidy session state
 The Stop hook only writes the session-state file. These two used to run on every turn; they run
@@ -341,6 +349,27 @@ Then, when the repo has a roadmap (`.caddis/roadmaps/`), re-render its page so p
 python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_roadmap.py" render --all
 ```
 
+## Step 6d — remove this session's own worktrees and scratch folders
+Checklist row 14, `own-cleanup`. It runs in every checkout, a shared one too, after the Step 0 `finish`
+(falls back to `scripts/caddis_created.py` in a source checkout; if the script is missing, or exits 2 because
+it has no `cleanup`, the row is `skipped: not installed`):
+```
+python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_created.py" cleanup --session-id <session-id> --apply
+```
+It reads only this session's record (`~/.caddis/sessions/<session-id>.created.jsonl`). A worktree goes only
+when its PR is merged, `git status` is clean, it has no commits after the PR head, and every file its branch
+changed equals `origin/<default>` (so a squash merge counts). Then its local and remote branch go too: each
+only while its tip is still the merged work. A scratch folder goes after a full scan, links first.
+
+It never removes: another session's worktree (it is not in this record), a roadmap runner's worktree, the
+worktree this session is working in, one with uncommitted changes (untracked files count), one whose PR is
+not merged or not found, one whose tree differs from `origin/<default>`, or anything through a
+junction or symlink (a link is removed as a link; its target stays). It prints one line per entry (`REMOVED`, `KEPT
+<path>: <reason>`, `GONE` or `FAILED <path>: <problem>`) and ends with
+`[OWN-CLEANUP] removed <n>, kept <n>, gone <n>, failed <n>`. Include that summary line and each `KEPT` and
+`FAILED` line in your report. It always exits 0: a kept or failed entry is not a failure of the row, which is
+`done` when the script ran.
+
 ## Step 7 — push prompt (interactive only)
 If this is an interactive session, ask the user every time — never reuse an earlier answer:
 `Push this note for another machine? (y/N)`
@@ -360,17 +389,18 @@ Print this block, every row filled with `done`, `skipped: <reason>` or `failed:
 === HANDOFF CHECKLIST ===
 1 knowledge-transfer   done | skipped: <reason> | failed: <error>
 2 plan-tracker         <same three forms>
-3 open-work-row        <same three forms>
+3 open-work-row        skipped: retired (see the 3-store model)
 4 relay                <same three forms>
 5 tasks-file           <same three forms>
 6 kb-index             <same three forms>
 7 violations-report    <same three forms>
-8 todo-reconcile       <same three forms>
+8 todo-reconcile       skipped: retired (see the 3-store model)
 9 usage-record         <same three forms>
 10 tidy-apply          <same three forms>
 11 state-prune         <same three forms>
 12 prune-list          <same three forms>
 13 handover-check      <same three forms>
+14 own-cleanup         <same three forms>
 Shared checkout: yes|no <reason>
 ```
 

package/bundles/antigravity-plugin/skills/pr-merge/SKILL.md

@@ -43,10 +43,10 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 - **On `SHARED: no`,** do the steps as written, in this checkout.
 - **On `SHARED: yes`,** never move this checkout. Leave its changes as they are, and report them. Instead:
-  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name>)" <branch>`, then
+  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name> --record --purpose "rebase <name>")" <branch>`, then
     `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
   - **Pull a branch to test it:** `git fetch origin`, then
-    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name>)" origin/<branch>` (for the default branch,
+    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
     `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
   - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
     `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
@@ -56,7 +56,8 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 `<name>` is the branch name with each `/` written as `-`. `caddis_worktree_root.py` prints the path of a new worktree:
 `$CADDIS_WORKTREE_ROOT/<repo>/<short-name>`, else `<parent of the main checkout>/.worktrees/<repo>/<short-name>`. Never `%TEMP%`: Windows
-cleanup can empty it. The caddis guard checks only the `Shared checkout: yes` line in
+cleanup can empty it. `--record --purpose "<why>"` also writes the path to this
+session's created list (`caddis_created.py`), so `/handoff` can remove the worktree later. The caddis guard checks only the `Shared checkout: yes` line in
 `AGENTS.md`, not a dirty tree: with that line, it asks before a tree move, and denies it in a headless session.
 <!-- /checkout-safety -->
 

package/bundles/antigravity-plugin/skills/roadmap/assets/plan-resume-prompt.md

@@ -15,7 +15,7 @@ Use the scripts in that folder; do not look for them in another caddis install.
 
 1. The plan `.caddis/plans/{{slug}}.md`: its goal, its decisions, its tracker. Every decision binds you.
 2. The relay `.caddis/relay/{{slug}}.md`. Its "Next step" says where to start.
-3. The open-work list `.caddis/open-work.md`, when it exists.
+3. The open parking-lot items (`.caddis/parking-lot/*.md` with `status: open`) that name this plan, when any.
 
 ## 2. Step 0: reconcile
 
@@ -47,8 +47,8 @@ publish a branch that does). Commit the phase there, with its tracker row set to
 - The runner reviews `risk: high` phases. A phase marked `**Risk:** high`: do not halt for it and do not run the
   review yourself. When its exit gate is green, set its row `done` and end with `STATUS: CONTINUE`. The runner then
   reviews it twice and, on findings, starts one fix session.
-- Set the tracker row of the batch to `done` (with its evidence) when its exit gate is green. Set open-work rows with
-  `python <scripts>/caddis_rows.py set` (by row id and column name).
+- Set the tracker row of the batch to `done` (with its evidence) when its exit gate is green. Work you defer on
+  purpose is filed once with `/caddis:park` (a parking-lot item); never write a to-do or backlog file.
 
 ## 5. Write the relay
 

package/bundles/antigravity-plugin/skills/ship-merge/SKILL.md

@@ -42,10 +42,10 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 - **On `SHARED: no`,** do the steps as written, in this checkout.
 - **On `SHARED: yes`,** never move this checkout. Leave its changes as they are, and report them. Instead:
-  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name>)" <branch>`, then
+  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name> --record --purpose "rebase <name>")" <branch>`, then
     `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
   - **Pull a branch to test it:** `git fetch origin`, then
-    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name>)" origin/<branch>` (for the default branch,
+    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
     `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
   - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
     `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
@@ -55,7 +55,8 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 `<name>` is the branch name with each `/` written as `-`. `caddis_worktree_root.py` prints the path of a new worktree:
 `$CADDIS_WORKTREE_ROOT/<repo>/<short-name>`, else `<parent of the main checkout>/.worktrees/<repo>/<short-name>`. Never `%TEMP%`: Windows
-cleanup can empty it. The caddis guard checks only the `Shared checkout: yes` line in
+cleanup can empty it. `--record --purpose "<why>"` also writes the path to this
+session's created list (`caddis_created.py`), so `/handoff` can remove the worktree later. The caddis guard checks only the `Shared checkout: yes` line in
 `AGENTS.md`, not a dirty tree: with that line, it asks before a tree move, and denies it in a headless session.
 <!-- /checkout-safety -->
 

package/bundles/antigravity-plugin/skills/ship-pr/SKILL.md

@@ -41,10 +41,10 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 - **On `SHARED: no`,** do the steps as written, in this checkout.
 - **On `SHARED: yes`,** never move this checkout. Leave its changes as they are, and report them. Instead:
-  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name>)" <branch>`, then
+  - **Rebase:** `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" rebase-<name> --record --purpose "rebase <name>")" <branch>`, then
     `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
   - **Pull a branch to test it:** `git fetch origin`, then
-    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name>)" origin/<branch>` (for the default branch,
+    `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
     `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
   - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
     `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
@@ -54,7 +54,8 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
 
 `<name>` is the branch name with each `/` written as `-`. `caddis_worktree_root.py` prints the path of a new worktree:
 `$CADDIS_WORKTREE_ROOT/<repo>/<short-name>`, else `<parent of the main checkout>/.worktrees/<repo>/<short-name>`. Never `%TEMP%`: Windows
-cleanup can empty it. The caddis guard checks only the `Shared checkout: yes` line in
+cleanup can empty it. `--record --purpose "<why>"` also writes the path to this
+session's created list (`caddis_created.py`), so `/handoff` can remove the worktree later. The caddis guard checks only the `Shared checkout: yes` line in
 `AGENTS.md`, not a dirty tree: with that line, it asks before a tree move, and denies it in a headless session.
 <!-- /checkout-safety -->
 

package/bundles/antigravity-plugin/skills/using-git-worktrees/SKILL.md

@@ -39,10 +39,16 @@ If none is true, stop here and use `git switch -c`.
    script `caddis_worktree_root.py` prints the path; use it so the rule lives in one place:
 
 ```powershell
-$wt = python "<caddis scripts>\caddis_worktree_root.py" <short-name>   # run in the repo; prints the path
+$wt = python "<caddis scripts>\caddis_worktree_root.py" <short-name> --record --purpose "<why>"   # run in the repo; prints the path
 git worktree add -b <branch> $wt origin/<default>
 ```
 
+   `--record` also writes the path to this session's created list (`caddis_created.py`), so `/handoff` can remove the
+   worktree later. Always record it, subagents most of all: their tool calls are in a separate transcript that the
+   Stop hook does not read. If you create a worktree without the helper, run
+   `python "<caddis scripts>\caddis_created.py" record --path <path> --kind worktree --purpose "<why>"` right after
+   `git worktree add`.
+
    `<caddis scripts>` is the `scripts` folder of the installed caddis plugin. Do not create worktrees inside the
    repo. An existing worktree stays where it is: moving it breaks a venv, which keeps absolute paths.
 4. State the full path of the worktree. Work only there, and do not switch branches in it.

package/bundles/codex/.codex/skills/devops/using-git-worktrees/SKILL.md

@@ -39,10 +39,16 @@ If none is true, stop here and use `git switch -c`.
    script `caddis_worktree_root.py` prints the path; use it so the rule lives in one place:
 
 ```powershell
-$wt = python "<caddis scripts>\caddis_worktree_root.py" <short-name>   # run in the repo; prints the path
+$wt = python "<caddis scripts>\caddis_worktree_root.py" <short-name> --record --purpose "<why>"   # run in the repo; prints the path
 git worktree add -b <branch> $wt origin/<default>
 ```
 
+   `--record` also writes the path to this session's created list (`caddis_created.py`), so `/handoff` can remove the
+   worktree later. Always record it, subagents most of all: their tool calls are in a separate transcript that the
+   Stop hook does not read. If you create a worktree without the helper, run
+   `python "<caddis scripts>\caddis_created.py" record --path <path> --kind worktree --purpose "<why>"` right after
+   `git worktree add`.
+
    `<caddis scripts>` is the `scripts` folder of the installed caddis plugin. Do not create worktrees inside the
    repo. An existing worktree stays where it is: moving it breaks a venv, which keeps absolute paths.
 4. State the full path of the worktree. Work only there, and do not switch branches in it.

package/bundles/codex/.codex/skills/workflow/roadmap/assets/plan-resume-prompt.md

@@ -15,7 +15,7 @@ Use the scripts in that folder; do not look for them in another caddis install.
 
 1. The plan `.caddis/plans/{{slug}}.md`: its goal, its decisions, its tracker. Every decision binds you.
 2. The relay `.caddis/relay/{{slug}}.md`. Its "Next step" says where to start.
-3. The open-work list `.caddis/open-work.md`, when it exists.
+3. The open parking-lot items (`.caddis/parking-lot/*.md` with `status: open`) that name this plan, when any.
 
 ## 2. Step 0: reconcile
 
@@ -47,8 +47,8 @@ publish a branch that does). Commit the phase there, with its tracker row set to
 - The runner reviews `risk: high` phases. A phase marked `**Risk:** high`: do not halt for it and do not run the
   review yourself. When its exit gate is green, set its row `done` and end with `STATUS: CONTINUE`. The runner then
   reviews it twice and, on findings, starts one fix session.
-- Set the tracker row of the batch to `done` (with its evidence) when its exit gate is green. Set open-work rows with
-  `python <scripts>/caddis_rows.py set` (by row id and column name).
+- Set the tracker row of the batch to `done` (with its evidence) when its exit gate is green. Work you defer on
+  purpose is filed once with `/caddis:park` (a parking-lot item); never write a to-do or backlog file.
 
 ## 5. Write the relay
 

package/bundles/manifest.json

@@ -1,7 +1,7 @@
 {
-  "poolVersion": "1.3.151",
+  "poolVersion": "1.3.153",
   "bundles": {
-    "antigravity-plugin": "1.3.151",
+    "antigravity-plugin": "1.3.153",
     "antigravity-plugin-extras": "1.3.46",
     "codex": "unknown"
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@caddis/cli",
-  "version": "0.4.65",
+  "version": "0.4.67",
   "description": "Install, update and diagnose the caddis dev harness across every coding agent you use (Claude Code, agy/Antigravity, and more).",
   "keywords": [
     "caddis",