# Sprint 136 Plan: Capability and Permission Gate Unification for MCP Tools

## Context

Tool reachability must also respect deterministic capability and permission gates.
Sprint 136 unifies policy enforcement across MCP registration and execution.

---

## Goals

1. Model tool capability/permission requirements uniformly
2. Enforce deterministic permission checks at execution boundaries
3. Detect missing or inconsistent policy bindings
4. Export policy conformance diagnostics for release gating

---

## Steps

### Step 1599: Tool capability requirement schema (10 tests)
### Step 1600: Permission policy binding model (10 tests)
### Step 1601: Execution-time permission evaluator integration (10 tests)
### Step 1602: Policy gap detector (`missing`, `inconsistent`, `orphaned`) (10 tests)
### Step 1603: `whetstone_get_tool_permissions` MCP tool (8 tests)
### Step 1604: `whetstone_validate_tool_permissions` MCP tool (8 tests)
### Step 1605: Permission gate strictness policy model (8 tests)
### Step 1606: Permission decision packet model (8 tests)
### Step 1607: Permission conformance report artifact (8 tests)
### Step 1608: Sprint 136 integration summary + regression (8 tests)

---

## Architecture Gate

- Permission decisions must be deterministic and auditable
- Missing policy bindings must be hard-fail under strict mode
- Decision packets must include explicit rule provenance
- Max 600 lines per header