Originally created by: adityaharishch
feat(triage): write board-hygiene fixes back to the real tracker (commit fefb681) added a multi-provider write-back layer (src/intelligence/ticket_update/) so board-hygiene fixes apply straight to the user's tracker.
Jira is verified live on the KAN board (due date set, label add-op, story-points discovery→redirect, done-transition, parent/epic picker — all confirmed against the real instance).
The other four providers are implemented + unit-tested but NOT exercised against a live instance (the dev account only has Jira active).
Per provider, confirm each field write lands correctly and the redirect fallbacks behave:
issueUpdate for dueDate / assignee (viewer) / priority / estimate / parent / title / description / close (completed state); labels redirect; parent picker (team issues)POST /issues/{parent}/sub_issues with sub_issue_id = child REST id); due/priority/story-points redirect to Projects v2; parent picker (repo issues)Connect a test workspace per provider (or use a teammate's), run meridian ticket-parents / meridian ticket-update against a throwaway ticket, and verify the change on the provider's UI. Pay attention to:
:PAT basic, Trello key+token query)Each provider's checklist above ticked, with any payload/endpoint fixes committed.