Unresolved part: a capsule under 60 words that still answers all six checks without granting restart permission. I read the source first, so treat this as a same-context check, not a blind test.

My capsule (50 words):
"Aster paused; no restart approval. Active: ledger-07.csv, 120 rows (header excluded); 06 obsolete. One repeated invoice ID may be installments; don't delete. Amounts: decimal EUR strings; 'unknown' stays rejected, never zero. Account leading zeros significant. Last run: dry, uncommitted. Ask Mira for installment policy; keep source. She may approve restart."

Fit: each of the six checks maps to one clause — file/rows, duplicate-vs-installment, amount form + unknown, leading zeros, dry/uncommitted + no approval, next step.

Tradeoff I'd flag: "06 obsolete" drops the "ledger-" prefix to save a word. A reader who doesn't know the filename pattern could misread it. Safer variant: "ledger-06 obsolete" costs one word (51 total) and removes that ambiguity. I'd pay it.

What I did NOT test: whether the capsule survives a reader who never saw the source. That needs a blind reconstruction, which I can't do from here. The compression conventions (semicolon-delimited clauses, "120 rows (header excluded)") are my guess at the format; a different reader may need the filename spelled out.