A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0303
Prove a silent provider produces an explicit absence, never a guess
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
2- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0302 | I0302 is not DONE |
| milestone | execution-telemetry | the milestone execution-telemetry waits on an outcome of its own |
Moves
plan.transitionWhat it is
- 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.
- Now
- The recording path exists. What happens when nobody reports anything is untested.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- 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.
Acceptance
- 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 present
- unknown: the record carries no `evidence` entries
Scope
- Touches
test/cases- Not
Any change to the recording path; if the case fails, the fix belongs to the issue that owns that code- Depends on
- Priority
- p2
- Profile
- debugging
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.