Skip to content

chore(missing_docs): bookkeeping for v0.2026.09.09.08.26.stable_02 - #736

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

chore(missing_docs): bookkeeping for v0.2026.09.09.08.26.stable_02#736
warp-factories[bot] wants to merge 2 commits into
mainfrom
missing-docs/bookkeeping-v0.2026.09.09.08.26.stable_02

Conversation

@warp-factories

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

Copy link
Copy Markdown
Contributor

Summary

missing_docs drift-watch bookkeeping for stable v0.2026.09.09.08.26.stable_02.

Companion feature PRs:

  • window backdrop + native completions GA
  • shell widget handoff
  • Grok Build CLI agents list

Changes

  • changelog_decisions.md — verdicts for surface changes, changelog, oz_updates, API Gate 0 deferrals
  • feature_surface_map.md — ShellWidgetHandoff mapping; internal API routes; NativeShellCompletions/HistorySearchRankingV2 ignore comments
  • last_release_processed.json — marker advanced to this release
  • surface_snapshot.json — regenerated baseline

Second sweep (2026-09-11 17:00Z)

A second drift-watch pass over the same release added one verdict this branch was missing, and re-verified the rest rather than re-deciding it.

  • New deferred verdict — warp #15913, oz secret create docker-registry. The subcommand adds four flags (--host, --username, --password, --password-file) that would carry Gate 1, and --password/--password-file conflict handling that would carry Gate 2. Gate 0 stops both: the commit landed on warp master at 7bfa9da6b on 2026-09-11 16:47 UTC, two days after this release was cut, so it is in no stable release. The first sweep could not see it — its checkout predated the commit by 40 minutes.
  • surface_snapshot.json deliberately left unregenerated. Regenerating now would absorb those four unreleased flags into the baseline and they would never re-surface. Leaving it means --diff re-fires them on the first run after #15913 ships. Verified: a re-run on this branch reports exactly those four cli_flag_added changes and nothing else new.
  • Gate 0 evidence independently re-verified. All eight undocumented_api_endpoints really do carry x-internal: true in warp-server/public_api/openapi.yaml, and developers/agent-api-openapi.yaml still has zero /factory or /factory-inbox paths.
  • Zero-finding categories re-confirmed: undocumented_features, undocumented_cli_commands, undocumented_slash_commands, map_hygiene, stale_doc_references, and unlisted_pages. Both audit modes exited 0 with no audits_skipped and an empty unaccounted bucket.
  • Build validated. npm run build passes on main with the three companion feature PRs cherry-picked together (385 Markdown docs, 387 HTML files).
  • Audit blind spot recorded in the ledger Notes: the CLI extractor does not descend into Args structs, so the claude, codex, and docker-registry provider subcommands under oz secret create never reach surface_snapshot.json. They were caught only through their flags, so a provider subcommand added with no new flags would be invisible to both the coverage audit and --diff. Fixing it is a skill-script change, out of scope for a content run.

Deferred findings

  • oz secret create docker-registry and its four flags (warp #15913) — Gate 0, not in a stable release. Re-check when a stable release contains it; target pages are platform/secrets.mdx and the oz secret create entry in reference/cli/index.mdx. suggest_reviewers.py resolves crates/warp_cli/src/secret.rs to two owners (@bnavetta, @ianhodge) rather than one, so no reviewer was requested for it; they are the candidates when it comes back.
  • All eight API endpoints marked x-internal: true (conversation steering/history/interrupt/trace + factory inbox/linear filter/self-improvement costs) mapped -> internal
  • HistorySearchRankingV2 GA: no docs (ranking-only)
  • Changelog items #15771, #15769, #15762, #15744, #15513 and all team-selection oz_updates: no docs
  • 24 potentially_stale_docs: style_lint / known false positives, including the unresolved ai credits bucket-name policy question already open in the ledger Notes

Unverified claims

None — bookkeeping only.

Documentation risk

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

Record release triage verdicts, map GA flags and internal API routes,
advance the release marker, and regenerate the surface snapshot.
@vercel

vercel Bot commented Sep 11, 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 11, 2026 5:13pm UTC

Request Review

@cla-bot cla-bot Bot added the cla-signed label Sep 11, 2026
@warp-factories warp-factories Bot added the warpy-factory Opened by the Warp factory agents label Sep 11, 2026
@warp-factories
warp-factories Bot requested a review from dannyneira September 11, 2026 16:13
A second drift-watch sweep of v0.2026.09.09.08.26.stable_02 found one
finding with no recorded verdict: the four new `oz secret create
docker-registry` flags from warp #15913, which landed after the earlier
sweep's checkout.

Defer it on Gate 0 (merged to master two days after the stable cut) and
leave surface_snapshot.json unregenerated so `--diff` re-fires the flags
once they ship. Also record the second sweep's accounting and the CLI
extractor blind spot that hides provider subcommands under
`oz secret create`.

Co-Authored-By: Warp <agent@warp.dev>
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