Skip to content

chore(missing_docs): bookkeeping for v0.2026.09.16.08.27.stable_02 - #768

Draft
warp-factories[bot] wants to merge 5 commits into
mainfrom
missing-docs/bookkeeping-v0.2026.09.16.08.27.stable_02
Draft

warp-factories[bot] wants to merge 5 commits into
mainfrom
missing-docs/bookkeeping-v0.2026.09.16.08.27.stable_02

Conversation

@warp-factories

@warp-factories warp-factories Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Residual re-verification

Fourth drift-watch pass while this PR is still open (2026-09-21). 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. Extended this PR (no second bookkeeping PR).

Merged origin/main (298e5a14) into the branch first — docs#752 and docs#763, both unrelated to tracked surfaces — so the snapshot and audit describe the post-merge tree rather than a stale one.

  • Every audit category is zero except the known staleness rows. undocumented_features, undocumented_cli_commands, undocumented_api_endpoints, undocumented_slash_commands, undocumented_settings, surface_changes, changelog_review, map_hygiene, stale_doc_references, and unlisted_pages all returned 0. Both modes exited 0, audits_skipped: null, unaccounted: {} across 297 flags, 91 CLI commands, 223 API routes, 65 slash commands, and 232 settings.
  • No surface moved. --update-snapshot against warp (3c520bed7) and warp-server (a1f654c93), both a day newer than the 2026-09-20 pass, reproduced this branch's surface_snapshot.json byte for byte.
  • Gate 0 re-verified at source, not carried forward: getRunHarnessUsage x-internal: true (openapi.yaml:7226-7235); publishHarnessUsage x-internal: true (openapi.yaml:10194-10205); createScoringBackfill (openapi.yaml:10922) is not x-internal but sits under /factory, excluded wholesale by sync_openapi.py:107, and the released spec still has zero /factory paths. All three stay mapped -> internal.
  • Swept the three documented blind spots the audit cannot see itself. Surface-scoped slash check over all 65 registry entries leaves only /docker-sandbox, still dogfood-gated by LocalDockerSandbox. CreateProvider still has exactly three variants, so the Args-struct extractor gap hides nothing new. --weak-coverage returns 82, unchanged.
  • All three skill test suites pass (19 + 18 + release-gate). npm ci && npm run build passes (388 Markdown docs, 390 HTML files).
  • Feature PR docs: private image credentials (docker-registry secrets) #767 still open; no new feature PR from this pass.

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).

Changes

  • feature_surface_map.md — map GET /agent/runs/{runId}/harness-usage, POST /harness-support/usage, and POST /factory/scorers/{scorer_id}/backfillinternal
  • changelog_decisions.md — verdicts for all 13 changelog/oz_updates bullets, 3 API routes, WindowsVideoRecording dogfood flag, and the 24 staleness rows, plus the 2026-09-19/20/21 re-verification rows
  • last_release_processed.json — advanced to this stable
  • surface_snapshot.json — regenerated

Deferred / no-docs findings

Item 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 / internal / small)
#15921, #15863, #16046 oz_updates no (bug fixes)
harness-usage, harness-support/usage deferred Gate 0 (x-internal)
factory scorers backfill deferred Gate 0 (unreleased /factory namespace)
WindowsVideoRecording deferred Gate 0 (dogfood)
/docker-sandbox deferred Gate 0 (dogfood LocalDockerSandbox)
24 potentially_stale_docs no (style_lint-owned; ai credits remains an open style-policy question for a human owner)

Reviewer routing

suggest_reviewers.py resolves only the @warpdotdev/oss-maintainers team for crates/warp_features/src/lib.rs; all three warp-server handler paths are unowned. Teams are never requested, so this PR keeps no requested reviewer.

Documentation risk

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

Record drift-watch triage for the new stable release: map three internal
API routes, append changelog verdicts (docker-registry yes via docs#767),
advance the release marker, and regenerate the surface snapshot.
@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs Ready Ready Preview Sep 21, 2026 5:11pm UTC

Request Review

@cla-bot cla-bot Bot added the cla-signed label Sep 18, 2026
@warp-factories warp-factories Bot added the warpy-factory Opened by the Warp factory agents label Sep 18, 2026
@warp-factories
warp-factories Bot requested a review from dannyneira September 18, 2026 16:10
@warp-factories

Copy link
Copy Markdown
Contributor Author

This PR was generated with Warp.

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

….stable_02

Record the 2026-09-20 drift-watch residual pass while bookkeeping PR #768
is still open. Snapshot remains byte-identical; no new findings.
hongyi-chen and others added 2 commits September 21, 2026 17:05
Fourth drift-watch pass over v0.2026.09.16.08.27.stable_02. Merged main
into the branch so the snapshot describes the post-merge tree. Snapshot
regen against a-day-newer warp/warp-server checkouts is byte-identical,
and every audit category except the 24 already-decided staleness rows is
zero. Re-verified Gate 0 at source for the three internal routes and
swept the three documented audit blind spots.

Co-Authored-By: Warp <agent@warp.dev>

This branch was successfully deployed

1 active deployment
Preview 2065b23b Deployed Sep 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed warpy-factory Opened by the Warp factory agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant