PR Summary

What problems was I solving

When the management UI view models were extracted into the @architect/management-ui-view-model package, the app-side duplicate of the session expiration handler (app/main/api/session-handler.ts) and its tests were left behind with no remaining production callers. This dead code adds noise and could mislead future maintainers into editing the wrong copy.

What user-facing changes did I ship

None. The canonical session handling logic remains in view-model/main/session-handler.ts and continues to redirect unauthenticated users to /login on HTTP 401 responses while leaving 403 responses alone.

How I implemented it

Verified that no production code in the management UI app imports from the app-side session handler, then deleted architect/management-ui/app/main/api/session-handler.ts and its companion test file architect/management-ui/app/test/session-handler.test.ts. The active tRPC client setup now consumes createSessionAwareFetch from view-model/main/session-handler.ts via view-model/main/api-client.ts, which is re-exported through app/main/api/api.tsx.

Description for the changelog

Removes the orphaned management UI app-side session handler and its tests, which were superseded by the view-model package's canonical implementation. There are no user-facing behavior changes.

Remove dead app-side session handler API code

low1 file
Deletes the orphaned duplicate `app/main/api/session-handler.ts`; the canonical implementation now lives in the view-model package and is the only one used in production.

Remove dead app-side session handler tests

low1 file
Removes the test file for the deleted duplicate session handler module.