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

AGENTS.md

@@ -15,12 +15,12 @@ Plan bounded changes before implementation. This repository owns the C# Native A
 
 ## 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 anonymous Native AOT Hello host, its container image and ingress Worker with the WP02 build, dependency and provenance baselines. Every business module is an open task. This repository's tasks are in the [cloud](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/cloud.md), [commerce](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/commerce.md), [policy](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/policy.md), [operations](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/operations.md), [device-bridge](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/device-bridge.md), [simulator](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/simulator.md), [search](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/search.md), [ai-routing](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/ai-routing.md), [harness](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/harness.md) lanes and parts of the extensions, 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.07.<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. Each of the 21 modules owns its own tables, folders, plans and tests, so module tasks proceed in parallel; cross-module changes use the declared participant interfaces of the guarded transaction families, whose participant list changes only through the Architecture Owner.
-- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/shared-resources.md): module tasks author D1 migrations under their module prefix and the integration owner assigns the global sequence number at merge; each module registers through its own entry point and route fragment while the host composition only lists modules; each publication watermark, Durable Object alarm namespace and R2 prefix has one owning module and is reserved in the binding plan first; storage-plan manifest hashes are regenerated after rebase; each owning task adds its own section of the private configuration; runbooks and provider fixtures are one file each with append-only indexes; the deployed test environment is held through a short lease during live runs. The Cloud integration owner orders merges and merges only pull requests of the claimant at the current claim epoch.
+- Baseline: The accepted bootstrap is the anonymous Native AOT Hello host, its container image and ingress Worker with the WP02 build, dependency and provenance baselines. Every business module is an open task. This repository's tasks are in the [cloud](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/cloud.md), [commerce](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/commerce.md), [policy](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/policy.md), [operations](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/operations.md), [device-bridge](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/device-bridge.md), [simulator](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/simulator.md), [search](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/search.md), [ai-routing](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/ai-routing.md), [harness](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/harness.md) lanes and parts of the extensions, 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/cloud-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.07.<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. Each of the 21 modules owns its own tables, folders, plans and tests, so module tasks proceed in parallel; cross-module changes use the declared participant interfaces of the guarded transaction families, whose participant list changes only through the Architecture Owner.
+- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/shared-resources.md): module tasks author D1 migrations under their module prefix and the integration owner assigns the global sequence number at merge; each module registers through its own entry point and route fragment while the host composition only lists modules; each publication watermark, Durable Object alarm namespace and R2 prefix has one owning module and is reserved in the binding plan first; storage-plan manifest hashes are regenerated after rebase; each owning task adds its own section of the private configuration; runbooks and provider fixtures are one file each with append-only indexes; the deployed test environment is held through a short lease during live runs. The Cloud integration owner (the holder of `roles/integration-cloud`) 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 validation records under `docs/` describe their original scope; they are evidence, not execution instructions.