steve/skills
Public Access
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Bootstrap the tracker runtime and provider selection #17

New Issue
Open
opened 2026-08-17 22:01:06 -04:00 by steve · 0 comments
steve commented 2026-08-17 22:01:06 -04:00
Owner
Copy Link
Copy Source

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Deliver the standalone Python package and agent-facing CLI foundation. A user can invoke one command and receive a stable JSON envelope while the tool selects GitHub, GitLab, or Gitea explicitly or from the repository context. The foundation must expose the subprocess seam used by all provider adapters and make transient versus non-retryable failures distinguishable.

Acceptance criteria

  • A reusable library API and CLI entry point exist for later tracker operations.
  • Provider selection precedence is --provider, then TRACKER_PROVIDER, then Git remote autodetection.
  • GitHub, GitLab, and Gitea are accepted canonical provider values.
  • Every invocation returns machine-readable JSON on stdout and keeps diagnostics on stderr.
  • Success and failure envelopes identify the operation and provider; failures include stable code and retryability.
  • The subprocess runner can be replaced by tests without live credentials.
  • Provider detection, invalid provider input, ambiguous remotes, and missing provider CLIs have contract tests.

Blocked by

  • None — can start immediately.
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 standalone Python package and agent-facing CLI foundation. A user can invoke one command and receive a stable JSON envelope while the tool selects GitHub, GitLab, or Gitea explicitly or from the repository context. The foundation must expose the subprocess seam used by all provider adapters and make transient versus non-retryable failures distinguishable. ## Acceptance criteria - [ ] A reusable library API and CLI entry point exist for later tracker operations. - [ ] Provider selection precedence is --provider, then TRACKER_PROVIDER, then Git remote autodetection. - [ ] GitHub, GitLab, and Gitea are accepted canonical provider values. - [ ] Every invocation returns machine-readable JSON on stdout and keeps diagnostics on stderr. - [ ] Success and failure envelopes identify the operation and provider; failures include stable code and retryability. - [ ] The subprocess runner can be replaced by tests without live credentials. - [ ] Provider detection, invalid provider input, ambiguous remotes, and missing provider CLIs have contract tests. ## Blocked by - None — can start immediately.
steve added the ready-for-agent label 2026-08-17 22:01:06 -04:00
steve added a new dependency 2026-08-17 22:02:02 -04:00
#18 Implement the issue lifecycle across providers
steve added a new dependency 2026-08-17 22:02:10 -04:00
#19 Implement idempotent labels and assignment
steve added a new dependency 2026-08-17 22:02:10 -04:00
#20 Implement the pull-request and merge-request lifecycle
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
in-progress
in-review
needs-info
needs-review
Waiting for review by a human
 needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
Wayfinder human decision ticket
 wayfinder:map
Wayfinder decision map
 wontfix
No labels ready-for-agent
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
steve (Steve Beaulac)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#18 Implement the issue lifecycle across providers
steve/skills
#19 Implement idempotent labels and assignment
steve/skills
#20 Implement the pull-request and merge-request lifecycle
steve/skills
Reference: steve/skills#17