Get dilution coverage status

Whether Signal8 holds a dilution snapshot for this company, how fresh it is, and — when there is none — why. Cheap enough to poll before spending credits on `/snapshot`, `/instruments` or `/history`. `status` is the customer-facing verdict: - `verified` — a current snapshot exists - `stale` — a snapshot exists but is older than the freshness window, OR a material filing / a delisting form has been filed since it (see `statusDetail`) - `not_covered` — no snapshot is being served for this ticker `statusDetail` (added 2026-10-11) refines it without changing the three `status` values: `verified` | `stale` | `newer_filing_unread` (a material filing — new or amended instrument, 424B5/B4/B1 pricing, split, 10-K — routed after the snapshot that it did not read, with no refresh job in flight) | `delisting_filed` (a Form 25 / 25-NSE / 15-12B / 15-12G / 15-15D filed after the snapshot) | `not_covered`. `unreadFilings` / `delistingFiled` name those filings. A null `unreadFilings` means NOT MEASURED, never "nothing unread". `lastSuccessAt` for a snapshot copied between environments is the snapshot's own generation time, not the copy time. `extraction` is the pipeline state behind that verdict (`never_extracted` | `running` | `failed` | `timeout` | `complete`). 🔴 `not_covered` means NOBODY HAS READ THIS COMPANY'S FILINGS. It is not a statement that the company has no dilution, and must not be rendered as one. `outOfScope: true` is a PRODUCT-SHAPE fact, not a suppression: dilution coverage is a small-cap product, and large caps are outside it. A null market cap is NOT out of scope.