feat(ui): align supervision with Lead status

[boadij]

Summary

• Publish Lead herd-run start time and Pi context percentage as display-only metadata through the existing Herdr path, and project it only after Lead identity validation.
• Show responsive elapsed/context columns on Manager work rows, dropping elapsed before context as width tightens.
• Reuse Pi's semantic theme roles for supervision rows; Chief receives theme styling only and no telemetry columns.
• Keep persistence, project/work schemas, model context, staff/control surfaces, and Chief telemetry unchanged.

Rationale

This preserves ADR 0002's separation of durable intent from derived runtime state and ADR 0012's Manager-owned project resolution. It reuses the canonical herd-run timing from PR #19 and respects the boundaries established by PRs #93, #184, and #201. The implementation follows the applicable Pi 1.0.0 and Herdr 0.9.3 contracts without adding polling, persistence, or protocol changes.

Validation

• Focused suites: Herdr (67 passed), supervision (54 passed), presentation (75 passed), controller lifecycle + extension contract (97 passed)
• npm run check (792 passed, 1 skipped)
• npm run build
• npm run package:audit
• npm run smoke -- manager-recovery
• git diff --check

Closes #199

[boadij]

Follow-up for External Review #2:

• Finding: paused/conflict work marker color incorrectly followed the live Lead lifecycle.
• Rationale: work-status precedence must govern both marker shape and color; only active rows use a validated Lead lifecycle. Paused markers are muted and conflict markers are warning-colored.
• Changes: aligned marker-color precedence with marker-shape precedence and extended the existing regression test for active/success, paused/muted, and conflict/warning.
• Internal review: no findings.
• Validation: npm test -- extension/presentation.test.ts — 75 passed; npm run check — 792 passed, 1 skipped; git diff --check — passed.