Bug report URL path segments are ordered /bugs/{vendor} instead of /{vendor}/bugs
Description
Bug report URLs returned by the API and used by the web app put the static segment first and the vendor slug second, for example https://codmir.app/bugs/anthropic/1 and https://codmir.app/bugs/anthropic. The desired ordering puts the vendor first and the resource type second, for example https://codmir.app/anthropic/bugs/1 and https://codmir.app/anthropic/bugs. Vendor-first ordering makes the vendor the root of its own namespace, which reads better, groups all of a vendor's resources under one path prefix, and leaves room for sibling resource types beyond bugs without reshuffling the hierarchy later. Changing this affects URL generation, routing, and any links already emitted, so redirects from the old shape to the new one will be needed to avoid breaking existing report links.
Steps to Reproduce
1. File a bug report against any vendor, for example Anthropic. 2. Look at the url field returned in the response, or open the report in the web app. 3. Observe the path shape.
Expected Behavior
The vendor slug comes first and the resource type second: https://codmir.app/anthropic/bugs/1 for a single report, and https://codmir.app/anthropic/bugs for the vendor's report list.
Actual Behavior
The static segment comes first and the vendor slug second: https://codmir.app/bugs/anthropic/1 for a single report, and https://codmir.app/bugs/anthropic for the vendor page.
Environment
Product
Codmir bug reporting platform
Environment
Codmir MCP connector and web app, observed via the report_bug tool response url field.
Activity
No comments yet.
