fix: remap vault URLs

Author: miohtama

.claude/docs/agent-tricks-and-troubleshooting.md

@@ -116,6 +116,21 @@ codex exec --json --sandbox read-only "Review uncommitted changes for correctnes
 
 Claude CLI is useful for independent second opinions, code reviews, background agents, and checking whether another agent's change makes sense.
 
+### Review timeout policy
+
+Every Claude CLI or Codex CLI review request must have an execution timeout of
+**at least 15 minutes**. Large diffs may take several minutes to inspect, and
+streaming output can remain quiet while the reviewer reads targeted files. Do
+not terminate a review merely because it has produced no final answer within a
+minute; check its stream or raw output file while allowing the full timeout.
+
+For review tools that expose their own timeout option, pass a value of 15
+minutes or greater, for example:
+
+```shell
+claude ultrareview master --timeout 15
+```
+
 Common commands:
 
 ```shell
@@ -251,9 +266,9 @@ claude -p "Review .claude/plans/my-plan.md for correctness and completeness. Foc
   --verbose
 ```
 
-If a grounded review produces no output after roughly a minute, stop it and
-switch to the no-tools inline review unless fresh repository inspection is
-strictly required.
+If a grounded review has not produced output, inspect its stream or raw output
+file while allowing the required 15-minute timeout. Only then switch to the
+no-tools inline review unless fresh repository inspection is strictly required.
 
 Notes:
 

CLAUDE.md

@@ -19,7 +19,7 @@ working on that area:
 ## Agent review workflows
 
 - **BLOCKING REQUIREMENT: before running ANY `codex` / `codex exec` or `claude` CLI command — reviews, sanity checks, or one-off runs — you MUST first read `.claude/docs/agent-tricks-and-troubleshooting.md`.** Do not invoke either CLI until you have read it in the current session. This is not optional and applies even when the call "looks trivial".
-- Follow its recommended invocation patterns for plan reviews, code reviews, PR reviews, tool restrictions, timeouts, and handling silent or hanging agent runs.
+- Follow its recommended invocation patterns for plan reviews, code reviews, PR reviews, tool restrictions, timeouts, and handling silent or hanging agent runs. Review requests must allow at least 15 minutes before being treated as timed out.
 - Always run non-interactive Codex reviews in **streaming mode** (`codex exec --json`) written to a raw file — never plain text mode piped through `tail`/`head`, which buffers output until completion and makes the run look hung.
 - `codex exec` selects the sandbox directly (`--sandbox read-only` for reviews) and does **not** accept `--ask-for-approval` (that flag is interactive-only).
 - Do not fall back to generic `claude --help`, plugin docs, or ad-hoc CLI flags until the local troubleshooting doc has been checked.

docs/cache-freshness-diagnostics.md

@@ -30,7 +30,7 @@ If those sources are refreshed at different times, the homepage and detail page
 
 - Vault summary metrics come from the top-vaults feed
   - Loaded in [src/routes/strategies/[strategy=yamlStrategy]/+layout.ts](/Users/moo/code/frontend/src/routes/strategies/[strategy=yamlStrategy]/+layout.ts)
-- The chart fetches `/trading-view/vaults/:id/metrics` client-side after hydration
+- The chart fetches `/vaults/:id/metrics` client-side after hydration
   - Implemented in [src/lib/top-vaults/VaultPriceChart.svelte](/Users/moo/code/frontend/src/lib/top-vaults/VaultPriceChart.svelte)
 - The frontend app code does not add SWR caching to this chart request
 

docs/chart-pages.md

@@ -1,25 +1,25 @@
 # Chart pages
 
-This document describes chart pages and chart navigation in the Trading Strategy frontend. It focuses on vault chart pages under `src/routes/trading-view/vaults/`, but also notes the shared charting libraries used elsewhere.
+This document describes chart pages and chart navigation in the Trading Strategy frontend. It focuses on vault chart pages under `src/routes/vaults/`, but also notes the shared charting libraries used elsewhere.
 
 ## Vault chart pages
 
 The vault chart pages linked from the top `Charts` menu are:
 
