[waleedlatif1]

Summary

Takes the redesigned organization view (#9708), the People page redesign (#9720) and its landing test fix (#9715) off staging, so main can keep releasing while the new UI ships all at once with #9687, which already carries all three.

After this, staging's /o UI matches main except 6 integration files that carry functional work later PRs added to the legacy view:

• Multiple accounts per integration (feat(search): connect multiple accounts per integration #9716).
• Jama and Flow saved credentials (feat(integrations): add Jama Connect and Flow Engineering #9723). Connect and Reconnect on the legacy detail page now open the saved-credential modal, and Disconnect goes through Search, since feat(integrations): add Jama Connect and Flow Engineering #9723 wired those only into the new view.

Only views are reverted. Hooks, contracts, key factories and lib helpers stay at staging's versions, and the legacy view adapts to them. Exports that only the redesigned views used are unexported where their own file still uses them, or deleted, so the unused-exports baseline only shrinks (2 entries).

Three API routes go: Home calendar, Home email and search-history sources. Only the new view called them, and none is on main. No reverted commit has a migration or schema change.

Merging this into #9687

#9687 already contains these commits, so a plain staging merge there would delete the org view (257 conflicting files in a dry run). After this merges, #9687 takes staging in three steps:

1. Merge staging up to this commit's parent.
2. git merge -s ours <this squash commit>.
3. Merge the rest of staging.

A simulation changed 0 org-view files on #9687 and brought in every other staging commit.

Type of Change

• Other: revert, held for Build the Platform Core, Chat, and member integrations UI #9687

Testing

• type-check passes.
• check:test-types, explicit-any, skills, biome, test-patterns, boundaries, react-query, source-conventions, file-names, utils, client-boundary, comment-hygiene, api-validation:strict, guidance-refs and unused-exports all pass. The unused-exports baseline shrank by one entry.
• Focused vitest: 351 files, 2,830 tests pass, covering app/o, all of hooks/, credential groups, org lib, search, People, _shell and workspace Home.
• test-assistant-actions-e2e.ts is back at main's legacy-view selectors.
• Needs a staging check of /o Home, Integrations (including Jama or Flow connect) and People after merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Ignored	Preview	Nov 6, 2026 7:02pm UTC

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The PR changes organization pages and a bounded set of workspace search behavior.

Remove the unused hook imports to satisfy the repository requirement before merging.

Summary

Restores the legacy organization and People views while keeping later account support.

• Organization Home and Search return to the legacy app pages.
• The organization People page returns to its legacy chart and directory.
• The legacy Integrations page keeps account and saved-credential actions.
• Organization Links returns to the app's resource-table view.
• The redesign-only Home and search-history endpoints are removed.
• Workspace knowledge search returns to its prior result and filter flow.

_{Reviews (2) · Last reviewed commit: "fix(org): keep staging's shared modules ..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[greptile-apps]

Comments Outside Diff

These findings could not be posted inline.

•  Removed hooks leave unused imports apps/sim/hooks/queries/search-history.ts:9 ▶

  search-history.ts restores removeSearchHistorySourceContract and SearchHistoryResponse, but neither is used. oauth-provider.ts also restores unused imports of useEffect, OAUTH_SEARCH_READ_SCOPE, and oauthScopeSatisfies.

  CLAUDE.md requires deleting unused imports. Remove these imports along with the hooks that needed them. This repository requirement must be satisfied before merging.

  Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!