Repository navigation
v0.16.2
Fixed
- Registering the same repo path under two project names silently created duplicate decisions
forever — found live right after the brand-decision-review feature shipped: this machine's own
consus-projects.jsonhadconsusandworkboth pointing at the same repo path, and every
scan synthesized a separate decision per project name (decision:<project-name>:<file-path>),
so the same brand decision showed up twice in the queue.POST /api/projectsvalidated name
uniqueness but never path uniqueness. Now returns409naming the existing project when the
resolved path is already registered under a different name.
Changed
docs/api-reference.md— documentedGET/POST /api/surveysandGET /api/surveys/:id
(previously shipped, undocumented), and the new path-uniqueness check onPOST /api/projects.
🤖 Generated with Claude Code