GitHub tracker does not propagate the GHES endpoint to the worker (github_graphql falls back to api.github.com)

[hojinzs]

Problem

A GitHub Enterprise Server user who configures tracker.endpoint/tracker.apiUrl in WORKFLOW.md gets a half-working system. The orchestrator/CLI talk to the configured GHES endpoint, but the dispatched worker's github_graphql tool falls back to https://api.github.com/graphql because the orchestrator never injects GITHUB_GRAPHQL_API_URL into the worker environment.

packages/tracker-github/src/orchestrator-adapter.ts:43-47 buildWorkerEnvironment returns only { GITHUB_PROJECT_ID } even though project.tracker.apiUrl is in scope. The worker tool reads the endpoint only from process.env (packages/tool-github-graphql/src/tool.ts:134, default at tool.ts:3). The Linear adapter does the right thing (packages/tracker-linear/src/orchestrator-adapter.ts:203 propagates LINEAR_GRAPHQL_URL), so GitHub is the odd one out.

Compounding this, doctor validates auth only against api.github.com and never inspects GITHUB_GRAPHQL_API_URL / tracker.apiUrl (packages/cli/src/commands/doctor.ts, packages/cli/src/github/client.ts hardcoded DEFAULT_API_URL), so a GHES user gets a green doctor run and then a confusing runtime failure.

Impact (OSS user)

GHES users silently hit the wrong host (or fail auth) when the worker posts comments/PR links, with no diagnostic. The only workaround is to separately export GITHUB_GRAPHQL_API_URL on the orchestrator host — an undocumented second place to configure the same fact.

Evidence (real files)

• packages/tracker-github/src/orchestrator-adapter.ts:43-47, 154.
• packages/orchestrator/src/service.ts:1578-1633 (worker env block, no GITHUB_GRAPHQL_API_URL).
• packages/tool-github-graphql/src/tool.ts:3,134; packages/runtime-codex/src/launcher.ts:41.
• packages/cli/src/github/client.ts DEFAULT_API_URL; packages/cli/src/commands/doctor.ts (no GHES endpoint check).
• Linear counterexample: packages/tracker-linear/src/orchestrator-adapter.ts:203.

Proposed fix

In the GitHub buildWorkerEnvironment, propagate the resolved tracker.apiUrl as GITHUB_GRAPHQL_API_URL when present so the worker tool inherits the same endpoint. Extend doctor to print the resolved GraphQL endpoint and warn when GITHUB_GRAPHQL_API_URL and tracker.apiUrl disagree. Document GHES setup end to end.

---

Priority: P1 · Symphony layer: Integration · category: config
Filed from an OSS-user-perspective audit of the repo.

[moncher-dev]

Workpad — #388 — Cycle 1

Type: fresh pickup
Branch: feat/388-ghes-graphql-endpoint
Draft PR: not yet created
Cycle opened: 2026-06-22T01:30:22Z · Trigger: Ready issue is actionable; no linked PR or prior branch found

Status Transitions

Plan

• 1. Propagate GHES GraphQL endpoint through GitHub tracker worker env; add focused tests.
• 2. Extend doctor to display the resolved GitHub GraphQL endpoint and warn on config/env mismatches; add focused tests.
• 3. Document GHES endpoint setup end to end.
• 4. 마무리: 원본 이슈 재검증 · Completion Bar 통과 · changeset (필요 시) · PR ready · In review 전이

Rework / PR Feedback

• N/A — fresh pickup.

Completion Bar

• In-scope requirements implemented
• pnpm lint
• pnpm test
• pnpm typecheck
• pnpm build
• Docker E2E (if integration behavior changed)
• Tests for new functionality (or justified N/A)
• Code conventions (CLAUDE.md)
• Inline review comments answered (rework only)

Validation

• Symphony layer classification: Integration Layer, crossing Configuration and Observability touchpoints.
• Spec conformance: pending post-work check against docs/symphony-spec.md.
• Changeset: N/A pending label check
• Docker E2E evidence: pending
• Merge commit (Land cycle only): N/A

위임 (out-of-scope / human / post-merge)

• None

Progress Log

• 2026-06-22T01:30:22Z: Opened fresh Cycle 1 after confirming issue GitHub tracker does not propagate the GHES endpoint to the worker (github_graphql falls back to api.github.com) #388 is in Ready, has no comments/workpads, and no linked open PR for #388.

Blockers

None

[moncher-dev]

⛔ Blocker

What: Required Docker E2E blackbox validation cannot run in this environment.

Why: docker compose -f docker-compose.e2e.yml -f docker-compose.e2e.events.yml up -d --build failed because Docker cannot connect to its server socket: unix:///Users/steve/.docker/run/docker.sock does not exist. docker info confirms the Docker client is installed but the server connection fails with the same missing socket.

How to unblock: Start Docker Desktop / the Docker daemon so docker info reports a live server, then move this issue back to Ready to rerun the Docker E2E and complete PR handoff.

Completed before blocker: Implementation committed and pushed on feat/388-ghes-graphql-endpoint (ec266d3). pnpm lint, pnpm test, pnpm typecheck, and pnpm build passed. Local E2E fallback reached health=idle, activeRuns=0, retryQueue=[], lastError=null after clearing the fixture.

[moncher-dev]

🔁 Status: Ready → Backlog

Reason: Required Docker E2E is blocked because the Docker daemon socket is unavailable in this environment.
Cycle: 1 close

[moncher-dev]

Workpad — #388 — Cycle 2

Type: resume after blocker
Branch: feat/388-ghes-graphql-endpoint
Draft PR: #405
Cycle opened: 2026-06-22T04:47:42Z · Trigger: Issue returned to Ready after Cycle 1 Docker-daemon blocker; existing implementation branch is available

Status Transitions

• 2026-06-22T04:47:42Z · Ready → In progress · Resuming after the Docker-daemon blocker was cleared; existing implementation branch and draft PR are ready for validation. (cycle 2 open)

Plan

• 1. Re-validate the existing GHES endpoint propagation implementation and focused tests.
• 2. Rerun required validation, including Docker E2E blackbox coverage from AGENT_TEST.md.
• 3. 마무리: 원본 이슈 재검증 · Completion Bar 통과 · changeset (필요 시) · PR ready · In review 전이

Rework / PR Feedback

• N/A — resume after infrastructure blocker, no PR review feedback.

Completion Bar

• In-scope requirements implemented
• pnpm lint
• pnpm test
• pnpm typecheck
• pnpm build
• Docker E2E (if integration behavior changed)
• Tests for new functionality (or justified N/A)
• Code conventions (CLAUDE.md)
• Inline review comments answered (rework only)

Validation

• Symphony layer classification: Integration Layer, crossing Configuration and Observability touchpoints.
• Spec conformance: pending post-work check against docs/symphony-spec.md.
• Changeset: N/A — issue has no changeset:* label.
• Docker E2E evidence: pending
• Merge commit (Land cycle only): N/A

위임 (out-of-scope / human / post-merge)

• None

Progress Log

• 2026-06-22T04:49:20Z: Reviewed Cycle 1 commit ec266d3; focused tests passed: pnpm exec vitest run packages/tracker-github/src/tracker-github.test.ts and pnpm exec vitest run packages/cli/src/commands/doctor.test.ts.
• 2026-06-22T04:47:42Z: Opened Cycle 2 by adopting feat/388-ghes-graphql-endpoint; Cycle 1 implementation commit ec266d3 is present and the previous blocker was Docker availability.

Blockers

None