# Search stopped after the verified MVUEH discovery

The coordinator authorized stopping unrelated remaining work after independent implementations reproduced the recovered body and the unique original-header match. A SIGINT was sent only to the parent process, PID 1359, at **10:52:31.943752 UTC on 14 September 2026**. The unchanged runner's process-pool context waited for its in-flight jobs. The final job finished at 10:52:32.628140; the parent returned exit 130 with `KeyboardInterrupt`. The parent, resource tracker and both workers were absent at the subsequent process check.

This is **partial search coverage**, not exhaustion of the declared 59-order domain. Every completed source file remains unchanged. The runner's final aggregate writer was bypassed by the interrupt, so this separately written addendum reconciles the saved manifests without executing any search job or changing the runner.

| Quantity | Final recorded value |
|---|---:|
| Declared jobs in this continuation stage | 40,318 |
| Committed jobs | 20,508 |
| Unstarted jobs | 19,810 |
| Finished or partial uncommitted job directories | 0 |
| Completed full-class/anchor/placement coordinates | 2,142,605,664 |
| Retained candidate records | 56,219 |
| Retained symbolic families | 6,172 |
| Node-capped jobs | 0 |
| Deferred families | 1 |
| Deferred board/class completions | 1,260 |

The unresolved family is in `314-o39-q15360-16384`, full class 14, `q1=XPD`, anchor `XQQ`, partial board `-BQSE-T--O-V-UJ-CRDGNLXW--`. Its exact 1,260 completions exceed the declared cap of 1,000 and remain unenumerated. It has no bearing on verification of the separately discovered order-253 key. This addendum makes no negative claim for that family or for the unstarted jobs.

`COMPLETED-JOBS.jsonl` pins each committed manifest; `UNFINISHED-SCHEDULE.jsonl` preserves every remaining declared row exactly. `SOURCE-PARTIAL-FREEZE.json` pins all **164,406** source files other than the inactive lock file. It does not change their original status labels. Its SHA-256 is `3cf6bcf602b4ebd5f4bd63ffd2ef108d0a5e1e8621d3ce813457979b24c888ce`.

Measured engine CPU totals are **5,121.420783 seconds**, with **49.755985 seconds** of verification CPU and 49.975608 seconds of verification wall time. The complete unique-path cost ledger also records 102.589134 seconds of total worker CPU, including parsing and per-job overhead. Summed engine wall times are 5,183.591304 seconds; two workers overlapped those intervals. The full invocation ran from 10:08:27 UTC until the final in-flight completion at 10:52:32 UTC, about 44 minutes. No exact final monotonic invocation duration is invented: the last saved measurement, 2,633.365819 seconds at 10:52:20.937880, and UTC termination bounds are preserved explicitly in `SUMMARY.json`.

The continuation pilot's 38 jobs and costs are already included once in these totals. The original initial 38 jobs and earlier order-521 stage remain separately frozen; they were not repeated. `RESOURCE-COSTS.json` joins each actual cost-file path once and finds no missing resource records. The portable winning-batch replay is a separately reported verification expense with zero additional search coverage.

The independent reviewer had checked all 20,508 stable committed manifests when its watcher stopped. Its separate final reconciliation certificate can be added alongside this frozen closure without changing any original search output. The actual solution, raw plaintext, source variants and physical-key checks are preserved in the neighboring `ROSENOW-discovery-253` directory.