(OPT) Make bounded ASCII captures useful for complete applications under ordinary fuel #706

The current-source LogLens campaign required repeated handwritten byte parsing and three SEMAPRAX candidates failed the literal-plus timezone boundary. The private ASCII-pattern engine now has four focused source/backend witnesses and an independent oracle, but has no public package admission or demonstrated long-input/default-fuel usefulness.

In one larger implementation batch, adapt and optimize the bounded source engine and package-facing API, then exercise the unchanged 49 LogLens obligations plus independent header/KV captures, long valid and nonmatching records, hostile repeats, exact work/fuel boundaries, malformed packets, and interpreter/native/Wasm settlement. Keep literal plus/minus semantics and refusal status distinct; do not raise fuel, weaken limits, or claim performance gains from small witnesses. Add agent-facing usage only after the API is supported.

Base: main ac3f3bf. Current experiment and focused receipt: experiments/ascii-pattern-source; benchmarks/opt-batch-verification-v1/opt702-704-minimal-verification.json.