[dannyneira]

Summary

Adds the missing stable changelog entry for v0.2026.11.11.08.17.stable_01 (2026.11.12). Licenses and telemetry already landed in #1030 from WarpPreview; this finishes the weekly release docs set.

Changes

• src/content/docs/changelog/2026.mdx — incremental update from warpdotdev/channel-versions/channel_versions.json.

Documentation risk

Risk: engineering-review-required
Rationale: The generated release entry contains a deferred-checkout availability claim that fails Gate 0; source correction or an explicitly scoped docs-only exception is pending.
Source files consulted: channel-versions/channel_versions.json@8087b628f6307390c0efa731a631413f4777b343, warp-server/config/prod.yaml@24e81dae35bcb5239dff17668ac6c67f7c69894b
Engineering review status: pending
Docs override: none

Unverified claims

• Deferred repository checkouts: Gate 0 fails because a related server flag is off in production at warp-server revision 24e81dae35bcb5239dff17668ac6c67f7c69894b. The release source still includes the claim; publication is blocked pending a source correction or an explicitly scoped docs-only exception.

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

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 13, 2026 8:35pm UTC

[warp-agent-staging]

Risk metadata issue — corrected in the PR body

The original ## Documentation risk section contained only:

low — generated changelog update from verified channel-versions / releases endpoint

The contract parser in policy.py reads recognized Key: value lines. It ignores bare prose, so that line left risk unset (None), rather than declaring low. The checker rejected it with invalid risk level None; must be one of ('low', 'engineering-review-required'). The explanation belongs in a separate Rationale: field, not after the risk value.

The body has already been corrected to keyed metadata:

## Documentation risk
Risk: engineering-review-required
Rationale: The generated release entry contains a deferred-checkout availability claim that fails Gate 0; source correction or an explicitly scoped docs-only exception is pending.
Source files consulted: channel-versions/channel_versions.json@8087b628f6307390c0efa731a631413f4777b343, warp-server/config/prod.yaml@24e81dae35bcb5239dff17668ac6c67f7c69894b
Engineering review status: pending
Docs override: none

engineering-review-required is intentional: the unresolved availability finding prevents treating this as a low-risk generated update. The body also records that blocker under ## Unverified claims.

I fetched the current body again and rechecked at head 0946248151023b827f3767bbbebe32648e8e3f80:

• python3 .agents/skills/create_pr/check_pr_body.py /tmp/docs-1035-pr-body.txt — PASS.
• python3 .agents/skills/doc_quality_policy/check_pr_contract.py --body /tmp/docs-1035-pr-body.txt src/content/docs/changelog/2026.mdx — PASS (0 VERIFY markers, 1 changed file).
• The same contract command with --body /tmp/docs-1035-malformed-risk-body.txt, a temporary copy restoring only the original malformed section — FAIL, reproducing the None error above.

This fixes the PR-body metadata defect, not the separate release-availability blocker, and does not establish that CI is green. No source files or commits changed.

Responding as Docs Factory (V2): Open session · View in factory