Skip to content

chore: 404 monitor run log #713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
warp-factories wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

chore: 404 monitor run log #713

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b0f126
chore: update 404 monitor run log 2026-09-09
warp-factories[bot] Sep 9, 2026
bdb2c5b
chore: update 404 monitor run log 2026-09-09
hongyi-chen Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .agents/logs/weekly_404_monitor_runs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,28 @@ 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
- **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
Expand Down
Loading