fix(planner): regenerate the stale plan-pane-bodies graph record

[kevinthelago]

Summary

• The graph-parity guard (graphParity.test.ts) caught real drift: FocusedBodies.tsx moved on to FeaturesStageBody/PlannerLibraryPane (The project planner shows neither library — present both the components and algorithms panes #4265), but the plan-pane-bodies seed record — its provides-tagged graph twin authored in Migrate the focused project pane into the graph (epic #3604) #4227 — was never regenerated, so the runtime loader was still vendoring the old FeaturesBody/PlannerComponentsPane switch wherever the pane composes FocusedBodies from the graph.
• Re-ran scripts/gen-pane-graph.cjs to bring plan-pane-bodies.json and its derived graphPlatform.ts back in sync with the live file (verified every other pane/bodies/session/list record is still byte-identical — regenerating them would only have stripped their derived composes/props metadata for no content change, so those were left untouched).
• Regenerated platform-modules.json (UPDATE_KITS=1) to match the updated registration set.

Status of owned issues

• Discovery: add a cloud outage response plan (discovery/outage_response.md) #3989 (Discovery cloud-outage-response dimension) — already merged (Discovery: add a cloud outage response plan (discovery/outage_response.md) #4011).
• Migrate the planner/Projects panes into the built-in UI / graph (thread 5 of #3782) #3787 (planner/Projects panes → graph) — full scope already delivered and live-mounted via already-merged Migrate Projects page into the base-studio-code components graph (#3604) #3874 (ProjectsList) + Migrate the Planning session into the graph — the planner's flagship page (epic #3604) #4224 (Planning session shell) + Migrate the focused project pane into the graph (epic #3604) #4227 (focused pane) + Migrate the planner stage bodies into the graph (epic #3604) #4230 (stage bodies), all under epic Epic: load the app's UI from the graph at runtime #3604. This PR is the one loose end that verification turned up, not new Migrate the planner/Projects panes into the built-in UI / graph (thread 5 of #3782) #3787 scope.

Also logged in DECISIONS.md: ~15 stale DB-only duplicate/draft component records were found in the local component graph during verification (not seed-backed, so they don't affect the shipped app). The planner role's bsc ui scope is read-only, so I can't prune them myself — flagged for a session with UI write access.

Test plan

• npm run typecheck — clean
• npm run lint — 0 errors (225 pre-existing warnings outside this lane)
• npm test — 728/729 files pass; the 1 remaining failure (reactUiKit.gen.test.ts, 2 tests) is pre-existing on develop before this change, unrelated to this lane (src/features/designs kit-hash drift)
• cargo test -p plandb -p bsc-blueprint — 150/150 pass
• cargo clippy -p plandb -p bsc-blueprint --all-targets -- -D warnings — clean
• graphParity.test.ts specifically re-verified green after the fix

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01PRyWeiBv8xpzk5VdfAQkVy