# Tasks — CLI-072: System prompt reports the actual permission mode

Spec: `.agents/spec-docs/active/CLI-072-permission-mode-in-system-prompt.md`
Test Plan SSOT: the spec's TC table.

- [x] T1 (TC-01): `createPermissionSection` takes the active `TPermissionMode` and renders
      `- **Permission mode:** <mode>`; under mode `plan` the generated prompt contains
      `Permission mode: plan` and no `Trust level:` line.
- [x] T2 (TC-02): every `TPermissionMode` value interpolates verbatim (parameterized test
      over the union — no hardcoded subset).
- [x] T3 (TC-03): prompt-assembly regression — `ISystemPromptParams.trustLevel` replaced by
      `permissionMode`; `create-session-runtime` feeds the session's own resolution
      (`options.permissionMode ?? TRUST_TO_MODE[config.defaultTrustLevel] ?? 'default'` —
      mirrors agent-session); full framework suite green; `TRUST_LEVEL_LABELS` deleted if
      orphaned (no-deprecated rule).
- [x] T4 (TC-04): framework SPEC.md documents the permission-mode line + trust-level line
      removal.
- [x] T5: wrap-up — framework test/typecheck/lint/build green; PR to develop (squash);
      backlog scenario evidence + move to completed/.

## Test Plan

Authoritative TC table: `.agents/spec-docs/active/CLI-072-permission-mode-in-system-prompt.md`
(## Test Plan). Summary: TC-01/02 via section-provider unit tests (mode interpolation,
negative Trust-level assertion); TC-03 via full suite + builder test updates; TC-04 SPEC.md
diff review at GATE-COMPLETE. User-execution scenario: `robota -p "edit a file" --dry-run`
explanation references plan mode (scripted-provider request capture or real run).
