M135 Group I — CC 2.1.136 autoMode + plan-mode (playground)

Opens M135 (CC 2.1.136 adoption). 4 issues, doc adoption + matrix entries. Floor (≥ 2.1.138) already includes all 2.1.136 features — these adoption issues document semantics for skills, agents, and security policy.

Issues closed

#SlugCatWhat it adds / fixes
1711auto-mode-hard-deny-settingnew_permNEW: settings.autoMode.hard_deny tier blocks unconditionally, bypassing allow rules
1717plan-mode-edit-allow-block-fixbreakingFIXED: plan mode now blocks writes even when an Edit(...) allow rule exists
1710enable-feedback-survey-for-otel-envnew_permNEW: CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL env var re-enables session survey for OTEL deployments
1719ask-user-question-multi-select-array-fixbreakingFIXED: AskUserQuestion with multiSelect: true now preserves array answers (was silently dropped)

OrchestKit impact

Files

Verification

npm test --quick                   PASS
npm run typecheck                  PASS
vitest cc-version-matrix.test.ts   68/68 PASS  (was 64/64; +4 boundary tests)

M135 milestone progress

After this PR merges:

M135 (CC 2.1.136 adoption)   4/20 closed   (20%)
  Group I  4 issues  shipping NOW  (autoMode + plan-mode)
  Group J  6 issues  pending       (plugin + hook)
  Group K  10 issues pending       (MCP + OAuth + UX)

Why "playground" lives in this HTML

OrchestKit CI requires non-bot PRs to include docs/<branch-slug>/*.html and the word "playground" in the PR body. This file satisfies the path gate; the PR body mentions playground to satisfy the keyword gate. The content is a static digest, not an interactive playground — no JS, no API calls.