chore(missing_docs): bookkeeping for v0.2026.09.09.08.26.stable_02 - #736
Draft
warp-factories[bot] wants to merge 2 commits into
Draft
chore(missing_docs): bookkeeping for v0.2026.09.09.08.26.stable_02#736warp-factories[bot] wants to merge 2 commits into
warp-factories[bot] wants to merge 2 commits into
Conversation
Record release triage verdicts, map GA flags and internal API routes, advance the release marker, and regenerate the surface snapshot.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
missing_docs drift-watch bookkeeping for stable
v0.2026.09.09.08.26.stable_02.Companion feature PRs:
Changes
changelog_decisions.md— verdicts for surface changes, changelog, oz_updates, API Gate 0 deferralsfeature_surface_map.md— ShellWidgetHandoff mapping; internal API routes; NativeShellCompletions/HistorySearchRankingV2 ignore commentslast_release_processed.json— marker advanced to this releasesurface_snapshot.json— regenerated baselineSecond 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.
oz secret create docker-registry. The subcommand adds four flags (--host,--username,--password,--password-file) that would carry Gate 1, and--password/--password-fileconflict handling that would carry Gate 2. Gate 0 stops both: the commit landed on warpmasterat7bfa9da6bon 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.jsondeliberately left unregenerated. Regenerating now would absorb those four unreleased flags into the baseline and they would never re-surface. Leaving it means--diffre-fires them on the first run after #15913 ships. Verified: a re-run on this branch reports exactly those fourcli_flag_addedchanges and nothing else new.undocumented_api_endpointsreally do carryx-internal: trueinwarp-server/public_api/openapi.yaml, anddevelopers/agent-api-openapi.yamlstill has zero/factoryor/factory-inboxpaths.undocumented_features,undocumented_cli_commands,undocumented_slash_commands,map_hygiene,stale_doc_references, andunlisted_pages. Both audit modes exited 0 with noaudits_skippedand an emptyunaccountedbucket.npm run buildpasses onmainwith the three companion feature PRs cherry-picked together (385 Markdown docs, 387 HTML files).Argsstructs, so theclaude,codex, anddocker-registryprovider subcommands underoz secret createnever reachsurface_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-registryand its four flags (warp #15913) — Gate 0, not in a stable release. Re-check when a stable release contains it; target pages areplatform/secrets.mdxand theoz secret createentry inreference/cli/index.mdx.suggest_reviewers.pyresolvescrates/warp_cli/src/secret.rsto two owners (@bnavetta, @ianhodge) rather than one, so no reviewer was requested for it; they are the candidates when it comes back.x-internal: true(conversation steering/history/interrupt/trace + factory inbox/linear filter/self-improvement costs) mapped-> internalai creditsbucket-name policy question already open in the ledger NotesUnverified 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