Linear create writeback should preserve GitHub mirror repo labels

[miyaontherelay]

Problem

Factory creates Linear mirror drafts for factory-labeled GitHub issues with repo labels like:

{
  "labels": [{ "name": "relayfile-adapters" }],
  "source": {
    "provider": "github",
    "owner": "AgentWorkforce",
    "repo": "relayfile-adapters",
    "number": 224
  }
}

In the live repro, AgentWorkforce/relayfile-adapters#224 was mirrored to Linear as AR-311, but the resulting Linear issue did not appear to retain the repo label needed for factory dispatch routing. Factory then fell back to repos.default.

Expected

Linear issue create writeback should reliably apply configured label names or expose a clear contract requiring label IDs. If label names cannot be resolved, the writeback should fail loudly or surface a dead-letter reason rather than silently creating an unroutable issue.

Acceptance criteria

• Creating a Linear issue with labels: [{ "name": "relayfile-adapters" }] applies the matching Linear label when available.
• If labels by name are unsupported, document and enforce the required config shape (labelIds, etc.).
• Writeback result/dead-letter includes enough detail to explain label resolution failures.
• Factory-created GitHub mirror issues retain repo routing labels after materialization.

Related

• Prior related issue: Linear issue create writeback should accept team keys and label names #225
• Source issue used in repro: GitHub: export shared mount-path parser for issues and PRs #224
• Repro Linear mirror: AR-311

[miyaontherelay]

Factory-side follow-ups filed: AgentWorkforce/software-garden#31 for Markdown Source route fallback and AgentWorkforce/software-garden#32 for live startup backfill.

[miyaontherelay]

Clarification on ownership from the factory repro: relayfile-adapters should not need to own factory routing policy.

Factory should derive the Linear routing label from the GitHub source repo when it creates the mirror payload. For example, AgentWorkforce/relayfile-adapters#224 should be mirrored with an explicit relayfile-adapters label in the Linear create payload.

The adapter-side responsibility here is narrower: if the caller supplies labels: [{ "name": "relayfile-adapters" }] or equivalent label IDs, Linear create writeback should apply that label reliably, or fail/surface a clear dead-letter reason if it cannot resolve/apply it. It should not silently create an unroutable issue.