dev plan push by issue number

[JPDuchesne]

dev plan push by issue number

Goal

dev plan push 34 works exactly like dev plan pull 34: the number resolves to the linked plan file in the workspace, no file path required. Alongside it, fix the header-detection gap that produced the misleading "no ai-flow header" failure on a file that visibly had one.

Motivation

Pushing is currently asymmetric with pulling. dev plan pull <n> resolves the number to a file via the workspace lookup, but dev plan push only takes a file path (or defaults to the sole linked plan — which fails in a workspace with several). The user-facing consequence: dev plan pull 34, edit, then dev plan push requires hunting for the exact .plan.md path that pull just derived.

Separately, dev plan push <file> failed with has no ai-flow header — link it first on a file that had the header — because Cursor's plan tooling rewrites plan files with its YAML frontmatter on top followed by a blank line, and Dev::Plan::Header::PATTERN is \A-anchored. Content.parse (lib/dev/plan/content.rb) handles frontmatter-above-header since the gh-37 fix, but the blank line between the closing --- fence and the <!-- ai-flow comment still defeats the anchor. Every pulled-then-edited-in-Cursor plan hits this, so it belongs with the push UX fix.

Changes

1. Accessor#push accepts a number (lib/dev/plan/accessor.rb)

• Usage becomes dev plan push [<file>|<n>] [--org].
• An argument matching \A\d+\z is an issue number: resolve owner_repo = target_repo(org:) and path = find_linked_plan(owner_repo, number) — the same lookup pull uses. No linked file → UsageError: no linked plan for <owner_repo>#<n> — run dev plan pull <n> first.
• Anything else stays a file path; bare dev plan push keeps the sole-linked-plan default.
• --org mirrors pull's flag so org plans push by number too (a file path never needs it — the repo comes from the header).

2. Header detection tolerates blank lines (lib/dev/plan/content.rb)

• In Content.parse, strip leading blank lines from the text handed to Header.split — in both paths (header-first, and header-after-frontmatter). Equivalent alternative: anchor the pattern with \A\s*; prefer the strip so Header.split's contract stays "header at start".
• Content#render already rewrites canonical order (header, frontmatter, body), so affected files self-heal on the next sync; no migration needed.

Tests

• test/dev/plan/accessor_test.rb: push by number finds the linked file and PATCHes; push by number with --org targets the org plans repo; push by an unknown number raises the pull first usage error; push by file path unchanged.
• test/dev/plan/content_test.rb: parse the exact Cursor-written layout — YAML frontmatter, blank line, ai-flow header, body — and assert the header, frontmatter, and body all survive; assert render restores canonical order.

Docs

• share/cursor-skills/ai-flow/SKILL.md and the README dev plan bullet: usage line gains push [<file>|<n>].

Out of scope

• Changing the divergence guard or merge flow — push semantics are untouched beyond argument resolution.
• Teaching old releases anything: 0.2.70-era push also pushed Cursor frontmatter into the issue body (pre-Content parser); that is already fixed on main and ships with the next release cut.

Test plan

• dev plan push <n> from a workspace with several linked plans pushes the right one.
• dev plan push <n> --org pushes an org plan.
• dev plan push <n> without a local linked file errors with the pull first guidance.
• A Cursor-rewritten plan file (frontmatter, blank line, header) pushes without the "no ai-flow header" error.
• bundle exec rake test green.