-- `/trading-view/vaults/cumulative-tvl-apy` - cumulative vault TVL by annualised return, with benchmark lines.
-- `/trading-view/vaults/yield-risk` - vault annualised return by TVL, grouped by risk level.
-- `/trading-view/vaults/yield-protocol` - vault annualised return by TVL, grouped by protocol.
-- `/trading-view/vaults/yield-chain` - vault annualised return by TVL, grouped by chain.
-- `/trading-view/vaults/current-peak-tvl` - current TVL by peak TVL.
-- `/trading-view/vaults/core3-risk` - stablecoin vault returns and TVL by CORE3 Probability of Loss.
-- `/trading-view/vaults/historical-tvl-chain` - historical vault TVL grouped by chain.
-- `/trading-view/vaults/historical-tvl-stablecoin` - historical vault TVL grouped by stablecoin.
-- `/trading-view/vaults/historical-tvl-protocol` - historical vault TVL grouped by vault protocol.
-- `/trading-view/vaults/stablecoin-chain-heatmap` - current stablecoin vault TVL by stablecoin and chain.
+- `/vaults/cumulative-tvl-apy` - cumulative vault TVL by annualised return, with benchmark lines.
+- `/vaults/yield-risk` - vault annualised return by TVL, grouped by risk level.
+- `/vaults/yield-protocol` - vault annualised return by TVL, grouped by protocol.
+- `/vaults/yield-chain` - vault annualised return by TVL, grouped by chain.
+- `/vaults/current-peak-tvl` - current TVL by peak TVL.
+- `/vaults/core3-risk` - stablecoin vault returns and TVL by CORE3 Probability of Loss.
+- `/vaults/historical-tvl-chain` - historical vault TVL grouped by chain.
+- `/vaults/historical-tvl-stablecoin` - historical vault TVL grouped by stablecoin.
+- `/vaults/historical-tvl-protocol` - historical vault TVL grouped by vault protocol.
+- `/vaults/stablecoin-chain-heatmap` - current stablecoin vault TVL by stablecoin and chain.
 
 Related vault list pages also include charts:
 
-- `/trading-view/vaults/stablecoins`, `/chains`, `/protocols`, and `/curators` use `MarketSharePieChart.svelte`.
+- `/vaults/stablecoins`, `/chains`, `/protocols`, and `/curators` use `MarketSharePieChart.svelte`.
 - Group detail pages use `VaultGroupMiniChart.svelte`.
 - Vault detail pages use lightweight-charts components for share price, utilisation, and benchmark series.
 
@@ -36,7 +36,7 @@ The common data sources are:
 - Route-local `chart-data/+server.ts` endpoints for heavier ECharts pages that need cached JSON payloads.
 - Client-side `fetch()` from `+page.svelte` for pages that opt out of SSR or need lazy chart data loading.
 - `+page.server.ts` for pages that can prepare their data during server rendering.
-- Vault detail metrics endpoints such as `/trading-view/vaults/[vault]/metrics` for time-series data.
+- Vault detail metrics endpoints such as `/vaults/[vault]/metrics` for time-series data.
 
 Current cached chart-data endpoints include:
 
@@ -98,7 +98,7 @@ Its `charts` array controls the `See charts:` link row displayed within chart pa
 
 When adding or removing a chart page, update both arrays unless there is a deliberate reason for the page to appear in only one navigation surface. Also update integration tests that assert menu or selector counts:
 
-- `tests/integration/trading-view/vaults/charts-dropdown.test.ts`
+- `tests/integration/vaults/charts-dropdown.test.ts`
 - chart-page tests that assert `.scatter-plot-selector a` counts
 
 The dropdown and in-page selector can intentionally have different counts. For example, a page can be present in the in-page selector before it is added to the top dropdown, but this should be explicit in the change.
@@ -113,6 +113,6 @@ first so private env vars and the historical vault parquet cache are available t
 Useful checks:
 
 - Run unit tests for chart payload builders, e.g. `pnpm exec vitest run src/lib/echarts/core3-risk.test.ts`.
