Skip to content

I0303 — Prove a silent provider produces an explicit absence, never a guess

Write the case that runs a whole task under a provider that reports nothing and asserts that the completed record carries an explicit absence with a reason, and that no field anywhere in the surfaces shows an estimated number.

BLOCKED wave 2 · p2 · debugging profile · runs alone

Part of execution-telemetry — Execution telemetry, only from providers that expose it honestly.

Blocked. This issue cannot start until I0302, milestone:execution-telemetry are done. The status is derived from that, not declared.

Objective

Write the case that runs a whole task under a provider that reports nothing and asserts that the completed record carries an explicit absence with a reason, and that no field anywhere in the surfaces shows an estimated number.

Why

The failure this milestone exists to avoid is not a missing feature, it is a plausible number nobody measured. Only a case that looks for the absence can keep that from creeping back in through a convenience default.

Current state

The recording path exists. What happens when nobody reports anything is untested.

Desired state

A case demonstrates the silent path end to end, and a grep-like assertion over the reporting surfaces shows no estimated value is ever printed as measured.

Scope

  • test/cases

Out of scope

  • Any change to the recording path; if the case fails, the fix belongs to the issue that owns that code

Dependencies

What waits on this

Acceptance criteria

  • The case runs start to finish with no telemetry reported and reaches a completed outcome
  • The stored record carries not_reported with a reason naming the provider
  • No surface prints a number for a task that reported none

Validation

  • bash test/run.sh

Evidence required

  • absence_proved

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

A case that only checks the stored file misses a surface that fills a gap on its way to the screen; it has to assert on what is printed as well.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0303.yaml. Read it back with majordomus plan show I0303.