#21146 Keep Chief Home in the native workspace sidebar

Home and its Chief conversations use the native workspace group and pane layout, so expanding Home moves the following rows down and terminal or browser splits stay in the selected Chief workspace. Home stays pinned, keeps its name and house icon, and preserves user-renamed child workspaces.

This follows #21063. Home’s plus button and Chief Settings create conversations through the native navigation path. The canonical Home workspace cannot be deleted.

Validation

• All 17 scoped static checks and the localization audit passed for the app implementation (11 catalogs, 9 locales, no parity errors).
• Fleet job f875ab8ffddc55387bad192d compiled app commit 1abddf0b6b3fd32b294643dd573736845f4b8a62. The subsequent change only makes the Python regression wait for published surface snapshots; app sources are identical.
• The native Home runtime regression passed in the normal tagged app and a separate fixture process: native selection, pinning, group disclosure, terminal splits, and canonical Home close protection.
• Two fixture Chiefs restored under Home. Expanded and collapsed screenshots were inspected with no overlapping sidebar rows. A nested Chief supported Chief, terminal, and browser surfaces in three distinct panes.
• CUA button clicks were unavailable because the approval broker could not authenticate the host process. Home’s plus and Settings creation buttons were not clicked during this verification.
• The shared HQ publisher rejected valid internal resource symlinks. The artifact hash, embedded commit, bundle ID, and all symlink destinations were verified, then the unchanged archive was restored and launched locally as issue-21063-native-home-sidebar.

Changelog

Fixed: Keep Home and its nested Chiefs in the native workspace sidebar with ordinary pane splits.