slot-reconcile engine: apply recipe drift to a provisioned slot; record declined drift #24

New issue

Open

opened 2026-08-11 19:24:01 +00:00 by jbr870 · 1 comment

jbr870 commented

2026-08-11 19:24:01 +00:00

Owner

Spawned from finding F-PO-21-3-2 (in-scope-deferrable) on issue #21 during /develop (auto-applied disposition, developer-decidable).

Gap: slot-isolation.md §5.5 defines reconcile as a first-class act and slot-claim.sh points operators at it on drift, but no slot-reconcile.sh engine ships in #21 — the operator procedure (git-worktrees/procedures/slot-lifecycle.md) documents the executable route instead (retire via worktree-cleanup + provision again), and a declined reconcile's drift.declined_at field is read by slot-status.sh but written by nothing.

Scope for this issue: a slot-reconcile.sh engine (recompute assignments from the current recipe, apply the delta axis-by-axis with the same resumable state machine, refuse destructive narrowing without --force) + record drift.declined_at on an explicit decline so status keeps flagging it, + slot-flow.sh scenarios.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /requirements --issue=<this> to flesh it out before planning.

Spawned from finding `F-PO-21-3-2` (in-scope-deferrable) on issue #21 during /develop (auto-applied disposition, developer-decidable). **Gap:** `slot-isolation.md` §5.5 defines **reconcile** as a first-class act and `slot-claim.sh` points operators at it on drift, but no `slot-reconcile.sh` engine ships in #21 — the operator procedure (`git-worktrees/procedures/slot-lifecycle.md`) documents the executable route instead (retire via worktree-cleanup + provision again), and a declined reconcile's `drift.declined_at` field is read by `slot-status.sh` but written by nothing. **Scope for this issue:** a `slot-reconcile.sh` engine (recompute assignments from the current recipe, apply the delta axis-by-axis with the same resumable state machine, refuse destructive narrowing without --force) + record `drift.declined_at` on an explicit decline so `status` keeps flagging it, + slot-flow.sh scenarios. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/requirements --issue=<this>` to flesh it out before planning.

jbr870 added the

labels

2026-08-11 19:24:01 +00:00

jbr870 referenced this issue

2026-08-11 19:24:02 +00:00

Worktree and devcontainer are provisioned separately — concurrent features collide in one container #21

jbr870 commented

2026-08-11 20:46:08 +00:00

Author

Owner

{"status":"active","from_issue":"21","finding_ref":"CR-25","decision":"auto-applied (developer-decidable, qa fix stage)","category":"in-scope-deferrable","summary":"Claim-time drift persistence removed by CR-11 fix; drift field written only by the future reconcile act","original_scope_note":"status renders the drift column; nothing populates it until reconcile ships","disposition_rationale":"CR-11 requires byte-identical record on refused claim; persistence belongs with reconcile (#24 scope)"}

```json {"status":"active","from_issue":"21","finding_ref":"CR-25","decision":"auto-applied (developer-decidable, qa fix stage)","category":"in-scope-deferrable","summary":"Claim-time drift persistence removed by CR-11 fix; drift field written only by the future reconcile act","original_scope_note":"status renders the drift column; nothing populates it until reconcile ships","disposition_rationale":"CR-11 requires byte-identical record on refused claim; persistence belongs with reconcile (#24 scope)"} ```

jbr870 referenced this issue

2026-08-12 19:50:51 +00:00

Worktree and devcontainer are provisioned separately — concurrent features collide in one container #21

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jbr870/devwork-skills#24

No description provided.

Rows
Columns