diff --git a/.agents/skills/missing_docs/references/changelog_decisions.md b/.agents/skills/missing_docs/references/changelog_decisions.md index 3d503d1e..3c384aba 100644 --- a/.agents/skills/missing_docs/references/changelog_decisions.md +++ b/.agents/skills/missing_docs/references/changelog_decisions.md @@ -32,6 +32,29 @@ Newest first. One row per PR number — usually a `warpdotdev/warp` changelog it | PR | Decided | Verdict | Gate / disqualifier | Reason and outcome | |---|---|---|---|---| +| n/a (2026-09-22 residual re-verification of v0.2026.09.16.08.27.stable_02) | 2026-09-22 | n/a | Not a verdict | Fifth drift-watch pass over this stable; the release gate on `main` still reports it as new because the marker lives only on this branch (`last_release_processed.json` already carries `v0.2026.09.16.08.27.stable_02` here). Extended #768 rather than opening a second bookkeeping PR. Independently re-verified rather than carrying forward: both audit modes exited 0 with `audits_skipped: []` and an empty `unaccounted` bucket (297 flags, 91 CLI commands, 223 API routes, 65 slash commands, 232 settings). Against this branch only the 24 already-decided `potentially_stale_docs` rows remain; against `main` the three mapped internal routes (`GET /agent/runs/{runId}/harness-usage`, `POST /harness-support/usage`, `POST /factory/scorers/{scorer_id}/backfill`) and `WindowsVideoRecording` reappear until #768 merges. Re-checked Gate 0 at source: `getRunHarnessUsage` and `publishHarnessUsage` still carry `x-internal: true` in warp-server `public_api/openapi.yaml`; `createScoringBackfill` remains under the factory tag that is itself `x-internal: true` (released `developers/agent-api-openapi.yaml` still has zero `/factory` paths and no harness-usage operation); `WindowsVideoRecording` is still in `DOGFOOD_FLAGS` (`crates/warp_features/src/lib.rs:1051`). `--update-snapshot` against current `warp` (`master`, `f4f9b8838`, 2026-09-21) and `warp-server` (`develop`, `28e045197`, 2026-09-21) reproduced this branch's `surface_snapshot.json` byte for byte. No new feature PR; feature PR docs#767 (docker-registry secrets) remains the only content PR from the 2026-09-18 triage. | +| n/a (2026-09-21 residual re-verification of v0.2026.09.16.08.27.stable_02) | 2026-09-21 | n/a | Not a verdict | Fourth drift-watch pass over this stable; the release gate on `main` still reports it as new because the marker lives only on this branch (`last_release_processed.json` already carries it here). Extended #768 rather than opening a second bookkeeping PR. Merged `origin/main` (`298e5a14`, two unrelated commits: docs#752 factory code-forge wording and docs#763 AFDocs link absolutization) into the branch first, so the snapshot and audit describe the post-merge tree rather than a stale one. Both audit modes exited 0 with `audits_skipped: null` and an empty `unaccounted` bucket (297 flags, 91 CLI commands, 223 API routes, 65 slash commands, 232 settings). Against this merged branch, `undocumented_features`, `undocumented_cli_commands`, `undocumented_api_endpoints`, `undocumented_slash_commands`, `undocumented_settings`, `surface_changes`, `changelog_review`, `map_hygiene`, `stale_doc_references`, and `unlisted_pages` are **all zero**; only the 24 already-decided `potentially_stale_docs` rows remain. `--update-snapshot` against `warp` (`master`, `3c520bed7`, 2026-09-21) and `warp-server` (`develop`, `a1f654c93`, 2026-09-21) — both a day newer than the 2026-09-20 pass — reproduced this branch's `surface_snapshot.json` **byte for byte**, so no tracked surface moved in the interval. Re-verified Gate 0 at source rather than carrying it forward: `getRunHarnessUsage` carries `x-internal: true` (openapi.yaml:7226-7235) and `publishHarnessUsage` carries `x-internal: true` (openapi.yaml:10194-10205); `createScoringBackfill` (openapi.yaml:10922) is **not** `x-internal` but sits under `/factory`, which `sync_openapi.py:107` excludes wholesale via `EXCLUDED_PATH_PREFIXES`, and `developers/agent-api-openapi.yaml` still has zero `/factory` paths — so all three remain correctly mapped `-> internal`. Also swept the three documented blind spots the audit cannot see itself: the surface-scoped slash check across all 65 registry entries (33 GuiOnly, 18 TuiOnly, 14 GuiAndTui, none carrying a `feature_flag`) leaves only `/docker-sandbox` uncovered, still dogfood-gated by `LocalDockerSandbox` (`crates/warp_features/src/lib.rs:1064`, inside `DOGFOOD_FLAGS`); `CreateProvider` still has exactly three variants (`claude`, `codex`, `docker-registry`, `crates/warp_cli/src/secret.rs:66-75`), so the `Args`-struct extractor gap hides nothing new; and `--weak-coverage` returns 82, unchanged from 2026-09-14. Re-checked the five staleness term classes at their source lines and confirmed each is a false positive or style-only: `warp ai` → the historical FAQ heading `agents/getting-started/faqs.mdx:18`; `generate command` → the live "Generate commands as command-line input" heading on the "Generate (Legacy)" page; `ai command` → AI Command Search at `terminal/entry/index.mdx:11`; `ai credits` → the bucket name (still the unresolved style-policy question in the Notes, deliberately left for a human); `warp terminal` → permitted distinguishing usage, with `terminal/more-features/index.mdx:4` still the one genuine wording nit that SKILL.md assigns to `style_lint`. All three skill test suites pass (19 + 18 + release-gate), so no extractor has rotted. `npm ci && npm run build` passes on the merged branch (388 Markdown docs, 390 HTML files). `suggest_reviewers.py` resolves only `@warpdotdev/oss-maintainers` for `crates/warp_features/src/lib.rs`, with all three warp-server handler paths unowned, so the PR keeps no requested reviewer. No new feature PR, and no second bookkeeping PR. | +| n/a (2026-09-20 residual re-verification of v0.2026.09.16.08.27.stable_02) | 2026-09-20 | n/a | Not a verdict | Drift-watch re-entry after the release gate on `main` still reported this stable as new (bookkeeping PR #768 unmerged; `last_release_processed.json` already carries `v0.2026.09.16.08.27.stable_02` on the branch). Extended #768 rather than opening a second bookkeeping PR. Independently re-verified rather than carrying forward: both audit modes exited 0 with `audits_skipped: []` and an empty `unaccounted` bucket (297 flags, 91 CLI commands, 223 API routes, 65 slash commands, 232 settings). Against this branch, `surface_changes`, `changelog_review`, and `undocumented_api_endpoints` are all empty; only the 24 already-decided `potentially_stale_docs` rows remain. `--update-snapshot` against fresh `warp` (`master`, `c1a27a6a2`, 2026-09-20) and `warp-server` (`develop`, `2e3da2cf1`, 2026-09-20) reproduced this branch's `surface_snapshot.json` **byte for byte**. Re-confirmed Gate 0 for the three routes mapped on 2026-09-18: `GET /agent/runs/{runId}/harness-usage` still has `x-internal: true` (`getRunHarnessUsage`, openapi.yaml:7235); `POST /harness-support/usage` still has `x-internal: true` (`publishHarnessUsage`, openapi.yaml:10205); `POST /factory/scorers/{scorer_id}/backfill` remains under the unreleased `factory` tag (`createScoringBackfill`, openapi.yaml:10925) with zero `/factory` paths in `developers/agent-api-openapi.yaml`. `WindowsVideoRecording` still dogfood. All 13 changelog/`oz_updates` bullets and #15913 already carry ledger verdicts; feature PR docs#767 remains open with reviewer `dannyneira`. No new feature PR, and no second bookkeeping PR. | +| n/a (2026-09-19 residual re-verification of v0.2026.09.16.08.27.stable_02) | 2026-09-19 | n/a | Not a verdict | Drift-watch re-entry after the release gate on `main` still reported this stable as new (bookkeeping PR #768 unmerged; `last_release_processed.json` already carries `v0.2026.09.16.08.27.stable_02` on the branch). Extended #768 rather than opening a second bookkeeping PR. Independently re-verified rather than carrying forward: both audit modes exited 0 with `audits_skipped: []` and an empty `unaccounted` bucket (297 flags, 91 CLI commands, 223 API routes, 65 slash commands, 232 settings). Against this branch, `surface_changes`, `changelog_review`, and `undocumented_api_endpoints` are all empty; only the 24 already-decided `potentially_stale_docs` rows remain. `--update-snapshot` against fresh `warp` (`master`, `03832b3a8`, 2026-09-18) and `warp-server` (`develop`, `f3bb86d4d`, 2026-09-19) reproduced this branch's `surface_snapshot.json` **byte for byte**. Re-confirmed Gate 0 for the three routes mapped on 2026-09-18: `GET /agent/runs/{runId}/harness-usage` still has `x-internal: true` (`getRunHarnessUsage`, openapi.yaml:7235); `POST /harness-support/usage` still has `x-internal: true` (`publishHarnessUsage`, openapi.yaml:10205); `POST /factory/scorers/{scorer_id}/backfill` remains under the unreleased `factory` tag with zero `/factory` paths in `developers/agent-api-openapi.yaml`. `WindowsVideoRecording` still dogfood. All 13 changelog/`oz_updates` bullets and #15913 already carry ledger verdicts; feature PR docs#767 remains open with reviewer `dannyneira`. No new feature PR, and no second bookkeeping PR. | +| n/a (release v0.2026.09.16.08.27.stable_02) | 2026-09-18 | n/a | Not a verdict | Drift-watch processed stable `v0.2026.09.16.08.27.stable_02` (released 2026-09-16). Feature PR docs#767 documents private image credentials; this bookkeeping PR carries map, ledger, release marker, and snapshot. | +| [#15913](https://github.com/warpdotdev/warp/pull/15913) — `oz secret create docker-registry` | 2026-09-18 | yes | Gate 0 cleared; Gate 1 + Gate 2 | Previously deferred 2026-09-11 (not in stable). Now in `v0.2026.09.16.08.27.stable_02`. Knobs: `--host`, `--username`, `--password`, `--password-file` (`DockerRegistryCreateArgs`, `crates/warp_cli/src/secret.rs:190-217`); web type **Private image credential**. Gate 2: `--password` conflicts with `--password-file` and help text warns about shell history/`ps` leaks. Not env-injected (`TestGetSecretsForTask_ExcludesRegistryCredentialEvenWhenExplicitlyNamed`). Updated `platform/secrets.mdx`, `platform/runners.mdx`, `factories/factory-as-code.mdx` (feature PR docs#767). No CLI map entry for the provider subcommand — extractor blind spot (Args struct) recorded 2026-09-11. | +| [#15903](https://github.com/warpdotdev/warp/pull/15903) fzf/atuin handoff | 2026-09-18 | no | Already covered (ShellWidgetHandoff) | Changelog new-feature bullet for ctrl-r/ctrl-t fzf and atuin. Covered by 2026-09-11 ShellWidgetHandoff Gate 3 update on `command-search.mdx` (docs#734 merged). | +| [#15903](https://github.com/warpdotdev/warp/pull/15903) native shell completions | 2026-09-18 | no | Already covered (Gate 1) | Settings knobs `terminal.input.warp_completions_enabled` / `native_shell_completions_enabled` already documented in `all-settings.mdx`; NativeShellCompletions GA correction shipped docs#733. | +| [#15903](https://github.com/warpdotdev/warp/pull/15903) history ranking | 2026-09-18 | no | Already decided (HistorySearchRankingV2) | Same ranking weights verdicted no on 2026-09-11 as no user-observable change requiring action. | +| [#15879](https://github.com/warpdotdev/warp/pull/15879) Windows Materials backdrop | 2026-09-18 | no | Already covered (Gate 1) | `appearance.window.backdrop` documented in docs#733 / map entry 2026-09-12. Changelog is the stable ship note for that setting. | +| [#16006](https://github.com/warpdotdev/warp/pull/16006) | 2026-09-18 | no | Disqualified: bug fix / small and intuitive | Parallel clone error reporting lists only failed repos. Improves an existing failure message; no knob or workflow change. | +| [#15844](https://github.com/warpdotdev/warp/pull/15844) | 2026-09-18 | no | Disqualified: no user-observable change requiring action | Discover and cache build tools in nested repository directories. Agent/runtime cache behavior; no setting, CLI flag, or user workflow change. | +| [#15905](https://github.com/warpdotdev/warp/pull/15905) | 2026-09-18 | no | Disqualified: pure UI affordance / small and intuitive | Workspace admins remove members from team settings. In-product UI action; no settings-file key or non-obvious setup. | +| [#15880](https://github.com/warpdotdev/warp/pull/15880) | 2026-09-18 | no | Disqualified: small and intuitive | Native workspace members leave a team without losing workspace access. Membership UI behavior understood on sight. | +| [#15881](https://github.com/warpdotdev/warp/pull/15881) | 2026-09-18 | no | Disqualified: pure UI affordance / small and intuitive | Native workspace users browse and join another open team from Teams settings. Discoverable in-product. | +| [#15921](https://github.com/warpdotdev/warp/pull/15921) | 2026-09-18 | no | Disqualified: bug fix restoring intended behavior | Native Oz follow-up prompts no longer interrupt one another. Restores expected multi-follow-up delivery. | +| [#15863](https://github.com/warpdotdev/warp/pull/15863) | 2026-09-18 | no | Disqualified: bug fix restoring intended behavior | Preserved team-scoped credentials when launching orchestrated agent runs. Restores expected credential scope; secrets/orchestration docs already cover team secrets. | +| [#16046](https://github.com/warpdotdev/warp/pull/16046) | 2026-09-18 | no | Disqualified: bug fix restoring intended behavior | Follow-up messages with attachments delivered at the next steering opportunity instead of waiting for turn end. Restores intended steering behavior. | +| GET /agent/runs/{runId}/harness-usage | 2026-09-18 | deferred | Gate 0 | New route in agent_webhooks.go. Marked `x-internal: true` in warp-server `public_api/openapi.yaml`; absent from `developers/agent-api-openapi.yaml`. Mapped `-> internal`. Re-check if marker drops; route via sync-openapi-spec. | +| POST /harness-support/usage | 2026-09-18 | deferred | Gate 0 | publishHarnessUsage for third-party harness usage snapshots. Tag `harness-support`, `x-internal: true`; harness-support excluded from released docs OpenAPI. Mapped `-> internal`. | +| POST /factory/scorers/{scorer_id}/backfill | 2026-09-18 | deferred | Gate 0 | createScoringBackfill under factory tag. Released OpenAPI has zero `/factory` paths (same Factory REST exclusion). Mapped `-> internal`. Re-check when factory API is published. | +| WindowsVideoRecording (flag added, dogfood) | 2026-09-18 | deferred | Gate 0 | New dogfood-status feature flag. Not GA. Tracked_non_ga via snapshot; re-check on promotion. No ignore-list entry required for dogfood. | +| n/a (24 potentially_stale_docs, 2026-09-18 run) | 2026-09-18 | no | Already decided / owned by style_lint | Same term set as 2026-09-14/11 (`ai credits` bucket-name false positives, permitted Warp terminal distinguishing usage, historical Warp AI FAQ, live Generate / AI Command Search headings). No missing content. | | n/a (2026-09-16 exhaustive re-verification sweep) | 2026-09-16 | n/a | Not a verdict | A second exhaustive drift-watch pass over the same stable release, two days after the 2026-09-14 pass that opened this PR. Nothing new to decide: **no tracked surface changed in the interval.** Running `--update-snapshot` against fresh `warp` (`master`, `91dad6a70`) and `warp-server` (`develop`, `91b349221`) checkouts, both dated 2026-09-16, reproduced this branch's `surface_snapshot.json` **byte for byte** across 296 flags, 91 CLI commands, 220 API routes, 65 slash commands, 232 settings, 23 web routes, 72 server tools, and 17 bundled skills. Both audit modes exited 0 with `audits_skipped: []` and an empty `unaccounted` bucket. Against `main` the run reproduced the 2026-09-14 findings exactly — one `undocumented_api_endpoints` entry, one `surface_changes` entry, both `GET /networking/egress-ranges`, plus the 24 staleness rows; with this branch's map entry applied, the first two drop to 0 and only the already-decided staleness rows remain. Independently re-verified the load-bearing evidence rather than carrying it forward: the `networking` tag and the `getEgressRanges` operation both still carry `x-internal: true` in warp-server `public_api/openapi.yaml` (lines 31-33 and 42-43), and five staleness term classes were re-checked at their source lines (`warp ai` → the historical FAQ heading; `generate command` → the live "Generate commands as command-line input" heading; `ai command` → AI Command Search; `ai credits` → the bucket name; `warp terminal` → the permitted distinguishing usage). The skill's three test suites pass (19 + 18 + release-gate tests), so no extractor has rotted. `npm ci && npm run build` passes on this branch at 386 Markdown docs and 388 HTML files. `suggest_reviewers.py` again resolves only the `@warpdotdev/fa-warp-3` team, with `router/handlers/public_api/networking.go` unowned, so the PR keeps no requested reviewer. No feature PR, and no second bookkeeping PR — this branch was extended per the skill's one-open-bookkeeping-PR rule. | | GET /networking/egress-ranges | 2026-09-14 | deferred | Gate 0 | Returns the canonical outbound IP ranges for Warp-hosted agents, scoped to the authenticated principal's active team (`RegisterNetworkingRoutes` / `EgressRangesHandler`, `router/handlers/public_api/networking.go:17-77`, behind `middleware.EnforceAuth()`). The only new surface this run — it is both the sole `undocumented_api_endpoints` finding and the sole `surface_changes` entry. Gate 0 fails twice over in warp-server's canonical `public_api/openapi.yaml`: the `networking` tag carries `x-internal: true` and so does the `getEgressRanges` operation, and `sync_openapi.py` drops `x-internal` operations wholesale, so the route cannot reach `developers/agent-api-openapi.yaml` while the markers stand (that file has zero `networking` paths and zero `x-internal` entries today). It backs the Admin Panel's hosted-agent egress CIDR list (`client/src/components/admin/team/platform/HostedAgentEgressCIDRs.tsx`), not the released public Agent API. Not a content gap either: the ranges themselves are already published on `platform/warp-hosting.mdx` under "Networking". Mapped `-> internal`. Re-check if the `x-internal` markers come off, and route it through sync-openapi-spec rather than hand-drafting. | | n/a (hardcoded egress CIDR list on platform/warp-hosting.mdx) | 2026-09-14 | no | Not a docs gap / noted for the owner | Surfaced while triaging the route above, recorded so it is not silently dropped. `platform/warp-hosting.mdx` publishes the hosted-agent egress ranges as a hardcoded bullet list, and warp-server now computes the same set server-side (`logic/ai/ambient_agents/networking/egress_ranges.go`). The page can therefore drift from the canonical source with nothing to catch it. No docs change is available: the endpoint is `x-internal`, so the page cannot point readers at it, and the current list is not known to be wrong. Flagging the durability question for the docs owner rather than editing correct content. | @@ -42,7 +65,7 @@ Newest first. One row per PR number — usually a `warpdotdev/warp` changelog it | GET /factory/{uid}/setup-progress, POST /factory/{uid}/setup-progress/dismiss | 2026-09-12 | deferred | Gate 0 | Both marked `x-internal: true` in warp-server `public_api/openapi.yaml` (`getFactorySetupProgress`, dismiss counterpart) inside the unreleased `/factory` namespace. Released `developers/agent-api-openapi.yaml` has zero `/factory` paths. Missed in the 2026-09-11 map pass that covered sibling factory routes; mapped both `-> internal` on this bookkeeping extension. Re-check when the factory API is published. | | appearance.window.backdrop (map residual) | 2026-09-12 | yes | Gate 1 (map only) | Setting already verdicted yes on 2026-09-11 with feature PR docs#733, but the surface-map entry was never added so coverage kept flagging it. Mapped `appearance.window.backdrop -> terminal/settings/all-settings.mdx` on this extension. | | n/a (third residual sweep of v0.2026.09.09.08.26.stable_02, 2026-09-12) | 2026-09-12 | n/a | Not a verdict | Drift-watch re-entry after the release gate on `main` still reported this stable as new (bookkeeping PR #736 unmerged). Checked out and extended #736 rather than opening a second bookkeeping PR. Independently re-verified Gate 0 for the two remaining unmapped factory routes above; re-confirmed #15913 docker-registry flags still deferred (Gate 0, not in any stable); re-confirmed the 15 changelog/`oz_updates` bullets and three flag promotions already carry ledger verdicts; `potentially_stale_docs` (24) still style_lint-owned. Feature PRs docs#733, docs#734, docs#735 remain open with reviewer `dannyneira`. Regenerated `surface_snapshot.json` so setup-progress leaves the `--diff` added bucket; #15913 flags enter the baseline and rely on the deferred ledger row plus the next stable changelog for re-surface. No new feature PR. | -| [#15913](https://github.com/warpdotdev/warp/pull/15913) — `oz secret create docker-registry` (`--host`, `--username`, `--password`, `--password-file`) | 2026-09-11 | deferred | Gate 0 | New `docker-registry` provider subcommand on `oz secret create` that stores a container registry credential (`CreateProvider::DockerRegistry` / `DockerRegistryCreateArgs`, `crates/warp_cli/src/secret.rs:72-74` and `190-217`). The four flags are real Gate 1 knobs, and `--password` declares `conflicts_with = "password_file"` with help text recommending `--password-file` for scripted use because a password on the command line leaks through shell history and `ps` — that would also carry Gate 2. Gate 0 stops both: the commit landed on warp `master` at `7bfa9da6b`, 2026-09-11 16:47 UTC, two days after the `v0.2026.09.09.08.26.stable_02` cut (2026-09-09 08:26 UTC), so it is in no stable release and absent from the 2026.09.09 changelog. `surface_snapshot.json` was deliberately **not** regenerated on this branch, so the four flags stay out of the baseline and `--diff` re-fires them on the first run after they ship. Re-check when a stable release contains #15913; target pages are `platform/secrets.mdx` and the `oz secret create` entry in `reference/cli/index.mdx`. | +| [#15913](https://github.com/warpdotdev/warp/pull/15913) — `oz secret create docker-registry` (`--host`, `--username`, `--password`, `--password-file`) | 2026-09-11 | yes (see 2026-09-18) | Gate 0 cleared on ship | Superseded by the 2026-09-18 yes row when `v0.2026.09.16.08.27.stable_02` shipped. Feature PR docs#767. | | n/a (second exhaustive sweep of v0.2026.09.09.08.26.stable_02, 2026-09-11 17:00Z) | 2026-09-11 | n/a | Not a verdict | A second drift-watch pass over the same release, an hour after the 16:08Z pass that produced this PR and feature PRs docs#733, docs#734, and docs#735. Both audit modes exited 0 with no `audits_skipped` and an empty `unaccounted` bucket (296 flags, 91 CLI commands, 217 API routes, 65 slash commands, 232 settings). Independently re-verified the load-bearing Gate 0 evidence for all eight `undocumented_api_endpoints`: every one carries `x-internal: true` in `warp-server/public_api/openapi.yaml`, and `developers/agent-api-openapi.yaml` still has zero `/factory` or `/factory-inbox` paths. Re-confirmed zero findings in `undocumented_features`, `undocumented_cli_commands`, `undocumented_slash_commands`, `map_hygiene`, `stale_doc_references`, and `unlisted_pages`. The only item without a verdict was #15913 above, which the earlier pass could not see because its checkout predated the commit. `npm run build` passes on `main` with docs#733, docs#734, and docs#735 cherry-picked together (385 Markdown docs, 387 HTML files). No new feature PR. | | appearance.window.backdrop | 2026-09-11 | yes | Gate 1 | Always-on Windows setting `appearance.window.backdrop` (`WindowBackdrop` in `app/src/window_settings.rs:19-28`, default `None`, options `none`/`mica`/`acrylic`/`mica_alt`; UI **Window backdrop** on **Settings** > **Appearance** > **Window**). Replaces the deprecated binary `override_blur_texture` Acrylic toggle. Documented in `all-settings.mdx` and updated `size-opacity-blurring.mdx` (feature PR). | | NativeShellCompletions (flag preview→ga) | 2026-09-11 | yes | Gate 1 (factual correction) | Flag now a default cargo feature (`app/Cargo.toml` default features include `native_shell_completions`) and no longer in `PREVIEW_FLAGS`. Documentable knobs remain `terminal.input.warp_completions_enabled` and `terminal.input.native_shell_completions_enabled` already in `all-settings.mdx`; removed the stale "Native shell completions Preview" availability gate from both rows (feature PR). Flag stays on the ignore list as a sub-feature toggle. | diff --git a/.agents/skills/missing_docs/references/feature_surface_map.md b/.agents/skills/missing_docs/references/feature_surface_map.md index 8cb974a0..c2c5e81f 100644 --- a/.agents/skills/missing_docs/references/feature_surface_map.md +++ b/.agents/skills/missing_docs/references/feature_surface_map.md @@ -407,6 +407,13 @@ POST /harness-support/finish-task -> internal POST /harness-support/report-shutdown -> internal POST /harness-support/upload-snapshot -> internal POST /harness-support/commit-snapshot -> internal +# Cumulative Claude Code / Codex usage snapshot for the current cloud execution +# (publishHarnessUsage). Marked `x-internal: true` upstream; harness-support tag +# is excluded from the released docs OpenAPI copy. +POST /harness-support/usage -> internal +# Read harness usage for a run (getHarnessUsage / agent_webhooks.go). Marked +# `x-internal: true` upstream; not in developers/agent-api-openapi.yaml. +GET /agent/runs/{runId}/harness-usage -> internal # Oz Factory REST API (router/handlers/public_api/factory*.go). Warp Factories # is now documented publicly (src/content/docs/factories/) as an Early Access @@ -548,6 +555,9 @@ DELETE /factory/scorers/{scorer_id} -> internal GET /factory/scorers/{scorer_id}/results -> internal GET /factory/scorers/{scorer_id}/results/reasons -> internal GET /factory/scorers/{scorer_id}/metrics/pass-rate -> internal +# Date-bounded scoring backfill (createScoringBackfill). Factory tag; released +# OpenAPI has zero /factory paths. Stays internal until the Factory API ships. +POST /factory/scorers/{scorer_id}/backfill -> internal # The scorer pause/resume routes and the autofix-config trio were replaced by # the self-improvement-config routes below; their dead map entries were pruned. GET /factory/scorers/{scorer_id}/self-improvement-config -> internal diff --git a/.agents/skills/missing_docs/references/last_release_processed.json b/.agents/skills/missing_docs/references/last_release_processed.json index f57782cc..fec54a56 100644 --- a/.agents/skills/missing_docs/references/last_release_processed.json +++ b/.agents/skills/missing_docs/references/last_release_processed.json @@ -1,8 +1,8 @@ { - "last_processed_version": "v0.2026.09.09.08.26.stable_02", - "release_date": "2026-09-09T08:26:00+00:00", - "processed_at": "2026-09-11T16:08:30Z", + "last_processed_version": "v0.2026.09.16.08.27.stable_02", + "release_date": "2026-09-16T08:27:00+00:00", + "processed_at": "2026-09-18T16:09:43Z", "changelog_entry_count": 21, - "oz_updates_count": 9, + "oz_updates_count": 3, "_comment": "Written by check_new_release.py --commit after a drift-watch run completes triage. Kept separate from surface_snapshot.json, which is regenerated wholesale and would lose this marker. Do not hand-edit; to force a re-run of the current release, delete this file." } diff --git a/.agents/skills/missing_docs/references/surface_snapshot.json b/.agents/skills/missing_docs/references/surface_snapshot.json index 79266fc9..a4fd757c 100644 --- a/.agents/skills/missing_docs/references/surface_snapshot.json +++ b/.agents/skills/missing_docs/references/surface_snapshot.json @@ -295,6 +295,7 @@ "WelcomeBlock": "other", "WelcomeTips": "other", "WellKnownMcpIds": "ga", + "WindowsVideoRecording": "dogfood", "WithSandboxTelemetry": "other", "WorkflowAliases": "ga" }, @@ -864,6 +865,7 @@ "GET /api/v1/agent/runs", "GET /api/v1/agent/runs/{runId}", "GET /api/v1/agent/runs/{runId}/handoff/attachments", + "GET /api/v1/agent/runs/{runId}/harness-usage", "GET /api/v1/agent/runs/{runId}/timeline", "GET /api/v1/agent/runs/{runId}/trace", "GET /api/v1/agent/runs/{runId}/transcript", @@ -990,6 +992,7 @@ "POST /api/v1/factory/avatar", "POST /api/v1/factory/run-scoring/dispatches", "POST /api/v1/factory/scorers", + "POST /api/v1/factory/scorers/{scorer_id}/backfill", "POST /api/v1/factory/webhooks", "POST /api/v1/factory/webhooks/dry-run", "POST /api/v1/factory/webhooks/{uid}/rotate", @@ -1025,6 +1028,7 @@ "POST /api/v1/harness-support/resolve-prompt", "POST /api/v1/harness-support/transcript", "POST /api/v1/harness-support/upload-snapshot", + "POST /api/v1/harness-support/usage", "POST /api/v1/memory_stores", "POST /api/v1/memory_stores/{uid}/memories", "POST /api/v1/oauth/consent", @@ -1465,5 +1469,5 @@ "verify-ui-change-in-cloud": "dogfood", "warpctrl": "bundled" }, - "changelog_last_version": "2026.09.09" + "changelog_last_version": "2026.09.16" }