Harden cross-provider behavior and migrate skills #24

New Issue

2026-08-17T22:01:08-04:00

steve commented

2026-08-17 22:01:08 -04:00

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Harden the complete cross-provider workflow and migrate the skills documentation to use it. A maintainer can validate the package against provider contracts, transient and semantic failures, and agent-facing guidance without live credentials.

Acceptance criteria

All provider adapters satisfy the same externally visible issue, request, label, wayfinding, dependency, claim, and resolution contract.
Transient failures and rate limits use bounded retries; semantic, authorization, missing-resource, and unsupported-capability failures do not retry.
Uncertain outcomes are represented explicitly when a provider command may have completed before failing.
Optional live smoke tests are isolated from credential-free contract tests.
Existing tracker guides and relevant agent instructions explain when to use the common tool and retain provider-specific fallback semantics.
Documentation prevents agents from reimplementing prerequisite queries and provider command translations.
A final cross-provider end-to-end test exercises one complete issue and one complete wayfinding flow for each provider fixture.

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 Harden the complete cross-provider workflow and migrate the skills documentation to use it. A maintainer can validate the package against provider contracts, transient and semantic failures, and agent-facing guidance without live credentials. ## Acceptance criteria - [ ] All provider adapters satisfy the same externally visible issue, request, label, wayfinding, dependency, claim, and resolution contract. - [ ] Transient failures and rate limits use bounded retries; semantic, authorization, missing-resource, and unsupported-capability failures do not retry. - [ ] Uncertain outcomes are represented explicitly when a provider command may have completed before failing. - [ ] Optional live smoke tests are isolated from credential-free contract tests. - [ ] Existing tracker guides and relevant agent instructions explain when to use the common tool and retain provider-specific fallback semantics. - [ ] Documentation prevents agents from reimplementing prerequisite queries and provider command translations. - [ ] A final cross-provider end-to-end test exercises one complete issue and one complete wayfinding flow for each provider fixture. ## Blocked by - [Implement the issue lifecycle across providers](http://gitea.sagacity.ca/steve/skills/issues/18) - [Implement idempotent labels and assignment](http://gitea.sagacity.ca/steve/skills/issues/19) - [Implement the pull-request and merge-request lifecycle](http://gitea.sagacity.ca/steve/skills/issues/20) - [Implement claim and resolution workflows](http://gitea.sagacity.ca/steve/skills/issues/23)

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

#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

steve added a new dependency 2026-08-17 22:02:10 -04:00

#23 Implement claim and resolution workflows

Sign in to join this conversation.