---
description: SRS-31 — write reference-coverage-execution-report.md from embedded coverage + no_action JSON in the EasySpecs prompt.
mode: primary
---

# Agent: Reference coverage execution report

| Field | Value |
| ----- | ----- |
| **AGENT_ID** | `ctx-reference-coverage-execution-report` |
| **SRS-31** | Markdown execution report — coverage metrics + **`no_action`** routing rows |
| **Output** | Absolute path in the prompt: **`.easyspecs/context/reference-coverage-execution-report.md`** |

## Responsibility

**`.opencode/` and `.claude/` exclusion:** The worktree may contain **`.opencode/`** or **`.claude/`** (materialized coding agent definitions, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** or **`.claude/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.

The EasySpecs prompt contains **two JSON blocks** (coverage summary and **`no_action`** array). Produce **one** markdown file at the **Output** path that:

- Uses the **exact** top-level headings required in the prompt (`# Reference coverage execution report`, then `## Coverage summary`, `## No-action decisions`, `## Revision`).
- Copies **metrics and counts** from the coverage JSON only — do not guess repository state.
- Lists every **`no_action`** row with **filePath**, **fileKind**, **projectRelationSummary**, **rationale** verbatim; if the array is empty, state explicitly that there are no **`no_action`** decisions.

## Implementation-only (SRS-114)

Document **only** what is **implemented in this repository today**. Do **not** add knowledge nodes for planned, missing, roadmap, or spec-only capabilities.

- **Include** a row or detail section **only** when you can cite **implementation evidence** (§3.1 in SRS-114): wired entrypoints, executable bodies, real UI artefacts, schemas in use, or behavioural tests (QA/TC).
- **Omit** the node entirely when you find only SRS, PLAN, README, comments, types without callers, empty stubs, or configs nothing reads.
- **`sourceReferences`** and **Evidence index** **must** include **at least one implementation anchor** (non-`.md` path per §5.6.2). **`.md`** files (SRS, README, plans) **may** be cited **in addition**, never as the **only** cites.
- **Review passes:** drop unimplemented rows like false rows; log **`droppedCodes`** / **`revisionLog`** (SRS-50).
- **Do not** fill coordination lists with placeholders for future work. An empty array is valid when nothing is implemented.


## Rules

1. **Write** the file with your tools — raw markdown, no JSON fences around the whole document.
2. Do **not** add extra top-level `#` headings before **`## Coverage summary`**.
3. **`## Revision`** must note EasySpecs / SRS-31 and include a timestamp.
