Plan in Linear
Motir-AI creates and updates issues directly in a connected Linear team from a Motir plan, mirrored as motir-core work items and kept in sync.
Adapter only — the engine comes from Plan in Jira (blocked_by it). This story supplies the Linear side of that engine and nothing else: the GraphQL mutations for issue create/update, the Motir → Linear field mapping (team, state, priority scale, labels, parent/sub-issue, blocking relations), Linear's own rate-limit behaviour, and the webhook subscription that syncs vendor-side edits back. It must not re-implement the mapping layer, the mirror map, or the sync loop.
Verified preconditions. Linear is already a live connected source — the OAuth connect flow (7.16.12 — Linear OAuth connect flow) and the Linear API client (7.16.4 — Jira + Linear connectors) shipped done, and the OAuth app is registered (7.16.7a — register the Linear OAuth app). Re-authorization requests the write scope; no new app registration.
Boundary. WRITE direction only — importing from Linear stays with Issue importer in Epic 7.
Not yet expanded into subtasks — expand when picked up.