Repository navigation
t27b ledger: the last 5 pass_vacuous rows are stubs with nothing to assert #8766
Description
Part of epic #8326 (coverage, see #6063). Each of the last five pass_vacuous rows in docs/reports/t27b_expectations.json was checked, and none has anything a real test could assert. Writing tests for them would mean restating constants, which the vacuous lane rules out. The rows stay pass_vacuous until each spec gets content or is deleted.
| spec | what it holds | why no test |
|---|---|---|
specs/lsp/language.t27 |
a TODO stub with an empty main() |
#8539 removed its assert true: "a stub with nothing assertable is out of scope, not a fake test" |
specs/tri/utils/string.t27 |
a module line and two use lines |
#8054 kept it because open issues name it (see #8013), but none says what it should contain |
specs/tri/utils/error.t27 |
a broken type skeleton, struct { enum : , } |
no fields or functions, and the "exit code 1-9" rule it promises has no source in the repo |
specs/sandbox/modules.t27 |
only use sandbox.session_timeout; |
that module has its own tests |
specs/physics/lqg_entropy.t27 |
documentation; its tests are then true / assert true |
every quantity it names (phi^-3, d_tau = phi, the Immirzi gamma) is defined and tested in specs/physics/lqg_cs_bridge.t27 |
Options, for each spec:
- write its real content, then test it;
- delete it, as t27b vacuous: delete 22 empty generated spec stubs (Closes #8052) #8054 deleted 22 empty stubs;
- move the documentation to docs/.
User Scenarios
- Given the t27b ledger reports five specs as
pass_vacuousbecause they are empty stubs, When an agent resolves each spec by implementing testable content, deleting it, or moving its documentation todocs/, Then the ledger no longer lists those specs aspass_vacuous.
Requirements
FR-001: Each of the five cited specs MUST be resolved by implementing real testable content, deleting the spec file, or moving documentation to docs/.
FR-002: The docs/reports/t27b_expectations.json file MUST be updated to reflect the resolution of each spec.
FR-003: No spec MUST remain pass_vacuous due to being an empty stub with nothing to assert.
Success Criteria
t27c --ledger specs/runs and shows 0pass_vacuousrows for the five cited specs (exit 0)- The five cited spec files are either deleted, contain testable content, or have documentation moved to
docs/ docs/reports/t27b_expectations.jsonno longer lists the five specs aspass_vacuous
Boundary
- specs/lsp/language.t27
- specs/tri/utils/string.t27
- specs/tri/utils/error.t27
- specs/sandbox/modules.t27
- specs/physics/lqg_entropy.t27
- docs/reports/t27b_expectations.json
- docs/
Activity
t27b ledger: delete the five vacuous stubs -- lsp/language, tri/utils…
gHashTag commentedon Oct 11, 2026
Outcome: all five stubs are deleted, by #8912 (issue #8908), merged as d910aa5.
git grepfound nouseof any of the five modules, so none needed real content.pass_vacuousrow.sandbox.modulesdep.On the t27c lab, the t27b corpus before and after: pass_vacuous 6 -> 1. The one left, specs/tri/agent/eternal_monitor.t27, has no ledger row, because the reference does not pass it.