Repository navigation
Wiki projection fails the whole run when folders differ only by case #1787
Description
Problem
plan_wiki_projection raises ValueError: Wiki projected scopes must be unique when compared as portable paths when two source folders differ only by letter case, for example marketing/Teams and marketing/teams (indexing/wiki_projector.py:425 and :446).
The error fails the whole projection run. Every later run fails the same way, so that project's wiki stops updating with no message to the user.
Evidence
- Basic Memory Cloud production: 69 failures since 10-11 (Logfire issue #2636). It currently recurs every day on one workspace.
- An earlier occurrence on another workspace was
customers/CPCagainstcustomers/cpc.
Expected
A case-only folder collision must not stop the rest of the project's wiki. Options:
- project both folders into distinct portable scopes, for example with a stable suffix;
- or skip the colliding scope and record a diagnostic the user can see and fix.
The portable-path uniqueness rule stays, because it protects case-insensitive sync targets. What changes is that one collision no longer fails the whole run.
Acceptance
- A test with two folders that differ only by case: projection completes for the other scopes, and the collision is reported, not raised.
Activity
claude commentedon Oct 20, 2026
Claude finished @phernandez's task in 15s —— View job
Triage
marketing/Teamsvsmarketing/teams) fails the whole wiki projection run. That workspace's wiki then stops updating on every later run, with no user-visible message. Production has 69 failures since 10-11 (Logfire #2636), and it recurs daily on one workspace.src/basic_memory/indexing/wiki_projector.py)Notes
wiki_projector.py(lines ~410, 425 and 446). The fix should cover all three, since the issue only cites two.fix(core): report case-only Wiki scope collisions instead of failing …