docs(examples): post-v2.11.0 re-probe pass — Redteam

[cdot65]

Summary

Post-v2.11.0 + SDK 0.10.0 re-probe of every Redteam command on the .missing-allowlist. Three commands unblocked (one CLI bug fix + new docs), four remain blocked (commented on tracker issues with retry plans).

Refs: epic #127, area tracker #129.

Landed (3 commands off the allowlist)

• redteam properties add-value — CLI redteam properties add-value sends wrong field names (name/value vs property_name/property_value) #197 fix shipped in v2.11.0 lands at HTTP level, but render was broken (undefined=undefined). Rewired to print MutationResponse.message. Added curated example.
• redteam properties values <name> — SDK 0.10.0 returns {name, values: string[]}, CLI service still expected pre-0.10 {data: [{name,value}]} shape. Rewired service adapter + renderer + types. Added --output json|yaml support. Added 3-format examples.
• redteam properties list --output json|yaml — service was returning pre-0.10 Array<{name}>; SDK now returns plain string[]. Rewired adapter + renderer. Refreshed list example with 3 formats (was empty-state only).

Still blocked (4 commands stayed on allowlist)

• redteam prompt-sets get (all 3 formats) — upstream /version-info returns 500 for every prompt set (redteam prompt-sets get: version-info endpoint returns 500 for every prompt set #117). CLI calls version-info unconditionally after detail fetch, so no format works. Needs upstream fix OR CLI graceful-degradation. Commented on sub-issue docs(redteam): redteam prompt-sets get — root-cause sub-issue #164 with retry date 2026-05-28.
• redteam properties create — NEW failure mode: API returns 201 {data: string[]} but SDK declares BaseResponseSchema = {message, status}; Zod rejects. Not the previous docs(redteam): redteam prompt-sets upload — root-cause sub-issue #168 empty-body issue. Commented on sub-issue docs(redteam): redteam properties create — root-cause sub-issue #172 with retry date 2026-05-28.
• redteam prompts delete — SDK docs(redteam): redteam prompt-sets upload — root-cause sub-issue #168 empty-body Zod validation still active (204 body fails BaseResponseSchema). Commented on docs(redteam): redteam prompt-sets upload — root-cause sub-issue #168.
• redteam targets delete — SDK docs(redteam): redteam prompt-sets upload — root-cause sub-issue #168 same failure. Stranded a throwaway target on the test tenant during probe; documented in docs(redteam): redteam targets delete — root-cause sub-issue #177. Commented on docs(redteam): redteam prompt-sets upload — root-cause sub-issue #168.

Still blocked (untouched in this pass)

• redteam instances create/get/update/delete, redteam devices create/update/delete — single probe confirmed API still returns 403 (redteam: live docs capture blocked for instances/devices CRUD (API 403 — distinct from license issue) #124). No retry attempted; same state as before.

Test plan

• pnpm tsc --noEmit clean
• pnpm lint clean (0 errors; 10 pre-existing warnings)
• pnpm test — 714/714 pass
• pnpm docs:gen regenerated docs/cli/redteam/properties.md
• pnpm docs:check — 123 commands, 28 on allowlist (was 32)
• pnpm docs:build clean
• CI green on this PR