Skip to content

chore(missing_docs): bookkeeping for v0.2026.09.02.08.27.stable_01 - #695

Merged
hongyi-chen merged 2 commits into
mainfrom
missing-docs/bookkeeping-v0.2026.09.02.08.27.stable_01
Sep 9, 2026
Merged

chore(missing_docs): bookkeeping for v0.2026.09.02.08.27.stable_01#695
hongyi-chen merged 2 commits into
mainfrom
missing-docs/bookkeeping-v0.2026.09.02.08.27.stable_01

Conversation

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Summary

Bookkeeping for an exhaustive missing_docs drift-watch run on 2026-09-07, covering every audit category at every severity. Records this run's docs-worthiness verdicts and advances the surface snapshot.

No feature PRs came out of this run. Every candidate either already carried a recorded verdict or failed the worthiness gates — which is a successful outcome, not an empty one. The single actionable finding was an API spec gap, routed separately to #694 per the skill's "keep API spec changes separate" rule.

What was audited

Release gate: check_new_release.py exited 10 (v0.2026.09.02.08.27.stable_01 already processed). Continued past it because the request was for a full standing audit, not the per-release increment.

Both audit modes exited 0 with no skipped audits and unaccounted: none:

feature_flags:  total=296  ga_preview=205  ignored=69  mapped=136  tracked_non_ga=91  finding=0
cli_commands:   total=91   hidden=9   mapped=30   doc_covered=38   gated_non_ga=14    finding=0
api_routes:     total=207  mapped=170 spec_covered=25 gated_non_ga=12                 finding=0
slash_commands: total=65   mapped=15  doc_covered=50                                  finding=0
settings:       total=231  private=1  tracked_non_ga=2 mapped=14 doc_covered=214      finding=0

surface_changes, map_hygiene, stale_doc_references, and unlisted_pages were all 0. Beyond the standing audit I also ran three checks that cover its known blind spots: --weak-coverage (81 findings, all the previously-verified keyword artifacts), a surface-scoped slash-command re-verification, and a full OpenAPI spec diff.

Changes

.agents/skills/missing_docs/references/changelog_decisions.md

Seven new verdict rows, all dated 2026-09-07:

  • GET /agent/conversations/{conversation_id}/transcriptyes, routed to sync-openapi-spec (docs: sync agent-api-openapi.yaml from warp-server #694). A released, non-x-internal endpoint missing from the published reference.
  • Audit blind spot: generated handler registrationno. The API extractor parses literal gin registrations, so routes registered via public_api_types.RegisterHandlersWithOptions are invisible to it. Explains why no surface-map entry was added for the route above.
  • automation/sync-agent-api-spec would leak unreleased surfaceno. Gate 0 protection; details below.
  • 10 changelog items for 2026.09.02no, already decided 2026-09-04. They re-surfaced only because of the stale snapshot marker.
  • 24 potentially_stale_docsno, terminology-only, owned by style_lint.
  • 81 --weak-coverage findingsno, heuristic false positives.
  • Surface-scoped slash re-verificationno, no new gap.

.agents/skills/missing_docs/references/surface_snapshot.json

Regenerated with --update-snapshot. The only change is changelog_last_version: 2026.08.272026.09.02. All surface counts are unchanged, confirming zero code-surface drift.

The marker had lagged because docs#682 landed the 2026.09.02 changelog entry after docs#657 regenerated the snapshot, so every already-decided item was being re-reported each run. Verified fixed: a post-regen --diff reports changelog_review: 0, down from 10.

last_release_processed.json is deliberately not touched — the gate reported no new release, so there is nothing new to commit.

Deferred and carried-forward findings

Nothing was silently dropped. Still outstanding after this run:

  • ~12 /factory* API routes — Gate 0 deferrals, mapped -> internal. Re-check when the Factory REST API is published.
  • /memory_stores/* and oz memory* — deferred behind research-preview AIMemories; auto-surface via gated: when the flag goes GA.
  • Non-GA flags (StoredScreenshots, ShellWidgetHandoff, HistorySearchRankingV2, NativeShellCompletions, LrcActivitySignal, WarpingModelName) — tracked; snapshot diff re-flags on promotion.
  • agents.warp_agent.other.usage_display_unit — dogfood-gated by PricingTransparency.
  • /team CLI slash command — verdicted yes on 2026-09-04; feature PR docs(cli): document the /team slash command #684 still open. Not re-drafted here.
  • /docker-sandbox — deliberately -> internal (dogfood LocalDockerSandbox).
  • The ai credits stale-term rule — still contributes ~16 false positives per run. Unchanged open question for the docs owner in this file's Notes; a style-policy call, not something to settle unattended.
  • Two audit blind spots — the repo-wide slash check and the newly-found API extractor gap. Both are skill-script fixes, out of scope for a content run.

⚠️ Worth a look: automation/sync-agent-api-spec

The release automation's branch (pushed 2026-09-04, no open PR) stages 47 API operations where the docs sync policy allows 31. The 16 extras are 15 /factory* routes plus GET /harness-support/transcript, with 41 Factory schemas — all unreleased surface this repo has explicitly deferred. warp-server's publisher filters only on x-internal: true, and those operations are unmarked. Full detail and a suggested upstream fix are in #694.

Unverified claims

None — this PR changes no public page content. The ledger rows cite source files and audit output verified during the run, and the snapshot is mechanically regenerated by audit_docs.py --update-snapshot.

Documentation risk

Risk: low
Rationale: Internal Docs-team skill bookkeeping only: audit ledger rows and a regenerated surface snapshot. No public page content and no product claim.
Docs override: none

Co-Authored-By: Oz oz-agent@warp.dev
Co-Authored-By: Warp agent@warp.dev

Record the 2026-09-07 exhaustive drift-watch verdicts and advance the
surface snapshot's changelog marker from 2026.08.27 to 2026.09.02.

Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
@hongyi-chen hongyi-chen added the documentation Improvements or additions to documentation label Sep 7, 2026
@vercel

vercel Bot commented Sep 7, 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 9, 2026 4:50am UTC

Request Review

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review summary

The independent agent completed its review for this commit.

Findings

  • No blocking findings.

Verdict

Approve

@hongyi-chen
hongyi-chen marked this pull request as ready for review September 8, 2026 05:14
@warp-for-oss

warp-for-oss Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

@hongyi-chen

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 /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@hongyi-chen
hongyi-chen enabled auto-merge (squash) September 8, 2026 05:14

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR records the latest missing-docs drift-watch bookkeeping decisions and advances the generated surface snapshot marker from 2026.08.27 to 2026.09.02. The diff does not change public documentation pages, code behavior, comments, or tests.

Concerns

  • No blocking concerns found. The declared low documentation risk is consistent with the diff because the changes are limited to internal Docs-team skill bookkeeping and a generated snapshot marker.
  • No approved or repository spec context was provided, so there is no material implementation/spec drift to report.
  • Security pass found no sensitive implementation, authentication, authorization, secret-handling, or user-facing data-handling changes.

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

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review summary

The independent agent completed its review for this commit.

Findings

  • No blocking findings.

Verdict

Approve

@hongyi-chen
hongyi-chen merged commit f293ebd into main Sep 9, 2026
10 of 11 checks passed
@hongyi-chen
hongyi-chen deleted the missing-docs/bookkeeping-v0.2026.09.02.08.27.stable_01 branch September 9, 2026 04:46

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review summary

The independent agent completed its review for this commit.

Findings

  • No blocking findings.

Verdict

Approve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed documentation Improvements or additions to documentation warpy-factory Opened by the Warp factory agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant