gate.diff-rules parks a task on a blocking violation, and the step's own doc offers a
definition edit as a remediation ("raise the rule / fix the rule and retry"). That
remediation does not reach the parked task:
internal/store/store.go RetryTask keeps the pinned workflow_definition_yaml /
digest / version columns, so the retry re-runs the same definition.
internal/daemon/daemon.go returns early when the task already carries YAML
(if task.WorkflowDefinitionYAML != "" { return nil }), so a live-applied definition
edit is never re-resolved for that task.
Retry is the only action taskstate offers a parked task besides abandon and reject.
The pinning is deliberate and pre-existing ("Each run keeps the workflow version it
started with", docs/prds/runtime-control-plane.md), but gate.diff-rules is the first step
whose operator remediation is a definition edit rather than another attempt at the change,
which is what makes this load-bearing now.
Fix options: clear the pinned definition on retry, or state in the park Detail that
retrying re-runs the same rules (the sibling diff-cap park already tells the operator what
to do, and a rule park could name the retry/reset path the same way).
Notes
Maintainer 2026-10-17: keep pinning a run to the definition version it started with. Add an explicit manual action to move a parked task onto the current definition version.
Imported from beads archie-core-vof9 · GitHub #1144 · type task · priority P2 · created 2026-09-21 · closed 2026-10-17
gate.diff-rules parks a task on a blocking violation, and the step's own doc offers a
definition edit as a remediation ("raise the rule / fix the rule and retry"). That
remediation does not reach the parked task:
- internal/store/store.go RetryTask keeps the pinned workflow_definition_yaml /
digest / version columns, so the retry re-runs the same definition.
- internal/daemon/daemon.go returns early when the task already carries YAML
(`if task.WorkflowDefinitionYAML != "" { return nil }`), so a live-applied definition
edit is never re-resolved for that task.
- Retry is the only action taskstate offers a parked task besides abandon and reject.
The pinning is deliberate and pre-existing ("Each run keeps the workflow version it
started with", docs/prds/runtime-control-plane.md), but gate.diff-rules is the first step
whose operator remediation is a definition edit rather than another attempt at the change,
which is what makes this load-bearing now.
Fix options: clear the pinned definition on retry, or state in the park Detail that
retrying re-runs the same rules (the sibling diff-cap park already tells the operator what
to do, and a rule park could name the retry/reset path the same way).
### Notes
Maintainer 2026-10-17: keep pinning a run to the definition version it started with. Add an explicit manual action to move a parked task onto the current definition version.
### Close reason
Retry on current definition option, 3b1860f7
---
_Imported from beads `archie-core-vof9` · GitHub #1144 · type task · priority P2 · created 2026-09-21 · closed 2026-10-17_
sam
added the mediumtask labels 2026-10-27 13:41:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
gate.diff-rules parks a task on a blocking violation, and the step's own doc offers a
definition edit as a remediation ("raise the rule / fix the rule and retry"). That
remediation does not reach the parked task:
digest / version columns, so the retry re-runs the same definition.
(
if task.WorkflowDefinitionYAML != "" { return nil }), so a live-applied definitionedit is never re-resolved for that task.
The pinning is deliberate and pre-existing ("Each run keeps the workflow version it
started with", docs/prds/runtime-control-plane.md), but gate.diff-rules is the first step
whose operator remediation is a definition edit rather than another attempt at the change,
which is what makes this load-bearing now.
Fix options: clear the pinned definition on retry, or state in the park Detail that
retrying re-runs the same rules (the sibling diff-cap park already tells the operator what
to do, and a rule park could name the retry/reset path the same way).
Notes
Maintainer 2026-10-17: keep pinning a run to the definition version it started with. Add an explicit manual action to move a parked task onto the current definition version.
Close reason
Retry on current definition option,
3b1860f7Imported from beads
archie-core-vof9· GitHub #1144 · type task · priority P2 · created 2026-09-21 · closed 2026-10-17