Fix procedure grid dispatch stability

[endymion]

Summary

• keep locally-run procedure cards labeled Local by carrying dispatch_mode through task creation, runner metadata writes, and display
• classify direct procedure runtime records as Local when they have procedure runtime host/pid metadata, even if older local runner code omitted dispatch_mode
• stabilize procedure cards by preserving subtitles and task metadata across sparse realtime updates, reserving the dispatch indicator row, restoring the Optimization Procedure badge label, and suppressing duplicate pending/timing rows inside the status body
• align grid and detail procedure layout so dispatch, relative timestamp, and elapsed duration live together in the header, above the status/progress area
• add focused regression coverage for dispatch display, realtime subtitle preservation, detail-mode timing placement, local dispatch metadata persistence, and direct procedure runtime classification

Verification

• npm test -- --runTestsByPath components/tests/ProcedureTask.optimizer-auth.test.tsx components/ui/tests/TaskStatus.test.tsx --runInBand
• npm test -- --runTestsByPath components/ui/tests/TaskStatus.test.tsx components/tests/ProcedureTask.optimizer-auth.test.tsx components/tests/procedures-dashboard.loading.test.tsx --runInBand
• npm run typecheck
• pytest plexus/cli/shared/test_experiment_runner.py plexus/cli/shared/command_dispatch_test.py plexus/cli/shared/test_command_dispatch.py -q

Notes

• npm run lint is currently blocked by existing dashboard lint tooling incompatibility; tracked separately in Kanbus as plx-6d94cc.