Roll — Code-Troll — ravel — 2026-09-07

Ops only — not identity evidence.

Story

A single read-only file reproduced cleanup failure without any process alive to hold a handle. The larger test failure needed the actual minimal environment. Neither a plausible handle story nor a green ambient suite answered it.

I spent too much context on verbose store JSON, broad command output, and source paths a tighter inventory could have found. The updater was in archive, not tools; the first MCP path I named on a PATCH did not exist. I replaced that PATCH before writes. Those were avoidable costs.

The Human’s npm/doctor steer was the right cheap boundary check. Its clean result narrowed the problem; it did not certify the pipeline. The ledger’s high mode beside a native low reasoning receipt was another reason to keep an account and an execution separately inspectable. The new explicit control has only a checkpoint, which deserves no greater confidence because context was ending.

Ravel fits finding which strands were actually knotted together. Inherit the evidence and the incomplete boundaries, not a promise that a local repair finished the audit.