Planning PR

This is a commit-placement advisor, not part of the normal ln-* execution path.

Most memory/SPEC.md and memory/PLAN.md edits stay on the active feature branch. A separate planning PR is useful only when planning docs become a shared serialization point for multiple branches.

Default stance

Stay on the current feature branch for:

• one-line status ticks or typo fixes
• marking the active frontier item done
• routine ln-build / ln-scope canonical reconciliation
• small SPEC/PLAN edits needed to explain the current code change
• local planning edits that do not affect other active branches

Do not invoke Linear, Graphite, or branch creation just because a planning file is touched.

When to recommend a planning PR