chore(missing_docs): repoint surface map at renamed /agents/ paths and refresh snapshot - #463
Conversation
…ch audit Bookkeeping for the missing_docs drift-watch run: repoint the surface map at the renamed /agents/ doc paths, add mappings for the newly GA flags, mark the new Warp Agent CLI-only surfaces internal, and regenerate the surface snapshot. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
One dependency worth flagging: this PR maps |
|
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 refreshes the missing-docs surface map and snapshot after the /agent-platform/ to /agents/ documentation path rename, while classifying newly observed surfaces as documented, gated, or internal.
Concerns
No blocking concerns found. The changed doc targets in the annotated diff exist locally, the changes are reference-data-only, and spec_context.md reports that no approved or repository spec context was found for this PR.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
What
Bookkeeping for a
missing_docsdrift-watch run. The headline change is repairing the surface mapafter the IA rename.
Surface map
src/content/docs/agent-platform/tosrc/content/docs/agents/.The rename in feat(phase0): rename /agent-platform/ → /agents/ (IA restructure Phase 0) #420 moved the docs tree but left the map behind, which alone produced
68 map-hygiene findings and 64 phantom "undocumented feature" findings — about two thirds of
everything the audit reported.
ContextWindowUsageBreakdown(promoted dogfood → GA),GeminiEnterprise(promoted dogfood → GA; already covered by the BYOLLM Gemini Enterprise page), and
OscHyperlinks(promoted preview → GA). Removed the stale
OscHyperlinksignore-list entry, which the map-hygieneintegrity check correctly flagged as a mapped/ignored conflict.
internalentries for Warp Agent CLI-only surfaces (SettingSurfaces::TUI/SlashCommandSurfaces::TuiOnly), matching the existing precedent for that surface:/api-keys,/reset-statusline,/vim-mode, the fiveappearance.zero_state.show_*toggles, andagents.voice.voice_input_hold_key./add-api-keyand/clear-provider-api-key, which were removed from code and replacedby
/api-keys.internal, matching every other/factoryroute: Factory is not a released public product.Snapshot
Regenerated with
--update-snapshotso the next run diffs against this baseline.Result
Standing findings went from 195 → 47. Completeness accounting now reports 0 findings for
feature flags, CLI commands, slash commands, settings, and map hygiene, with no unaccounted surfaces.
npm run buildpasses (355 pages).Relationship to #446
#446 is an earlier bookkeeping PR from a previous run of this skill, still open. It predates the #420
rename, so it does not contain the
agent-platform/→agents/path repair, and it also carriesan
audit_docs.pyOpenAPI path-parsing fix that this PR does not touch. The two overlap onfeature_surface_map.mdandsurface_snapshot.json, so they need sequencing: merge #446 first, thenrebase this one (the snapshot is a wholesale regen, so re-running
--update-snapshotafter the rebaseis the cleanest resolution).
Companion PRs from this run
auto_approve_bypasses_command_denylistin the settings reference/copy-debugging-idslash commanddocs/settings-warp-agent-menu-path— stale Settings menu pathsClosed as duplicates of existing open PRs: #455 (→ #451), #460 (→ #440 and #387), #461 (→ #439).
Deferred findings (full list)
15 warp-server public API routes missing from
developers/agent-api-openapi.yaml. warp-server isprivate, so per the skill's public/private guardrail these were not hand-written. All of them back
already-public surfaces, so they belong to the
sync-openapi-specskill as a separate change:GET /agent/artifacts/{uid},GET /agent/artifacts/{uid}/download(back the publicoz artifactcommands)GET /agent/events,GET /agent/events/stream,POST /agent/events/{run_id}POST /agent/messages,GET /agent/messages/{run_id},POST /agent/messages/{id}/read,POST /agent/messages/{id}/delivered(back the publicoz run messagecommands)GET /agent/schedules/{id},PUT /agent/schedules/{id},DELETE /agent/schedules/{id},POST /agent/schedules/{id}/pause,POST /agent/schedules/{id}/resume(the collection endpoint isalready in the spec)
GET /agent/run-by-external-reference— genuinely ambiguous: it sits inagent_webhooks.gobesideharness-support plumbing. Left unmapped rather than marked
internalso it keeps resurfacing untilsomeone with context classifies it.
32 terminology/staleness findings (
ai credits→credits,warp terminal→Warp,agent-mode→Agent Mode, oneambient agent→cloud agent). These are pure wording and areowned by the
style_lintskill, which has a--fixmode. Sweeping them here would have buried thesubstantive changes in unrelated churn — and #452 is already an open attempt at exactly that sweep.
1 new server-side agent tool:
report_external_reference. Reported by the snapshot diff. Its onlyclient surface is
oz harness-support report-external-reference, a hidden command already mappedinternal, so there is no public surface to document yet.Verified as already covered, no action needed: agent execution profiles in settings files
(
execution_profilesis documented), computer-use overlay timing, MCP tool confirmation copy,code-block file reference opening, logout signing out of Warp web, and the Oz icon replacement.
gcloudauto-sign-in during GCP provider setup is already handled by open PR #442.Conversation: https://staging.warp.dev/conversation/c45bb2ea-d33b-4723-8249-478547f81a47
Run: https://oz.staging.warp.dev/runs/019fc891-7c04-779b-b006-328169d8a0d7
This PR was generated with Oz.