feat(depot): unify the Labby and Depot control plane

[jmagar]

Summary

Unify Depot into the existing Labby control-plane frontend and expose full Bazaar search without creating a second operator UI.

Why This Exists

Depot authority and Labby operator workflows need one same-origin experience with explicit compatibility boundaries.

Resolution

This branch freezes the compatibility contract, wires the shared frontend, closes review gaps, and expands Bazaar search coverage.

Reviewer Considerations

Review authority boundaries, same-origin assumptions, mutation ownership, and real-data compatibility first.

Behavior Changes

Operators can use the Labby frontend for Depot control-plane workflows and search the full Bazaar catalog.

Implementation Summary

• Compatibility contract
• Unified control-plane wiring
• Frontend remediation
• Full Bazaar search and result polish

Verification

• Branch is based on current origin/main
• Full CI and product qualification remain required before ready-for-review

Risk

Medium; frontend authority and mutation routing require focused review.