chore(missing_docs): bookkeeping for the 2026-09-09 exhaustive audit - #717
Conversation
Record this run's docs-worthiness verdicts, update the surface map for the six surfaces that drifted, and regenerate the surface snapshot. Every candidate gated out, so no feature PRs accompany this one. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment |
|
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 |
There was a problem hiding this comment.
Overview
This PR records bookkeeping from the 2026-09-09 missing_docs audit by updating the verdict ledger, surface map, and generated snapshot for feature flag and internal API surface changes. The declared low documentation risk matches the diff because no public documentation pages, public product claims, commands, examples, or user-facing docs content are changed.
Concerns
- No blocking concerns found.
- No security findings found in the changed audit bookkeeping files.
- No implementation/spec drift was assessed because
spec_context.mdreports that no approved or repository spec context exists for this PR.
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
There was a problem hiding this comment.
Overview
This PR updates the missing_docs audit ledger, surface map, and generated snapshot for the 2026-09-09 coverage sweep. The submitted mappings and recorded deferrals are internally consistent, and no public documentation surface changed.
Verdict
Checks: build ✅ · audit-script tests ✅ · map audit ✅ · diff-accounting audit ✅ · CI ⏳ (the Agent docs review check is still in progress; all other reported checks pass)
Found: 0 critical, 0 important, 0 suggestions
Approve
Review run
https://platform.staging.warp.dev/bOEZRU0oiK4KrUD6bKONxk/runs/01a0873a-64c6-7d44-b0ea-43aff0907208


Bookkeeping for the exhaustive
missing_docsdrift-watch run on 2026-09-09. Every candidate was gated out, so this is the only PR from the run — no feature PRs accompany it.Titled by audit date rather than release version because the release gate was a no-op:
check_new_release.pyexited 10, current stable is stillv0.2026.09.02.08.27.stable_01, and the previous bookkeeping PR (#695) already carries that version.last_release_processed.jsonis deliberately unchanged.What ran
Both audit modes exited 0, with no
audits_skippedand an emptyunaccountedaccounting bucket across all 296 feature flags, 91 CLI commands, 209 API routes, 65 slash commands, and 231 settings.audit_docs.py --warp ../warp --warp-server ../warp-server--diff--weak-coverage, for exhaustivenessname:entries instatic_commands/commands.rs, working around the audit's documented repo-wide slash blind spotnpm ci && npm run build, clean (382 Markdown docs, 384 HTML files)Re-running the audit after these changes clears every category except the 24 terminology-only staleness hits, which are recorded as
no.Verdicts recorded
Full reasoning and evidence are in
changelog_decisions.md; this is the summary.RestorePromptOnInlineModelSelectorSearch(dogfood → GA) - No docs. Opening the inline model selector from the model chip parks input text so the input can filter the model list, then restores it on close (app/src/terminal/input.rs:5666). No setting, CLI flag, or API field; the model chip and/modelalready surface the selector. Disqualified as a pure UI affordance. Mapped ignore.PeriodicHandoffCheckpoints(dogfood → preview) - Deferred on Gate 0. Periodic workspace-snapshot uploads during a cloud agent run (PREVIEW_FLAGS,crates/warp_features/src/lib.rs:970). Preview, not GA. Re-check on promotion, at which point it belongs onplatform/handoff/.POST /factory-inbox/notifications/dismissand/restore- Deferred on Gate 0. Bulk dismiss and restore for the personal factory inbox (factory_inbox.go:26-27). Mapped-> internal.POST /factory/{uid}/integrations/jira/handoff- Deferred on Gate 0, the Jira counterpart of the Linear handoff route deferred on 2026-09-02. Mapped-> internal. Not a content gap either: the user-facing flow is already covered atfactories/integrations/jira.mdx.POST /factory-inbox/notifications/{uid}/dismiss(removed) - Map hygiene. Replaced by the bulk route above; never in the released spec or any page. Dead entry replaced in place.potentially_stale_docs- No docs. Re-verified line by line rather than carried forward from the previous run. All are terminology matches: the knownai creditsbucket-name false positive,warp terminalused in the distinguishing sense the style guide permits, a historical FAQ heading, and two live feature names (Generate, AI Command Search). The one genuine wording nit isstyle_lintterritory per SKILL.md.--weak-coveragefindings - No docs. Same mapped-page keyword misses verified since 2026-08-26.Five categories returned zero and are recorded as such so a later run can distinguish "checked and empty" from "not checked": CLI commands, slash commands, settings, stale doc references, and unlisted pages.
Deferred findings
Nothing was silently dropped. Four surfaces carry
deferredverdicts, all on Gate 0, all with a recorded re-check condition:PeriodicHandoffCheckpoints- re-check when the flag reachesRELEASE_FLAGSor the default feature set./factory*routes - re-check when the Factory REST API is published.developers/agent-api-openapi.yamlstill has zero/factoryand/factory-inboxpaths, and warp-server is private, so none may be hand-documented. Released factory routes would reach docs throughsync-openapi-spec, not this skill.No content design plan
None of the three cases in
.agents/references/content-design-plan.mdapplies: no page is created, no concept is added, and nothing is corrected on a page. This is bookkeeping, which that reference lists under "when a plan can be skipped."Reviewer
No reviewer requested.
suggest_reviewers.pyresolved the two warp source files to the team@warpdotdev/oss-maintainers, and teams are never requested. Both warp-server paths —router/handlers/public_api/factory_inbox.goandfactories.go— resolved to no owner, the expected outcome the skill documents for/factoryhandlers, which carry no entry in that repo's ownership file.Documentation risk
Risk: low
Rationale: Audit bookkeeping only: surface-map entries, the verdict ledger, and the regenerated surface snapshot. No page under src/content/docs/ changes, and no public product claim is added or altered.
Docs override: none
Unverified claims
None. No
VERIFYmarkers in the changed files.