From 7b0f12638557bc156f9d0209df20b057e4995291 Mon Sep 17 00:00:00 2001 From: "warp-factories[bot]" <243557089+warp-factories[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 15:40:55 +0000 Subject: [PATCH 1/2] chore: update 404 monitor run log 2026-09-09 --- .agents/logs/weekly_404_monitor_runs.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.agents/logs/weekly_404_monitor_runs.md b/.agents/logs/weekly_404_monitor_runs.md index 3d5a70c8..a8ad13f1 100644 --- a/.agents/logs/weekly_404_monitor_runs.md +++ b/.agents/logs/weekly_404_monitor_runs.md @@ -8,6 +8,17 @@ This log tracks every run of the `weekly-404-monitor` skill — both runs that o --- +## 2026-09-09 — No data +- **Total 404s this week**: n/a +- **Total 404s last week**: n/a +- **Trend**: n/a +- **Significant gaps (≥5 hits)**: n/a +- **Redirect candidates processed**: 0 (hits ≥ 5) +- **HIGH-confidence redirects**: 0 +- **PR**: none +- **Oz run**: https://app.warp.dev/conversation/2f9e8558-518f-4943-b7b7-5854ac1309dd +- **Notes**: Metabase query failed with HTTP 401 Unauthenticated. `METABASE_API_KEY` is present in environment K5KStCm5aYvhfBJb8cHol6 but is a short placeholder/invalid value (len=16, not an `mb_` key), not a real Metabase API key for https://warp.metabaseapp.com. Posted failure notice to #growth-docs. Action needed: replace the secret with a valid Metabase API key and re-run. Same failure mode as 2026-08-10, 2026-08-17, 2026-08-24, 2026-08-31, and 2026-09-07. + ## 2026-09-07 — No data - **Total 404s this week**: n/a - **Total 404s last week**: n/a From bdb2c5b6b4cfa6793c65bdd47a5e13055f51eb28 Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Wed, 9 Sep 2026 16:20:43 +0000 Subject: [PATCH 2/2] chore: update 404 monitor run log 2026-09-09 Co-Authored-By: Warp --- .agents/logs/weekly_404_monitor_runs.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.agents/logs/weekly_404_monitor_runs.md b/.agents/logs/weekly_404_monitor_runs.md index a8ad13f1..7aad05a2 100644 --- a/.agents/logs/weekly_404_monitor_runs.md +++ b/.agents/logs/weekly_404_monitor_runs.md @@ -8,6 +8,17 @@ This log tracks every run of the `weekly-404-monitor` skill — both runs that o --- +## 2026-09-09 — PR opened +- **Total 404s this week**: 270 +- **Total 404s last week**: 299 +- **Trend**: ▼ 29 (-9.7%) +- **Significant gaps (≥5 hits)**: 5 (3 new) +- **Redirect candidates processed**: 3 (hits ≥ 5, excluding 2 malformed captures) +- **HIGH-confidence redirects**: 2 +- **PR**: https://github.com/warpdotdev/docs/pull/715 +- **Oz run**: https://app.warp.dev/conversation/0d43fcb7-95f8-4b8e-9b9a-8fccf962631b +- **Notes**: `METABASE_API_KEY` now a valid `mb_...` key, but every query failed with `ValueError: Invalid header value` because the env-injected secret carries a trailing newline that urllib rejects in an HTTP header. Patched `run_404_report.py` to strip the key before use (PR #716) and re-ran successfully. 161 pages had SQL-normalised hits; 134 uncovered (129 below threshold). `/agents/agent-mode` (6 hits) → `/agents/` and `/features/session_management/launch-configuration` (5 hits) → `/terminal/sessions/launch-configurations/` added as HIGH-confidence redirects, mirroring existing analogous patterns already in `vercel.json`. `/agents/inference` (6 hits) posted to Slack as a MEDIUM-confidence suggestion (no exact index page under that directory). Two top gaps — `/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling/:*logging` (10 hits) and `/agents/local-agents/interacting-with-agents/voice/:)%3cb%3evoice` (9 hits) — excluded from the redirect PR: their underlying pages already exist, and the malformed `:`-containing suffixes look like a `docs_404` capture/encoding artifact (a literal `:` is also unsafe as a vercel.json route source, since path-to-regexp treats it as a named parameter). Recommend the docs team check the `broken_url` capture for links with raw punctuation. 135 resolved since last week. Posted summary to #growth-docs. + ## 2026-09-09 — No data - **Total 404s this week**: n/a - **Total 404s last week**: n/a