devlyn-cli 4.2.24 → 4.2.26

package/config/skills/_shared/task-complete.py

@@ -264,7 +264,12 @@ def allocate(args, *, exclude_receipts=()):
     receipt["worktree_identity"] = workspace_identity(target, Path(receipt["worktree_gitdir"]))
     receipt["allocation"] = "owned"
     atomic_json(path, receipt)
+    # Owned first: an interrupted warm-up leaves a usable allocation whose build starts cold.
+    with locked_receipt(path) as owned:
+        owned["build_dirs"] = shared("warm-build-dirs")["warm"](target, work, scratch)
+        atomic_json(path, owned)
     return {"status": "ALLOCATED", "receipt": str(path), "worktree": str(target), "scratch": str(scratch),
+            "build_dirs": owned["build_dirs"],
             "reconciled": [] if local else reconcile(common, path, work, exclude_receipts=exclude_receipts)}
 
 

package/config/skills/_shared/task-completion.md

@@ -106,10 +106,21 @@ require the affected checks again.
 Keep the original edits through pending or failed delivery; only reconciliation
 removes them. Preserve all other work and report anything left behind.
 
-Allocation also returns a receipt-owned `scratch` directory. Put disposable
-build intermediates there (for example, set
-`CARGO_TARGET_DIR` to `<scratch>/target`). Keep source checkouts, Git data,
-lockfiles, reports and restart evidence outside scratch. Do not create unowned
+Build in the task worktree's own default build directory, never in one
+another checkout builds in, even one build at a time: tools such as Cargo take
+one checkout's outputs as fresh for the other. When a Cargo workspace's
+Cargo.toml sets `[workspace.metadata.devlyn] warm-build-dirs = true`,
+allocation seeds that directory from a built checkout of the repository, so
+the first build does not rebuild every dependency; `build_dirs` in its result
+and receipt says what it did, and a skip means an ordinary cold build. The
+opt-in is the workspace's: seeding keeps dependency outputs that may hold the
+other checkout's paths, and those follow that checkout's later rebuilds. `warm-build-dirs.py <worktree>` does the same for a
+worktree made without allocation. A warmed directory leaves with the worktree
+after merge, so a pending, failed or local-only task keeps it.
+
+Allocation also returns a receipt-owned `scratch` directory for other
+disposable build files, such as writable tool caches. Keep source checkouts,
+Git data, lockfiles, reports and restart evidence outside scratch. Do not create unowned
 temporary build trees or preserve them by copying them into evidence custody.
 Prefer `TemporaryDirectory`/`finally` for short-lived test fixtures.