Motir-AI creates and updates work items directly in a connected Plane project from a Motir plan, mirrored as motir-core work items and kept in sync. Plane is the open-source, often self-hosted member of the set.
Adapter only — the engine comes from Plan in Jira (blocked_by it). This story supplies the Plane side: the REST write calls for work-item create/update, the Motir → Plane field mapping (project, state group, priority, labels, parent, blocking relations), and the webhook/sync path back. It must not re-implement the mapping layer, the mirror map, or the sync loop.
Verified preconditions. Plane is already a live connected source — the OAuth connect flow including the self-hosted base URL (7.16.13 — Plane OAuth connect flow) and the Plane REST connector (7.16.4b — Plane connector) shipped done, with the app registered (7.16.7b — register the Plane OAuth app). The self-hosted case is the one that needs care on write: an on-prem instance's version may lag the API shape the write path assumes, so version detection belongs in this story's scope.
Boundary. WRITE direction only — importing from Plane stays with Issue importer in Epic 7.
Not yet expanded into subtasks — expand when picked up.