[99f61c8c] Stuck indicator on task cards and task detail

[roboco-app]

Surface the wedge-ledger stuck state on task cards and task detail. Frozen cross-cell contract (identical text in the backend slice's brief; changes route back through main-pm): the task API payload carries active_time_since_progress (active time since last progress-fingerprint movement), open_wedge_strikes (count), and wedge_cycle (recorded actor/verb/timestamp entries). Build a stuck indicator that shows the active time since last progress movement plus the recorded actor/verb cycle, driven by open_wedge_strikes or a blocked-for-human status. Place data fetching in panel/src/hooks and presentation in panel/src/components per the architectural standard (no models/routes/components in hooks; no models/routes in components). This is READ-ONLY surfacing: no remediation buttons or actions — decisions stay with the PM/CEO. Match the existing panel's design system and tokens; functional surfacing, not a redesign. The backend slice is being built in parallel: if its API is not merged when QA runs, mock the contract fields in frontend tests. Run the panel gate (make panel-gate) before submitting.

[github-actions]

Thanks for opening your first pull request on RoboCo!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• make quality — ruff format check, ruff check, mypy, pytest (≥80% coverage), and the rest of the gate
• Panel changes pass pnpm lint and pnpm exec tsc --noEmit (run from panel/)
• No # noqa / # type: ignore shortcuts; pre-existing violations in touched files are fixed
• Added an entry under ## [Unreleased] in CHANGELOG.md
• Signed the CLA (the bot will prompt you on this PR)
• Signed your commits — master requires verified signatures (SSH signing setup)
• Updated any affected docs under docs/

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.