fix(task-detail): guard against undefined task in TaskDetail render

[posthog]

Problem

Opening a task in the Code app could hard-crash the whole TaskDetail view with Cannot read properties of undefined (reading 'repository'), thrown inside React's render loop.

useRefreshedTask (added in #3758) returned its query data as if it were always a Task. But the route components subscribe to the same query key without initialData; when their observer creates the cache entry first while the fetch is still in flight, React Query drops useRefreshedTask's initialData and data comes back undefined. That undefined flowed straight into getTaskRepository, which dereferenced task.repository with no guard and threw during render.

This is a same-day regression from #3758 on a core flow (opening a task).

Changes

• useRefreshedTask now returns data ?? initialTask, restoring the pre-regression guarantee that useTaskData always receives a defined task.
• getTaskRepository is now null-safe on its task argument as defense in depth.

How did you test this?

• Added a unit test to useRefreshedTask.test.tsx asserting the hook falls back to initialTask when the query yields undefined data.
• Added repository.test.ts covering getTaskRepository with undefined / null / missing / populated inputs (plus parseRepository).
• Verified both new tests fail without the fix and pass with it.
• Ran pnpm --filter @posthog/ui typecheck and pnpm --filter @posthog/shared typecheck (clean) and Biome lint on the changed files.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code from this inbox report.

[trunk-io]

🚫 This pull request was removed from the merge queue because it was closed by @tatoalo. See more details here.

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 318369c.}