Implement claim and resolution workflows #23

Open
opened 2026-08-17 22:01:08 -04:00 by steve · 0 comments
Owner

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Deliver the claim and resolution workflows. An AI agent can claim a frontier ticket, record a resolution, close it, and update the map pointer while receiving explicit recovery information if a later step fails.

Acceptance criteria

  • Claim assigns the ticket to the current authenticated user using the common operation.
  • Claim fails clearly when the current user cannot be determined or assignment is unsupported.
  • Resolve posts the answer as a comment/note, closes the ticket, and appends a concise context pointer to the map.
  • Resolution exposes completed steps and remaining recovery work when a later provider action fails.
  • Resolution does not silently lose the answer when close or map update fails.
  • Tests cover successful claim/resolve, already-claimed tickets, provider failures at each step, and replay behavior.

Blocked by

Part of [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## Parent [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## What to build Deliver the claim and resolution workflows. An AI agent can claim a frontier ticket, record a resolution, close it, and update the map pointer while receiving explicit recovery information if a later step fails. ## Acceptance criteria - [ ] Claim assigns the ticket to the current authenticated user using the common operation. - [ ] Claim fails clearly when the current user cannot be determined or assignment is unsupported. - [ ] Resolve posts the answer as a comment/note, closes the ticket, and appends a concise context pointer to the map. - [ ] Resolution exposes completed steps and remaining recovery work when a later provider action fails. - [ ] Resolution does not silently lose the answer when close or map update fails. - [ ] Tests cover successful claim/resolve, already-claimed tickets, provider failures at each step, and replay behavior. ## Blocked by - [Implement dependencies and frontier queries](http://gitea.sagacity.ca/steve/skills/issues/22)
steve added the ready-for-agent label 2026-08-17 22:01:08 -04:00
steve added a new dependency 2026-08-17 22:02:10 -04:00
steve added a new dependency 2026-08-17 22:02:10 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: steve/skills#23