docs: document Vim indent and dedent operators in the code editor

[hongyi-chen]

What

Adds > / < and >> / << rows to the editing keybindings table in
code/code-editor/code-editor-vim-keybindings.mdx.

Why

Flagged by the missing_docs changelog cross-check (2026.07.31: "Added Vim < and > indent and
dedent operators to the code editor"). The keybindings table is the page readers scan to see what
is supported, and it did not list them.

Source of truth

• crates/vim/src/vim.rs — VimOperator::Indent / Dedent, the > and < key mapping, and the
  doubled >> / << line forms.
• app/src/code/editor/view/vim_handler.rs — the operator implementation in the code editor.

Deferred findings from this run

Nothing from the audit was silently dropped. The full deferral list lives in the companion
bookkeeping PR (docs/missing-docs-audit-bookkeeping); in summary:

• 15 warp-server public API routes missing from the OpenAPI spec — routed to the
  sync-openapi-spec skill rather than hand-written, per the skill's public/private guardrail.
• 32 terminology/staleness findings — owned by the style_lint skill.
• 1 new server-side agent tool (report_external_reference) — reached only through the hidden
  oz harness-support CLI, so no public surface to document yet.

---

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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 3, 2026 5:21pm

[hongyi-chen]

Closing as a duplicate of #439, which covers the same > / < Vim operators on the same page and does it more thoroughly (it adds a dedicated 'Indenting and dedenting' subsection with count and visual-mode forms).

Found while running the missing_docs drift-watch skill, which flagged this from the 2026.07.31 changelog entry. I didn't check for existing open PRs before drafting — my mistake. #439 is the better change; no rebase needed since it's already on a current path.