-- Run focused Playwright specs after navigation changes, e.g. `pnpm exec playwright test --config tests/integration tests/integration/trading-view/vaults/charts-dropdown.test.ts`.
+- Run focused Playwright specs after navigation changes, e.g. `pnpm exec playwright test --config tests/integration tests/integration/vaults/charts-dropdown.test.ts`.
 - Run `pnpm run build:test` before focused integration specs if `.svelte-kit-test/output/server` is missing.
 - Use Playwright browser checks to verify canvas count, tooltip content, and navigation when adding a new ECharts page.

docs/echarts.md

@@ -23,7 +23,7 @@ The front page adapter lives in:
 
 The standalone page adapter lives in:
 
-- `src/routes/trading-view/vaults/cumulative-tvl-apy/CumulativeTvlApyChart.svelte`
+- `src/routes/vaults/cumulative-tvl-apy/CumulativeTvlApyChart.svelte`
 
 The diagnostics implementation lives here:
 
@@ -185,7 +185,7 @@ The standalone page uses a larger preset so axis labels, tooltip text, and plot
 The ECharts migration is covered by integration tests in:
 
 - `tests/integration/index.test.ts`
-- `tests/integration/trading-view/vaults/cumulative-tvl-apy.test.ts`
+- `tests/integration/vaults/cumulative-tvl-apy.test.ts`
 
 The home page test checks that the page:
 
@@ -257,8 +257,8 @@ If you change the front page widget, check these areas together:
 
 If you change the standalone page, check these areas together:
 
-- `src/routes/trading-view/vaults/cumulative-tvl-apy/CumulativeTvlApyChart.svelte` control logic and URL state
+- `src/routes/vaults/cumulative-tvl-apy/CumulativeTvlApyChart.svelte` control logic and URL state
 - `src/lib/scatter-plot/ScatterPlotShell.svelte` chart hosting behaviour
-- `tests/integration/trading-view/vaults/cumulative-tvl-apy.test.ts`
+- `tests/integration/vaults/cumulative-tvl-apy.test.ts`
 
 If the change is primarily visual or experimental, prefer trying it on the diagnostics page first and then porting the result into the front page widget once the behaviour is stable.

docs/new-vault-chain.md

@@ -57,11 +57,11 @@ Vaults with `risk_numeric: null` (common for new chains without risk scoring) mu
 If the new chain's vaults need a different default TVL threshold, add an entry to:
 
 - `CHAIN_TVL_THRESHOLD_OVERRIDES` map in `src/lib/top-vaults/helpers.ts` (affects `meetsDefaultTvl` used on the front page)
-- `chainOverrides` in the `tvlFilterOptions` array in the same file (affects the interactive filter on `/trading-view/vaults`)
+- `chainOverrides` in the `tvlFilterOptions` array in the same file (affects the interactive filter on `/vaults`)
 
 ## 6. Parquet data
 
-Vault share price chart data is served from a locally cached `data/cleaned-vault-prices-1h.parquet` file. The server refreshes this cache from the configured Cloudflare source when the file has not been checked for over one hour. The metrics endpoint (`src/routes/trading-view/vaults/[vault=vaultId]/metrics/+server.ts`) queries this file by vault ID.
+Vault share price chart data is served from a locally cached `data/cleaned-vault-prices-1h.parquet` file. The server refreshes this cache from the configured Cloudflare source when the file has not been checked for over one hour. The metrics endpoint (`src/routes/vaults/[vault=vaultId]/metrics/+server.ts`) queries this file by vault ID.
 
 Ensure the parquet file is updated to include rows for the new chain's vaults. Without this, the chart will render empty (no error shown to the user).
 
@@ -70,7 +70,7 @@ Ensure the parquet file is updated to include rows for the new chain's vaults. W
 After adding a new chain, verify:
 
 - [ ] Chain logo appears on the blockchains page (`/trading-view/blockchains`)
-- [ ] Vaults appear in the listing (`/trading-view/vaults`) — try the search box and lower TVL filters
-- [ ] Vault detail page loads (`/trading-view/vaults/{slug}`)
+- [ ] Vaults appear in the listing (`/vaults`) — try the search box and lower TVL filters
+- [ ] Vault detail page loads (`/vaults/{slug}`)
 - [ ] Share price chart shows data on the vault detail page
