[P2-018] Re-pin the delivery model to the repaired claim and handoff rules

AGENTS.md

@@ -12,12 +12,12 @@
 
 ## Delivery model (P2-018)
 
-Work is scheduled as delivery tasks in the [delivery graph](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/README.md) and executed through the [Plan execution entry](https://github.com/ArcForges/Plan-B/blob/0cb637d1bfbf64d7db22a96a2b7370a409a25d8e/arcforges-implementation.md). There is no Current task, numbered substep order or single main context.
+Work is scheduled as delivery tasks in the [delivery graph](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/README.md) and executed through the [Plan execution entry](https://github.com/ArcForges/Plan-B/blob/ec8820732486464e92df89788edb89eafac86afb/arcforges-implementation.md). There is no Current task, numbered substep order or single main context.
 
-- Baseline: The accepted bootstrap is the Android application with its development package identity, the preview-only shared module and the transport probe client, with the WP02 build, dependency and provenance baselines. Every Android companion capability is an open task. This repository's tasks are in the [android](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/android.md) lane and parts of the governance, release and runtime-proof lanes.
-- Start only a task that Plan-B's `python tools/delivery.py ready --claims` lists and whose `claims/<task-id>` branch you hold. A task here becomes ready only after the adoption slice for its lane (`ADOPT.10.<lane>`) is recorded.
-- Several workers may work here at once, each on a different claimed task in its own retained worktree and `task/<task-id>` branch, inside the task's write scope. After the module skeleton task, each feature task edits only its own module, so storage, security, network and screen work proceed in parallel.
-- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/shared-resources.md): the module skeleton task registers all modules once and later tasks edit only their module; version catalog entries are appended and locks and verification metadata regenerated after rebase; dependency additions carry admission receipts; signing identities and store listings are used only by release tasks through protected CI environments. The Mobile integration owner orders merges and merges only pull requests of the claimant at the current claim epoch.
+- Baseline: The accepted bootstrap is the Android application with its development package identity, the preview-only shared module and the transport probe client, with the WP02 build, dependency and provenance baselines. Every Android companion capability is an open task. This repository's tasks are in the [android](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/android.md) lane and parts of the governance, release and runtime-proof lanes.
+- Start only a task that Plan-B's `python tools/delivery.py ready` lists and whose claim you hold (`python tools/delivery.py claim <TASK-ID> --worker <name>`, recorded as `claims/<key>`, the ID in lower case with dots replaced by hyphens, such as `claims/and-01`); continue interrupted work from its handoff record (`python tools/delivery.py show <TASK-ID>`) rather than restarting it. A task here becomes ready only after the adoption slice for its lane (`ADOPT.10.<lane>`) is recorded.
+- Several workers may work here at once, each on a different claimed task in its own retained worktree and `task/<key>` branch, inside the task's write scope. After the module skeleton task, each feature task edits only its own module, so storage, security, network and screen work proceed in parallel.
+- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/shared-resources.md): the module skeleton task registers all modules once and later tasks edit only their module; version catalog entries are appended and locks and verification metadata regenerated after rebase; dependency additions carry admission receipts; signing identities and store listings are used only by release tasks through protected CI environments. The Mobile integration owner (the holder of `roles/integration-mobile`) orders merges and merges only at the head commit reviewed for the claimant at the current claim epoch, keeping the task IDs in the merge title.
 - Title pull requests `[<TASK-ID>] <summary>`; a bundle of compatible ready tasks lists each ID, and planning alignment uses `[P2-018]`.
 - Earlier dated bootstrap and provenance records under `docs/` describe their original scope; they are evidence, not execution instructions.