stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Resume autonomous release runs from durable checkpoints #331

New Issue
Closed
opened 2026-08-08 19:10:27 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-08 19:10:27 +00:00
Member
Copy Link

Evidence

The release engine persists claimed, agent_complete, tests_passed, and pushed states, but production execution never calls StateStore.load(). A worker restart therefore repeats completed coding/testing stages and can repeat mutations. Open issues have no eligible timmy/unassigned item; existing #11 is assigned to rockachopa and historical issue/commit review found no checkpoint-resume implementation.

User impact

Operators can restart an interrupted autonomous release safely. The engine validates repository, issue, deterministic branch, and commit identity, skips only proven completed stages, and reuses/opens exactly one PR without rerunning expensive work.

Acceptance tests

  • Restart from agent_complete with matching branch/SHA skips claim and coding, then tests, pushes, and opens one linked PR.
  • Restart from tests_passed skips claim, coding, and tests, then pushes and opens one linked PR.
  • Restart from pushed verifies the remote branch SHA and opens one linked PR without earlier stages.
  • Mismatched repository, issue, branch, local SHA, or remote SHA fails closed before push/PR mutation.
  • Fresh runs persist versioned repository and commit-bound checkpoints atomically.
  • Existing PR reuse and dry-run behavior remain idempotent.
## Evidence The release engine persists `claimed`, `agent_complete`, `tests_passed`, and `pushed` states, but production execution never calls `StateStore.load()`. A worker restart therefore repeats completed coding/testing stages and can repeat mutations. Open issues have no eligible timmy/unassigned item; existing #11 is assigned to rockachopa and historical issue/commit review found no checkpoint-resume implementation. ## User impact Operators can restart an interrupted autonomous release safely. The engine validates repository, issue, deterministic branch, and commit identity, skips only proven completed stages, and reuses/opens exactly one PR without rerunning expensive work. ## Acceptance tests - Restart from `agent_complete` with matching branch/SHA skips claim and coding, then tests, pushes, and opens one linked PR. - Restart from `tests_passed` skips claim, coding, and tests, then pushes and opens one linked PR. - Restart from `pushed` verifies the remote branch SHA and opens one linked PR without earlier stages. - Mismatched repository, issue, branch, local SHA, or remote SHA fails closed before push/PR mutation. - Fresh runs persist versioned repository and commit-bound checkpoints atomically. - Existing PR reuse and dry-run behavior remain idempotent.
timmy was assigned by rockachopa 2026-08-08 19:10:27 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
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: stackchain/stackchain-dashboard#331
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?