openplanr 1.4.3
Patch Changes
Four improvements that close real workflow gaps in
openplanr linear push,openplanr linear tasklist-sync, and the per-typeupdatecommands.Granular push scope (BL-012).
openplanr linear pushadds--no-cascadeand redefines--push-parentsto be upward-attachment only.--no-cascadeon EPIC/FEAT pushes skips descendants (stories, tasklists, linked QT/BL). No-op for leaves.--push-parentsno longer drags in the parent's other children. PushingTASK-004 --push-parentsnow creates EPIC + parent FEAT + this tasklist only — not the feature's sibling stories.
TASK status now propagates to Linear (BL-014).
openplanr linear pushresolves a workflow stateId for the merged TaskList issue using an aggregation rule across all task files under the feature: alldone→ Linear Done, anyin-progress→ Linear In Progress, mix of done+pending → In Progress, allpending→ Linear Todo. Closes the gap whereTASK-006 status: donelocally left Linear's TaskList in Backlog.Bulk subtask completion (BL-015).
openplanr task update,openplanr quick update, andopenplanr updateadd--all-doneand--all-pendingflags that set the frontmatter status AND flip everyN.Mtask checkbox in the body in one operation. Replaces the manualsed-or-edit-each-box workflow when shipping a feature.tasklist-sync no longer skips healthy issue UUIDs (BL-016).
openplanr linear tasklist-syncpreviously rejected every task file whoselinearIssueIdwas a UUIDv4 — the entire population of healthy task files — because a shape-based pre-screen flagged them as "looks like a workflow state UUID." Linear issue ids and workflow-state ids are both UUIDv4 and indistinguishable by shape, so the pre-screen has been removed; the existingisLikelyLinearIssueIdcheck still rejects truly malformed values likeENG42.Backward-compat note: scripts that relied on
--push-parentscascading downward will see fewer entities pushed.