{{ house_style }}

Review the coding session described below and produce a **PQRST Estimate** of
where effort was spent.

Use these categories:

- **P — Main problem:** implementing or directly solving the requested deliverable.
- **Q — Quality and tests:** tests, verification, edge cases, maintainability,
  error handling, cleanup, and production-quality hardening.
- **R — Research and context clarification:** reading the codebase or docs,
  tracing behavior, investigating unknowns, reconciling requirements, and
  establishing missing context.
- **S — Security and credentials:** authentication, authorization, secrets,
  credentials, trust boundaries, security validation, and security-specific
  handling.
- **T — Task organization:** planning, decomposition, todo management,
  sequencing, coordination, and overhead required to keep the work organized.

Treat this as a **post-session audit, not a planning estimate**. Estimate
relative cognitive/work effort rather than tokens or wall-clock time. The five
percentages **must sum to exactly 100%**.

Where activities overlap, assign effort according to the primary purpose of the
activity. Do not inflate a category merely because it was important; estimate
how much effort it actually consumed.

Session material:

{{ session_summary }}

Return:

```text
P: NN%
Q: NN%
R: NN%
S: NN%
T: NN%
Total: 100%
```

Then provide:

1. **Primary effort driver** — one sentence naming what dominated the session.
2. **Interpretation** — what the distribution says about the session's shape.
3. **Signal** — one notable imbalance, if any, that may be worth learning from.

Include rationale: {{ include_rationale }}