chore(missing_docs): bookkeeping for v0.2026.09.16.08.27.stable_02

[warp-factories]

Residual re-verification (2026-09-28)

Drift-watch re-entry, the first pass since 2026-09-25, run as an exhaustive sweep across every category at every severity. The release gate on main still reports v0.2026.09.16.08.27.stable_02 as new because the marker lives only on this branch; on the branch it exits 10 as expected. Extended this PR rather than opening a second bookkeeping PR, merging origin/main first (two content commits since the 2026-09-25 residual: factories/benchmarks.mdx and platform/architecture.mdx).

Nothing new to decide — no tracked surface moved. --update-snapshot against warp (master, e7656eab3) and warp-server (develop, 6627c8e10), both dated 2026-09-28 and three days newer than the last regen, reproduced this branch's surface_snapshot.json byte for byte across 295 flags, 91 CLI commands, 228 API routes, 65 slash commands, 232 settings, 23 web routes, 73 server tools, and 17 bundled skills. The snapshot is therefore unchanged in this commit.

Both audit modes exit 0 with audits_skipped: [] and an empty unaccounted bucket. Against main the run reproduces the known findings exactly (8 undocumented_api_endpoints, 12 surface_changes, 13 changelog_review, 2 map_hygiene, 24 staleness); against this branch all of them drop to zero except the 24 style_lint-owned staleness rows.

Evidence re-verified at source, not carried forward

• All eight deferred API routes still fail Gate 0. getRunHarnessUsage (public_api/openapi.yaml:7470), publishHarnessUsage (10436), listFactoryMicrosoftTeamsTeams (1374), listFactoryMicrosoftTeamsChannels (1422), and rescoreBenchmarkRun (12439) all still carry x-internal: true. createScoringBackfill (11161), markFactoryInboxNotificationsRead (2604), and markFactoryInboxNotificationsUnread (2655) are not x-internal, but sit under /factory*, excluded wholesale by EXCLUDED_PATH_PREFIXES = ("/factory",) at sync_openapi.py:107. Released developers/agent-api-openapi.yaml has 0 /factory, /factory-inbox, and /harness-support paths, 0 x-internal entries, and no harness-usage operation.
• Removed flags confirmed gone. OrchestrationUnifiedStack and WaitForEventsParentRegistration have no remaining reference anywhere in crates/ or app/, so the 2026-09-23 ignore-list pruning is correct.
• Non-GA flags still non-GA. WindowsVideoRecording (crates/warp_features/src/lib.rs:1040) and LocalDockerSandbox (1053) are in DOGFOOD_FLAGS and PREVIEW_FLAGS and are not default cargo features.

Blind spots the audit cannot see itself

• Surface-scoped slash check across all 65 registry entries (33 GuiOnly, 18 TuiOnly, 14 GuiAndTui, none carrying a feature_flag): 0 TUI-available commands missing from agents/cli/, and only /docker-sandbox uncovered — deliberately so, behind the non-GA LocalDockerSandbox.
• CLI Args-struct extractor gap: CreateProvider still has exactly three variants (claude, codex, docker-registry, crates/warp_cli/src/secret.rs:65-75), so the gap hides nothing new.
• --weak-coverage: 81, down one from 82 on 2026-09-21 because two flags left the universe. Five spot-verified, all keyword artifacts against pages that substantively document the feature.

Validation

All three skill test suites pass (19 + 18 + 17), so no extractor has rotted. npm ci && npm run build passes on the merged branch (388 Markdown docs, 390 HTML files). Re-running both audit modes after the edits confirms the addressed findings stay gone.

Summary

Drift-watch bookkeeping for stable v0.2026.09.16.08.27.stable_02.

Feature work landed separately in docs#767 (private image credentials / oz secret create docker-registry). No new feature PR from this residual pass — every finding already carried a verdict, and nothing new passed the worthiness gate.

Changes

• changelog_decisions.md — four 2026-09-28 residual rows (re-verification record, --weak-coverage, staleness, clean-category accounting) plus prior release triage
• last_release_processed.json — refreshed processed_at
• feature_surface_map.md — unchanged this pass; prior passes mapped harness-usage, harness-support usage, factory scorers backfill, factory-inbox read/unread, MS Teams pickers, and benchmark rescore, and pruned the removed orchestration flags
• surface_snapshot.json — unchanged this pass; regen reproduced it byte for byte

Deferred / no-docs findings

Nothing is silently dropped; every item below carries a recorded ledger verdict.

• #15913 docker-registry — yes → docs#767
• #15903 fzf/atuin, native completions, history ranking — no (already covered)
• #15879 Windows backdrop — no (already covered)
• #16006, #15844, #15905, #15880, #15881 — no (UI affordance / internal / small and intuitive)
• #15921, #15863, #16046 (oz_updates) — no (bug fixes restoring intended behavior)
• GET /agent/runs/{runId}/harness-usage, POST /harness-support/usage — deferred Gate 0 (x-internal operations)
• POST /factory/scorers/{scorer_id}/backfill, MS Teams team/channel pickers, POST /factory/{uid}/benchmarks/runs/{run_uid}/rescore — deferred Gate 0 (factory REST still unpublished)
• POST /factory-inbox/notifications/read and /unread — deferred Gate 0 (factory-inbox unpublished)
• WindowsVideoRecording — deferred Gate 0 (still dogfood)
• /docker-sandbox — deferred Gate 0 (non-GA LocalDockerSandbox)
• OrchestrationUnifiedStack / WaitForEventsParentRegistration removed — no (flag cleanup, no user-observable change)
• report_self_improvement_metadata — no (internal server tool)
• 24 potentially_stale_docs — no (style_lint-owned; the ai credits bucket-name rule conflict remains an open question for a human owner, recorded in the ledger Notes)

Reviewer routing

suggest_reviewers.py against this run's source files resolves @warpdotdev/oss-maintainers (root rule), @moirahuang (app/src/search/slash_command_menu/), and @bnavetta @ianhodge (crates/warp_cli/); all six warp-server public_api handler paths are unowned. Several distinct owners is not a single clear owner, so no new reviewer was requested. The existing dannyneira request is kept.

Unverified claims

None — bookkeeping only; no user-facing page content changed.

Documentation risk

Risk: low
Rationale: Bookkeeping only: ledger, release marker, surface map, and snapshot. No user-facing doc pages.
Docs override: none

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 28, 2026 5:27pm UTC

[warp-factories]

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

  View origin