Workspace app registry has no home path, so every cross-app link targets the app root

# Workspace app registry has no home path, so every cross-app link targets the app root

**Version:** `@agent-native/core` 0.176.4, `@agent-native/dispatch` 0.33.0.

**What happens.** `WorkspaceAppManifestEntry` carries `id`, `name`, `description`, `path`, `url`. The org switcher (`visibleOrgAppLinks`) and Dispatch app cards link to `path`, which is the template's public marketing route. `app.homePath` exists in the app config schema but is not part of the registry, so a sibling app cannot know where a signed-in user should land.

**Expected.** Publish `homePath` in the manifest entry (default `/home`) and have the org switcher and Dispatch cards link to `path + homePath` for signed-in users.

**Workaround used.** Rely on the root handoff (report 08) so the root itself redirects.

Start with the WorkspaceAppManifestEntry registry and the app config schema, then trace visibleOrgAppLinks and the Dispatch app cards to see how they consume path. Publish homePath with a /home default and update signed-in links to combine path and homePath; verify both link destinations.

Written by the indexing model from the issue text.