chore(missing_docs): bookkeeping for v0.2026.09.02.08.27.stable_01

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

@@ -32,6 +32,13 @@ Newest first. One row per PR number — usually a `warpdotdev/warp` changelog it
 
 | PR | Decided | Verdict | Gate / disqualifier | Reason and outcome |
 |---|---|---|---|---|
+| GET /agent/conversations/{conversation_id}/transcript | 2026-09-07 | yes | Gate 0 pass, routed to sync-openapi-spec | Released public endpoint absent from the published reference. Tagged `agent`, `bearerAuth`, and **not** `x-internal` in `warp-server/public_api/openapi.yaml`, so `sync_openapi.py --mode diff` classifies it as public with no `!` warning; its sibling `GET /agent/runs/{runId}/transcript` is already published. Backs the raw third-party-harness transcript output shipped in `v0.2026.09.02.08.27.stable_01` (#15642), whose CLI half was verdicted `no` as a bug fix — the API half is a genuine publish gap, not the same item. Not hand-documented (warp-server is private): regenerated the subset via sync-openapi-spec (docs#694), which adds this one operation and removes none. No surface-map entry added — see the extractor blind-spot row below. |
+| n/a (audit blind spot: generated handler registration, 2026-09-07) | 2026-09-07 | no | Audit accuracy, not a docs gap | The API extractor parses literal gin registrations, so it cannot see routes registered through `public_api_types.RegisterHandlersWithOptions` (`agent_conversations.go:214`). Three routes are invisible to it: `/agent/conversations/{conversation_id}/transcript`, `/fork`, and `/rename` — none appear in `surface_snapshot.json`'s 207 `api_routes`. This is the API-side analogue of the documented repo-wide slash blind spot, and it is why the transcript gap above needed a spec-level diff to surface. Deliberately did **not** add map entries for these routes: map hygiene validates entries against extracted routes, so an entry for a route the extractor cannot see would register as a dead entry every run. Recorded here instead; fixing the extractor is a skill-script change, out of scope for a content run. |
+| n/a (automation/sync-agent-api-spec would leak unreleased surface, 2026-09-07) | 2026-09-07 | no | Gate 0 protection, not a docs gap | The release automation's unmerged branch (pushed 2026-09-04, no open PR) stages 47 operations against this run's safe 31. The extra 16 are 15 `/factory*` routes plus `GET /harness-support/transcript`, with 41 Factory schemas — all deliberately excluded by `EXCLUDED_PATH_PREFIXES`/`EXCLUDED_TAGS`, and all already carrying Gate 0 deferrals in this ledger. Cause: warp-server's publisher filters only on `x-internal: true` and those Factory operations are unmarked (several are tagged `agent` upstream). Flagged in docs#694 with a request that the server team mark them `x-internal` so both publishers agree. No docs change here. |
+| n/a (10 changelog items, 2026.09.02, re-surfaced 2026-09-07) | 2026-09-07 | no | Already decided | The `--diff` run re-reported all 10 items for 2026.09.02 (#14916, #15691, #15625, #15579, #15642, #15605, #15380, #15574, #15714, #15616) because `surface_snapshot.json` still recorded `changelog_last_version: 2026.08.27` — docs#682 landed the changelog entry after docs#657 regenerated the snapshot. Every PR number already carries a `no` verdict from 2026-09-04; none re-evaluated. The snapshot regen in this PR advances the marker to 2026.09.02 so the next run stops re-reporting them. |
+| n/a (24 potentially_stale_docs, 2026-09-07 run) | 2026-09-07 | no | Disqualified: not a docs gap / owned by style_lint | Up from 23 because docs#672 and docs#683 added `AI credits` bucket-name prose to `enterprise/support-and-resources/billing.mdx` and `errors/insufficient-credits.mdx`. Re-verified line by line: 16 files are the known `ai credits` bucket-name false positive (unresolved style-policy question in the Notes below), 10 `warp terminal` hits are the distinguishing usage the style guide permits (client vs. backend, local terminal vs. cloud harness), `warp ai` is the historical FAQ heading, `generate command` matches the live "Generate commands" heading, and `ai command` matches AI Command Search. One borderline nit — `terminal/more-features/index.mdx:4` "Warp terminal features" is not distinguishing — is a pure wording issue that SKILL.md assigns to `style_lint`. No missing content. |
+| n/a (81 --weak-coverage feature findings, 2026-09-07 re-run) | 2026-09-07 | no | Disqualified: not a docs gap / heuristic false positive | Re-ran `--weak-coverage` for exhaustiveness: 81 findings, matching the 2026-09-04 count. Same mapped-page keyword misses verified on 2026-08-26, 2026-08-28, 2026-09-02, and 2026-09-04. No new gap. |
+| n/a (surface-scoped slash re-verification, both surfaces, 2026-09-07) | 2026-09-07 | no | Already covered | Re-ran the scoped check that works around the repo-wide slash blind spot, parsing all 65 `name:` entries in `static_commands/commands.rs` (47 GUI-visible, 32 TUI-capable; no entry carries a `feature_flag` in that file). Only two absences: `/docker-sandbox` from the GUI page (deliberately `-> internal`, dogfood `LocalDockerSandbox`) and `/team` from `agents/cli/`, already verdicted yes on 2026-09-04 with feature PR docs#684 still open. No new gap. |
 | /team (Warp Agent CLI slash command table) | 2026-09-04 | yes | Gate 1 | Corrects the 2026-08-28 row's claim that "all 32 TUI-capable commands" are covered under `agents/cli/`, and the 2026-09-02 scoped re-verification, which checked only the GUI side. `/team` (`StaticCommand TEAM`, `SlashCommandSurfaces::TuiOnly`, `Availability::ALWAYS`, no `feature_flag`, `static_commands/commands.rs:566`) is GA and was the one TUI-capable command absent from the slash command table on `agents/cli/reference.mdx`, which presents itself as the complete list. Invisible to the audit twice over: mapped `-> internal` (right for the GUI page, wrong for the CLI table) and hidden by the repo-wide slash check. Opens `TuiTeamMenuModel` (`crates/warp_tui/src/team_menu.rs`) and re-scopes the session in place, unlike the desktop app's new window per team. Added the table row plus one behavior paragraph (feature PR docs#684); remapped `/team` to that page. |
 | n/a (surface-scoped slash re-verification, TUI side, 2026-09-04) | 2026-09-04 | no | Already covered | Ran the scoped check against both surfaces this time. Of 63 unique static commands, the only GUI-visible one missing from `agents/capabilities/slash-commands.mdx` is `/docker-sandbox` (deliberately `-> internal`, dogfood `LocalDockerSandbox`), and the only TUI-capable one missing from `agents/cli/` was `/team`, handled above. No other gap. |
 | n/a (11 TUI-only slash entries mapped `internal`) | 2026-09-04 | no | Map accuracy, not a docs gap | `/exit`, `/status`, `/api-keys`, `/vim-mode`, `/theme`, `/voice`, `/clear`, `/logout`, `/statusline`, `/reset-statusline`, and `/natural-language-detection` are mapped `-> internal` yet all appear in the CLI reference's slash command table, so the sentinel overstates "no public docs". Suppression behaves identically whether they point at `internal` or at that page, so this changes no audit outcome. Left as-is with a NOTE on the `/team` entry rather than churning 11 lines on a PR already under review. |

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

@@ -1447,5 +1447,5 @@
     "verify-ui-change-in-cloud": "dogfood",
     "warpctrl": "bundled"
   },
-  "changelog_last_version": "2026.08.27"
+  "changelog_last_version": "2026.09.02"
 }