You can now see what each Jira Epic delivered beside what that work was meant to change, in one read-only view. Ask for a project's Epics and their outcomes: the view groups the project's work by Epic, counts delivery from the flow-metrics skill's own per-issue rows, and renders each Epic's recorded outcome next to it. It writes nothing to Jira and leaves no file behind.
An Epic with no recorded outcome says so, and asks you for one. Instead of a blank row, the view states plainly that nothing is recorded and names the one place to write it — the block under an Outcome heading in the Epic's description. Hand your answer back with --outcome EPIC-KEY=<text> and your exact words come back as text you paste into Jira yourself, so the outcome stays something your team said.
A `flow-metrics` run can now touch the on-disk cache not at all. The new --inert-cache mode performs no cache read, write, directory creation or stale-temporary-file cleanup, which --no-cache still did. It is off by default, so every existing flow-metrics run behaves exactly as before.