GeezerVison

Summary

• A table or knowledge base opened from inside a folder rendered Tables / name, dropping every folder between it and the root, while a file's header showed the full Files / docs / name path. The detail pages never read the resource's own folderId, so the trail could not include it.
• Rather than patch the two headers, all six foldered surfaces (Files, Tables, Knowledge — list and detail) now build their trail from one shared builder:
  • folderAncestorChain(folderId, lookup) in lib/folders/tree.ts is the single upward walk. Both getFolderPath variants delegate to it. The two lock predicates deliberately keep their inline walks — they short-circuit at the first locked ancestor on a per-row render path.
  • folderBreadcrumbItems takes a trailing slot for detail pages, as a discriminated union so an open-folder rename can't be passed alongside it and silently dropped.
  • useFolderAncestors owns the folder tree plus the foldersResolved staleness rule; useFolderNavigation delegates to it.
  • FOLDERED_RESOURCE_HEADERS owns each resource's root label, root icon, and list path, which seven sites previously restated.
• Files' list trail moved off splitting the materialized path string, which couldn't tell two same-named siblings apart, onto the shared parentId walk.
• Also fixes the Files loading trail, whose folder crumbs used the nuqs setter while rendering on the file detail route — appending ?folderId= to the open file's own URL instead of navigating to the list.

Type of Change

• Bug fix

Testing

tsc --noEmit, bun run lint:check, and bun run check:react-query / check:api-validation / check:client-boundary all clean. 2902 tests across 249 files pass, including new coverage for the chain walk and the detail-page trail; I verified those tests fail against a deliberately broken implementation.

Not yet verified in a browser — the dev server won't start from a git worktree (Turbopack resolves the outer repo as root). The visual change is the folder segments now appearing in table/KB headers, so it's worth a look on the preview before merge.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)