Repository navigation
Conversation
Retain query-preserving redirects and keep registry, catalogs, handlers, font subset and route tests aligned. Ultraworked with [omo](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: sisyphus-dev-ai <sisyphus-dev-ai@users.noreply.github.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 36 files
Shadow auto-approve: would not auto-approve because issues were found.
Re-trigger cubic
Navigate to /token-counter and /pipe themselves instead of loading the destination directly, assert the browser was redirected from the retired path, and check a control unique to each landing tool. The 301 and Location checks stay as they were.
There was a problem hiding this comment.
All reported issues were addressed across 2 files (changes from recent commits).
Shadow auto-approve: would not auto-approve because issues were found.
Re-trigger cubic
#format-btn also exists on JSON Schema Studio; #json-empty-state is unique to the formatter. Assert redirectedFrom() through optional chaining so a missing redirect fails as an assertion instead of a TypeError.
There was a problem hiding this comment.
All reported issues were addressed across 2 files (changes from recent commits).
Shadow auto-approve: would not auto-approve because issues were found.
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
Parse redirectedFrom() only after asserting it exists, compare the pathname exactly instead of suffix-matching the full URL, and drive /pipe and /token-counter with a query string so the redirect's query preservation is asserted on both the Location header and the landed URL.
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would require human review. Retires token-counter and pipe: handlers, registry, i18n, docs, and tooling references removed. The claimed 301 redirects preserving bookmarks/query strings aren't visible in the provided diff (routing diffs omitted), so the public URL change needs human sign-off.
Re-trigger cubic
1 participant
Summary
refactor(routes): retire token counter and pipe. This is logical change 2/11 in the dependency-ordered product-audit release stack.
Refs #969
What changed
5aa335cca3e2ecb40cf450d8cc9a46ed04ef8b68; validated tree:70ea8cffb37fb493ba30ccff8085c24c85993278.Why
Remove the retired token counter and pipe routes without leaving broken registry entries, fonts, or bookmarks.
Verification
bun run buildpassed on this exact candidate tree.npm test -- --maxWorkers=2passed on this exact candidate tree.Four retired URL/slash/query fixtures returned the correct 301 targets; no retired cards or sitemap entries; 45 public tools and 3 dev games.
Final combined tree additionally passed 801 unit tests and all 293 Playwright tests with retries disabled, plus all 48 primary tool workflows at desktop and mobile. The exploratory Color Converter exact-HEX boundary remains a documented pre-existing defect; its runtime is unchanged by this stack.
Risk & rollback
Summary by cubic
Retires the token counter and pipe routes (Refs #969).
/token-counterand/pipenow 301 to/prompt-template-builderand/json-formatterinstead of rendering their pages, so existing bookmarks and query strings keep working; the production catalog drops from 47 to 45 tools.Refactors
Rollout
Written for commit 6135db1. Summary will update on new commits.