Problem
Factory has fallback logic to infer a GitHub mirror's source repo from the Linear issue description when labels are missing. It currently handles plain source lines like:
Source: https://github.com/AgentWorkforce/relayfile-adapters/issues/224
But it does not handle Markdown link forms like:
Source: [https://github.com/AgentWorkforce/relayfile-adapters/issues/224](<https://github.com/AgentWorkforce/relayfile-adapters/issues/224>)
Observed with Linear AR-311, mirrored from AgentWorkforce/relayfile-adapters#224: factory triage AR-311 routed to factory via repos.default instead of relayfile-adapters because the mirror did not have the repo label and the Markdown Source fallback failed.
Expected
githubMirrorRepoForIssue() / source URL parsing should accept:
- plain GitHub issue URLs
- Markdown link syntax
[text](url)
- autolinks wrapped in
<...>
- structured
source.url when present
Acceptance criteria
- Label-less GitHub mirror issues route to the configured repo using Markdown Source links.
- Regression test uses the exact
Source: [https://...](<https://...>) shape.
- If both structured
source and description source exist, structured source remains preferred.
Related
Problem
Factory has fallback logic to infer a GitHub mirror's source repo from the Linear issue description when labels are missing. It currently handles plain source lines like:
But it does not handle Markdown link forms like:
Observed with Linear
AR-311, mirrored fromAgentWorkforce/relayfile-adapters#224:factory triage AR-311routed tofactoryviarepos.defaultinstead ofrelayfile-adaptersbecause the mirror did not have the repo label and the Markdown Source fallback failed.Expected
githubMirrorRepoForIssue()/ source URL parsing should accept:[text](url)<...>source.urlwhen presentAcceptance criteria
Source: [https://...](<https://...>)shape.sourceand description source exist, structured source remains preferred.Related
AR-311