docs: fix stale Docs Agent environment reference in weekly-404-monitor

[rachaelrenk]

Problem

The #growth-docs Slack channel received a failure alert this week:

⚠️ docs.warp.dev 404 Report — week of 2026-08-03
Failed: METABASE_API_KEY is not set in this Oz environment.
Fix: add METABASE_API_KEY to the Docs Agent Oz environment secrets, then re-run.
Environment expected: K5KStCm5aYvhfBJb8cHol6 (Docs Agent).

Investigation

• The weekly-404-monitor SKILL.md's ## Scheduling section instructed operators to verify secrets on the Docs Agent Oz environment (K5KStCm5aYvhfBJb8cHol6) and to register the schedule against that environment.
• The actual live schedule (Weekly docs 404 monitor, schedule ID xAqd8EBlaJ3EihLlfF3fOs) is registered against a different environment: qDewDp082oqhaq7ZJd6LJI ("buzz").
• K5KStCm5aYvhfBJb8cHol6 is not visible/resolvable via oz-dev environment get/list from the Oz account operating this schedule, so anyone following the doc to "verify secrets" on that environment for this schedule would be looking in the wrong (inaccessible) place.
• The buzz environment (qDewDp082oqhaq7ZJd6LJI) already has METABASE_API_KEY and BUZZ_SLACK_TOKEN provisioned as Team-scoped secrets — confirmed by a successful run today that posted a full report with real data (323 total 404s this week, down from 458) to #growth-docs.
• Separately, the buzz environment did not have warpdotdev/docs in its configured repos, even though the skill's prompt assumes /home/user/warpdotdev/docs is already checked out. Fixed via oz-dev environment update qDewDp082oqhaq7ZJd6LJI --repo warpdotdev/docs.

Note: other docs automations (validate_ui_refs, release_updates / release-docs-update.yml, refresh-ui-paths.yml) still reference K5KStCm5aYvhfBJb8cHol6 and appear to dispatch successfully via a separate GitHub Actions WARP_API_KEY/service-account scope, so that environment likely exists under a different account scope than the one running this schedule. This PR only corrects the weekly-404-monitor skill's docs to match its actual, working configuration — it does not touch the other workflows.

Changes

• Updated .agents/skills/weekly-404-monitor/SKILL.md ## Scheduling section to reference the correct, live environment (qDewDp082oqhaq7ZJd6LJI / "buzz") instead of the inaccessible K5KStCm5aYvhfBJb8cHol6.
• Added an incident note documenting the 2026-08-03 failure and resolution.

Already applied (not part of this diff)

• Added warpdotdev/docs to the buzz Oz environment's repo list via oz-dev environment update.
• This week's 404 report already ran successfully and posted to #growth-docs.

Conversation: https://staging.warp.dev/conversation/1703d43c-d6c3-46bc-adf9-d0531cc582ac
Run: https://oz.staging.warp.dev/runs/019fc891-7eb9-7b39-a1ed-ed7a50b7f6d3

This PR was generated with Oz.

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 3, 2026 6:36pm

[rachaelrenk]

Closing — these changes have been moved to #454 (cherry-picked commit d837a53) per request.