Context
SpecTrack handoff guidance currently assumes each in-flight issue carries a body Resume section that is refreshed during handoff. That makes continuation state part of the issue body even when the issue body should remain a current implementation spec rather than a session handoff surface.
GitHub and Jira both support updating existing issue comments. A comment-backed Resume record would let handoff keep current continuation state in one provider-visible comment per issue, while preserving separate appended comments for narrative-worthy events.
Authoring contracts and agent guidance also contain body-Resume assumptions. Those references need to be reviewed so future sessions do not keep writing handoff state into issue bodies by default.
Description
Change SpecTrack handoff persistence so current Resume state can live in an updatable provider comment instead of requiring a Resume section in the issue body. The workflow should support GitHub and Jira issue backends and keep provider records discoverable for fresh sessions.
Update user-facing and runtime-facing guidance so handoff behavior, issue authoring contracts, and implementation/audit agents consistently describe the chosen Resume location.
Acceptance Criteria
- GitHub-backed issues can maintain a single current Resume comment that is updated on subsequent handoffs rather than appending duplicate Resume comments.
- Jira-backed issues can maintain a single current Resume comment that is updated on subsequent handoffs rather than appending duplicate Resume comments.
- Handoff guidance no longer requires refreshing a
Resume section in the issue body when the provider supports a comment-backed Resume record.
- Narrative-worthy events remain ordinary appended comments and are not conflated with the current Resume record.
- Fresh-session context discovery can find the current Resume state for a touched issue without relying on local-only files.
- Authoring contracts and agent guidance no longer instruct body
Resume writeback where that conflicts with the comment-backed Resume model.
- Existing provider freshness and stale-write protections still cover Resume comment updates.
- Tests or equivalent verification cover GitHub and Jira Resume comment update behavior and the no-duplicate-comment expectation.
Context
SpecTrack handoff guidance currently assumes each in-flight issue carries a body
Resumesection that is refreshed during handoff. That makes continuation state part of the issue body even when the issue body should remain a current implementation spec rather than a session handoff surface.GitHub and Jira both support updating existing issue comments. A comment-backed Resume record would let handoff keep current continuation state in one provider-visible comment per issue, while preserving separate appended comments for narrative-worthy events.
Authoring contracts and agent guidance also contain body-
Resumeassumptions. Those references need to be reviewed so future sessions do not keep writing handoff state into issue bodies by default.Description
Change SpecTrack handoff persistence so current Resume state can live in an updatable provider comment instead of requiring a
Resumesection in the issue body. The workflow should support GitHub and Jira issue backends and keep provider records discoverable for fresh sessions.Update user-facing and runtime-facing guidance so handoff behavior, issue authoring contracts, and implementation/audit agents consistently describe the chosen Resume location.
Acceptance Criteria
Resumesection in the issue body when the provider supports a comment-backed Resume record.Resumewriteback where that conflicts with the comment-backed Resume model.