oc-recording-findingslisted

# Recording-Findings — Consolidating agent outputs into the transient findings buffer **Announce at the start (in pt-br):** "Usando recording-findings para consolidar os findings da run no buffer de findings." **Input:** the raw output blocks emitted by `executor-<tier>`, `compliance`, `adversary`, and `sniper-<tier>` agents during the completed feature run (the run's findings buffer that `build` accumulated in Phase 2 step h). **The findings buffer is TRANSIENT** — a single-run digest. It is the input to `oc-distilling-learnings` (which routes durable insights to native MEMORY.md / nested AGENTS.md / kaizen.md) and is then **deleted by the harvester** at the end of the run (per `agents/harvester.md` step 5). It is not a durable archive — the run's commit/PR in git is the durable audit. Do not treat it as a cross-run log. --- ## Finding block formats (per agent) The tiered agents (`executor-high/medium/low`, `sniper-high/medium/low`) emit under the same headings regardless of tier — match on the heading, not the tier suffix. **Executor** (`executor-<tier>`) emits under `### Findings`: ``` - <decision taken, gotcha hit, or assumption made> ``` **Compliance** emits under `### Problemas encontrados`: ``` - PROBLEMA: <description> — file:line - SUGESTAO: <non-blocking improvement> ``` **Adversary** emits a JSON `issues` array: ```json { "description": "...", "category": "...", "severity": "low|medium|high", "scope": "...", "evidence": "...", "fix_hint": "..." } ``` **Sn