-- [ ] Chain appears in the "by chain" vault grouping (`/trading-view/vaults/chains`)
+- [ ] Chain appears in the "by chain" vault grouping (`/vaults/chains`)

docs/tests.md

@@ -120,7 +120,7 @@ tailscale ip -4
 Example:
 
 ```text
-http://brian.tail71b97.ts.net:5173/trading-view/vaults/stablecoins/frax
+http://brian.tail71b97.ts.net:5173/vaults/stablecoins/frax
 ```
 
 The Vite config allows `.ts.net` hosts so agent-hosted remote dev previews work without disabling host validation globally.

docs/vault-data-optimisation-plan.md

@@ -12,7 +12,7 @@ The landing page vault data was optimised in PR #1171 by pre-computing aggregate
 
 ## Candidates for optimisation
 
-### 1. `/trading-view/vaults/+layout.ts` (highest impact)
+### 1. `/vaults/+layout.ts` (highest impact)
 
 Central hub for all vault listing pages (~15 child routes). Currently fetches full `VaultInfo[]` (80+ fields per vault) and passes it to every child.
 

docs/vault-data-source.md

@@ -63,11 +63,11 @@ R2 downloads stream the object body via the AWS SDK (`getR2Object`) and pipe it
 
 ### Treasury benchmark (FRED DTB3)
 
-**Code:** `src/routes/trading-view/vaults/treasury-benchmark/+server.ts` (server proxy) and `src/lib/top-vaults/treasury-benchmark.ts` (client fetcher)
+**Code:** `src/routes/vaults/treasury-benchmark/+server.ts` (server proxy) and `src/lib/top-vaults/treasury-benchmark.ts` (client fetcher)
 
 The US 3-month Treasury bill rate is used as a risk-free benchmark on non-perpetual-futures vault charts. FRED blocks browser CORS and rate-limits aggressively, so the data is proxied through a server endpoint.
 
-**Server endpoint** (`/trading-view/vaults/treasury-benchmark?cosd=YYYY-MM-DD&coed=YYYY-MM-DD`):
+**Server endpoint** (`/vaults/treasury-benchmark?cosd=YYYY-MM-DD&coed=YYYY-MM-DD`):
 
 1. Validates and clamps date range (rejects future `cosd`, clamps to DTB3 series bounds)
 2. Checks file cache at `~/.cache/ts-frontend/fred-DTB3-{cosd}-{coed}.json` (24h TTL)
@@ -96,11 +96,11 @@ The US 3-month Treasury bill rate is used as a risk-free benchmark on non-perpet
 
 ### Datasets download endpoint
 
-**Code:** `src/routes/trading-view/vaults/datasets/download/[datasetId]/+server.ts`
+**Code:** `src/routes/vaults/datasets/download/[datasetId]/+server.ts`
 
 This public-facing endpoint proxies downloads through a separate Vault API service (`TS_PUBLIC_VAULT_API_URL`), not through R2 or the local cache. It is used by the datasets listing page for user-facing downloads.
 
-The datasets listing page (`src/routes/trading-view/vaults/datasets/+page.server.ts`) requires R2 to be configured for displaying file metadata (size, last modified), even though the actual download goes through the Vault API.
+The datasets listing page (`src/routes/vaults/datasets/+page.server.ts`) requires R2 to be configured for displaying file metadata (size, last modified), even though the actual download goes through the Vault API.
 
 ## Data flow diagram
 

scripts/benchmark-historical-tvl-chain.mjs

@@ -1,8 +1,8 @@
 #!/usr/bin/env node
 
 // Benchmark the same aggregation used by
-// `/trading-view/vaults/historical-tvl-chain/chart-data`
-// for the page at `/trading-view/vaults/historical-tvl-chain`.
+// `/vaults/historical-tvl-chain/chart-data`
+// for the page at `/vaults/historical-tvl-chain`.
 //
 // Local benchmark baseline from 2026-03-21 on this checkout after
 // weekly daily-close averaging and dropping the current partial week: