GitHub

Select GitHub artifact mirroring with artifacts.provider: "github". The local run remains authoritative.

Configuration

{
  "artifacts": {
    "provider": "github",
    "github": {
      "owner": "acme",
      "ownerType": "organization",
      "statusField": "Status",
      "visibility": "private",
      "projectStatuses": {
        "planned": "Todo",
        "executing": "In Progress",
        "inReview": "In Review",
        "done": "Done",
        "blocked": "Blocked"
      }
    }
  }
}

Credentials belong in the host's authenticated gh environment, never in repository configuration. Projects v2 and native dependencies use gh api graphql; repository issue operations use GitHub issue APIs through gh. Custom HTTP/GraphQL clients, credential reads, and token forwarding are forbidden.

Transport capabilities and boundaries

The GitHub provider requires host-authenticated gh with these verified capabilities:

• Projects: projectRead, projectWrite, and projectDelete (for smoke testing);
• Issues: issueRead, issueWrite, issueClose, and issueDelete (for smoke testing);
• Dependencies: dependencyRead and dependencyWrite;
• Status field: statusFieldRead and statusFieldWrite;
• Operations: complete pagination and independentReadBack.

Missing capabilities, unauthorized scopes, foreign markers, drift, or partial responses fail closed at the provider boundary.

Identities, hierarchy, and graph

Accepted canonical URL forms are:

• Projects: https://github.com/orgs/<owner>/projects/<N> (organizations) or https://github.com/users/<owner>/projects/<N> (users);
• Issues: https://github.com/<owner>/<repo>/issues/<N>.

Canonical URLs are user-facing references and Commit attribution targets. Native GraphQL node IDs and Project item IDs remain separate mutation identities.

Build and project-backed Fix resolve an exact supplied Project URL or create one [Build]/[Fix] <goal> Project under the configured owner. The complete specification is written inside ProjectV2.readme between markers <!-- woostack-spec-start --> and <!-- woostack-spec-end -->, preserving unrelated README bytes. shortDescription contains a concise goal summary.

Plan increments are normal parentless repository issues (parent = null) added directly as Project items. No synthetic parent plan issue or draft item is created. Preallocated external mutation IDs (<!-- woostack-project-mutation:<UUID> --> and <!-- woostack-issue-mutation:<UUID> -->) enable duplicate-safe recovery across pagination.

An admitted sequence of $N$ increments creates $N-1$ native blocked-by dependencies (predecessor blocks successor). Project item ordering or prose never substitutes for the native graph.

Lifecycle and closure

Execute transitions Project item status from planned to executing during implementation, inReview at PR delivery, and done (closing the issue) at completion. Recorded blockers set blocked without closing the issue. Nonterminal states keep issues open.

When local runs are mirrored to GitHub (artifacts.provider: "github"), the local manifest remains the authoritative execution and resume checkpoint. Execute delivery associates the PR with the exact mapped canonical issue (Resolves https://github.com/<owner>/<repo>/issues/<N>), verified live against the admitted repository. An aggregate failed mirror status does not suppress issue association when an exact task mapping exists. If issue verification or association fails, Execute warns and continues repository delivery and local manifest CAS persistence without blocking. When --recheck encounters an already-delivered task whose verified open PR lacks the exact association, it repairs the PR body without rerunning implementation, creating Git/Graphite objects, or modifying issue lifecycle state.

Completing all increments leaves the Project open. Explicit provider-backed Plan/Execute closure closes the exact admitted Project after a fresh read and independent read-back. Local-run abandonment records status: "abandoned" in the manifest and retains all local artifacts in .woostack/tmp/runs/<run-id>/ without mutating or closing the mirrored Project or its issues.

Workflow matrix