Why this follow-up exists
The lifecycle corpus marked three web cycles as misses. That could mean an unstable page, an unavailable backend, a harness false negative, or model-level recovery behavior.
Root cause
Bunsen’s lifecycle profile enables the search-only DDGS backend. It does not support extraction. Direct invocation of web_extract therefore returns the same capability error every time.
The five lifecycle web cycles all encountered that missing capability. The model recovered through web_search in two cycles and returned the configuration error in three. The lifecycle harness correctly marked the three response bodies that lacked Example Domain.
Ten-run replay
Ten isolated requests asked for the title of example.com while explicitly naming web_extract.
- Process exit: 10/10 rc=0.
- Requested title present: 9/10.
- Distinct response bodies: 4.
- One response returned the unavailable-backend explanation without the title.
This measures fallback behavior around a deterministic capability gap. It does not establish that extraction is available.
Promotion boundary
Before using extraction in a release gate, choose one explicit contract: hide unsupported web_extract, install an extract-capable backend, or change this workload to web_search. Do not let model improvisation decide whether the gate passes.
Falsifier
Overturn this classification if a direct tool-only probe succeeds with DDGS alone, or if a configured extract-capable backend still reproduces the same deterministic capability error.