Revisit GitHub issue discovery after relayfile-cloud#63

[miyaontherelay]

Context

Factory PR #25 added GitHub issue discovery that scans configured compact repo roots such as:

/github/repos/<owner>__<repo>/issues/by-id

in addition to the broad /github/repos root. This made factory-labeled GitHub issues discoverable when the relayfile-cloud GitHub root listing is shallow.

The cloud-side contract is being tracked in AgentWorkforce/relayfile-cloud#63.

What to do once relayfile-cloud#63 is resolved

Revisit factory's GitHub issue discovery path and align it with the finalized cloud discovery contract.

Expected review points:

• Keep compact alias scanning if aliases are the documented discovery surface.
• Prefer per-repo issue indexes such as /github/repos/<owner>/<repo>/issues/_index.json if that becomes the recommended discovery surface.
• Do not rely on /github/repos being recursively complete unless relayfile-cloud explicitly guarantees that behavior.
• Update tests around shallow root listings to match the finalized contract.

Current relevant code

• src/orchestrator/factory.ts: #githubIssuePaths() and githubIssueScanRoots(config)
• src/orchestrator/factory.test.ts: mirrors compact GitHub issues when the repo root listing is shallow

Related

• AgentWorkforce/relayfile-cloud#63
• Fix GitHub issue mirror dispatch #25