missing_docs bookkeeping for v0.2026.08.19.08.15.stable_01 - #624
Conversation
Record drift-watch triage verdicts, update the feature surface map for new factory routes and flag cleanup, advance the release marker, and regenerate the surface snapshot. Co-Authored-By: Warp <agent@warp.dev>
|
This PR was generated with Warp. Comment   |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Your GitHub account is not connected to Warp. Connect it here. |
… titles The convention I introduced, "missing_docs bookkeeping: <version>", quietly contradicted create_pr's existing rule that docs PR titles carry a prefix. It also invented a third naming shape in a change whose whole point is that two competing shapes are what let #614 and #624 miss each other. "chore(missing_docs): bookkeeping for <version>" matches the shape #614 already used, matches the repo's conventional-commit practice, and still carries both terms the documented search keys on -- verified against #614, whose title has exactly this form and which the search finds. Co-Authored-By: Warp <agent@warp.dev>
#614 landed the same two /factory map entries this branch adds, so the surface map conflicted. Resolved in favour of main: #614 placed each route beside its logical neighbours with a comment explaining why it is internal, which is what the skill asks for. This branch had both as bare uncommented lines in one spot. Dropping the duplicates leaves each route mapped exactly once. The snapshot auto-merged cleanly and needed no regeneration: this branch's regen is a strict superset of #614's. Both contain the two /factory route additions; this one additionally records CtrlCCancelsThirdPartyHarness going dogfood -> ga and OpenWarpNewSettingsModes being removed. Verified the merged snapshot is byte-identical to this branch's original. Both of those flag changes were already triaged here -- CtrlCCancelsThirdPartyHarness has a map ignore entry explaining it has no setting, menu, or CLI surface, and OpenWarpNewSettingsModes was pruned from the map. Neither is silently swallowed by the advancing snapshot. The ledger anby the advancing snapshot. The ledger anby the advancing snapshot. The ledger-Authored-By: Warp <agent@warp.dev>
|
Rebased onto What conflicted and how it was resolved. #614 added the same two The snapshot needed no regeneration. This branch's regen turned out to be a strict superset of #614's — both carry the two Both flag changes were already triaged, so the advancing snapshot isn't swallowing them silently:
The collision itself is addressed in #630, which limits the pipeline to one open bookkeeping PR at a time and gives them a findable title so a future run can discover an existing one instead of opening a second. |
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![warp-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR records missing-docs drift-watch bookkeeping for stable release v0.2026.08.19.08.15.stable_01: changelog decisions, surface-map cleanup/internal ignores, the processed-release marker, and the regenerated surface snapshot. I found no blocking documentation, bookkeeping, spec-drift, or security concerns in the annotated diff.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR records the missing-docs drift-watch decisions and regenerated references for v0.2026.08.19.08.15.stable_01. The release marker, triage ledger, surface-map pruning, and generated snapshot match the reviewed source state.
Verdict
Checks: CI ✅ · typecheck ✅ · build ✅ · missing-docs tests ✅ · snapshot regeneration ✅ · visual proof n/a (internal bookkeeping data only)
Found: 0 critical, 0 important, 0 suggestions
Approve
Review run
https://oz.staging.warp.dev/runs/01a03a84-bb45-7a0e-93c8-138f2c253eec
* missing_docs: keep at most one bookkeeping PR open The PR strategy said a bookkeeping PR "is independently mergeable in any order." That is true against feature PRs, which is the case it was written for. It is false against a second bookkeeping PR: both edit feature_surface_map.md and surface_snapshot.json, and the snapshot is a wholesale regen, so a conflict between two of them cannot be resolved by hand at all -- it has to be regenerated on the merged tree. #614 and #624 are that collision, sitting open right now. Two drift-watch runs a day apart independently triaged the same two /factory routes, reached the same Gate 0 verdict, and each added the same two map lines. Neither looked for the other's PR, and they used different branch-naming schemes, so there was no way to find one from the other. Run #2's ledger eway to find one from the other. Run #2's ledger eway to find one from the other. Run #2's ledger eway to find one from the other. Run #2's ledger eway to find one from the other. Run #2's ledgeran stays rare. Changes: - Scope the independence claim to feature PRs, and add the rule: check for an open bookkeeping PR first, extend that branch, and re-run --commit and --update-snapshot there so the marker and snapshot stay one regen covering every release the PR carries. Wait for the merge instead when it is already approved. - Standardize the title (missing_docs bookkeeping: <version>) and branch (missing-docs/boo (missing-docs/boo (mise search (missing-docs/boo (missing-docs/boo (mise search (missing-docs/boo (miste their inconsistent titles. - Triage now reads the ledger and map as they stand on any open bookkeeping PR, not just on main. A verdict in an unmerged PR is still a verdict. - Carry both into drift-watch step 8 and the scheduled-agent prompt, which is the only copy a cron run is guaranteed to read. Co-Authored-By: Warp <agent@warp.dev> * missing_docs: use the repo's existing prefix style for bookkeeping PR titles The convention I introduced, "missing_docs bookkeeping: <version>", quietly contradicted create_pr's existing rule that docs PR titles carry a prefix. It also invented a third naming shape in a change whose whole point is that two competing shapes are what let #614 and #624 miss each other. "chore(missing_docs): bookkeeping for <version>" matches the shape #614 already used, matches the repo's conventional-commit practice, and still carries both terms the documented search keys on -- verified against #614, whose title has exactly this form and which the search finds. Co-Authored-By: Warp <agent@warp.dev> * missing_docs: restrict bookkeeping-PR search to avoid self-match The gh pr list --search "missing_docs bookkeeping in:title" query ANDs the two words anywhere in the title, so it also matches this rule-only PR's own title ("...keep at most one bookkeeping PR open"). The next drift-watch run would then check out and extend this PR's branch instead of a real bookkeeping PR. Restrict the search to the quoted "bookkeeping for" phrase, which matches the canonical and legacy bookkeeping-PR titles but not this PR's title, and add reviewDecision to the output so the already- approved exception can be applied without a second query. Apply the same corrected query to the recommended scheduled-agent prompt. Co-Authored-By: Warp <agent@warp.dev> --------- Co-authored-by: Warp <agent@warp.dev> Co-authored-by: warp-agent-staging[bot] <240773466+warp-agent-staging[bot]@users.noreply.github.com>
1 participant
Summary
Companion audit-bookkeeping PR for the missing_docs drift-watch run on stable release
v0.2026.08.19.08.15.stable_01. No user-facing doc prose here — that lives in the/usagefeature PR.Changes
changelog_decisions.md— verdicts for all triage candidatesfeature_surface_map.md— map new factory routes-> internal, ignoreCtrlCCancelsThirdPartyHarness, pruneOpenWarpNewSettingsModeslast_release_processed.json— markv0.2026.08.19.08.15.stable_01processedsurface_snapshot.json— regenerated baselineRelated feature PR
Documents
/usageon the CLI models and reference pages (opened as a sibling draft).Triage table (this run)
#14968/usageCLI command/usageinstatic_commands/commands.rs; CLI docs lacked itsrc/content/docs/factories/exists; major launches are human-ledCtrlCCancelsThirdPartyHarnessdogfood→gaview.rs; Ctrl-C already documentedOpenWarpNewSettingsModesremovedPOST /factory/{uid}/runsPOST /factory/automations/{id}/run