GitHub issue ingestion misses owner__repo relayfile paths

[miyaontherelay]

Problem

Factory did not ingest a GitHub issue that exists in relayfile cloud because the issue path uses the owner__repo shape.

Test case:

• GitHub issue: Telegram: add ergonomic telegramClient + fill catalog/receipt gaps to match slack/linear/github relayfile-adapters#222
• Label: factory
• Direct relayfile read succeeds at:

/github/repos/AgentWorkforce__relayfile-adapters/issues/by-id/222.json

Payload includes the expected label:

{
  "title": "Telegram: add ergonomic telegramClient + fill catalog/receipt gaps to match slack/linear/github",
  "labels": ["factory"]
}

But factory factory loop --config ./factory.config.json --dry-run completed without mirroring or reporting this issue.

Likely cause

githubIssuePathParts() appears to accept split owner/repo paths like:

/github/repos/<owner>/<repo>/issues/by-id/<number>.json

but not compact relayfile paths like:

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

PR paths have some support for owner__repo elsewhere, but issue ingestion seems to miss it.

Expected behavior

Factory should ingest factory-labeled GitHub issues from both relayfile GitHub path shapes, if both are valid mount outputs:

• /github/repos/<owner>/<repo>/issues/...
• /github/repos/<owner>__<repo>/issues/...

Acceptance criteria

• githubIssuePathParts() and related read-candidate logic parse owner__repo issue paths.
• factory run-once --dry-run sees AgentWorkforce__relayfile-adapters/issues/by-id/222.json as a GitHub issue.
• A factory-labeled issue at that path is mirrored/routed to repo label relayfile-adapters.
• Add regression coverage for by-id, flat JSON, and nested meta.json/metadata.json shapes where applicable.