Unsealed specs, no test or invariant (L4): batch 2 of 2 (20 specs) #8414

Part of #8393 (epic #8095). These specs declare code but hold no test, invariant or bench, so nothing checks them and checks_pass refuses their seal (#8374). Without a seal, t27c frontier can never reuse their verdict.

Attribute an error to the file it is in: an identifier that comes from an import is fixed in the import or the imported spec.

Acceptance criteria

• Every spec under Boundary holds at least one test or invariant, and each new test calls a function or reads a constant that its own spec declares.
• t27c test-report <spec> reports at least one pass, FAIL 0 and vacuous passes 0 for every spec under Boundary.
• Every spec under Boundary has a v2 seal written by t27c seal <spec> --save with seal_schema 2 and tests.failed 0.

Boundary

specs/tools/mcp/neon.t27
specs/tools/mcp/notebooklm.t27
specs/tools/mcp/railway-mcp-server.t27
specs/tools/mcp/t27-traceability.t27
specs/tools/trinity/tri/mesh.t27
specs/tools/trinity/tri/needle-check.t27
specs/tools/trinity/tri/needle-search.t27
specs/tools/trinity/tri/needle.t27
specs/tools/trinity/tri/omega.t27
specs/tools/trinity/tri/particles.t27
specs/tools/trinity/tri/phi.t27
specs/traffic_animator.t27
specs/tri/math/math.t27
specs/tri/math/measurement.t27
specs/tri/pipeline/spec_writer.t27
specs/tri/utils/error.t27
specs/tri/utils/string.t27
specs/lsp/language.t27
specs/numeric/formats_catalog.t27
specs/tri/agent/faculty_board.t27
.trinity/seals/

User Scenarios

• Given a spec file from the Boundary list that declares functions or constants but contains no test or invariant blocks, When a developer runs t27c test-report <spec>, Then the tool reports FAIL 0 and vacuous passes 0 with at least one passing test.
• Given all 20 specs in the Boundary have been augmented with at least one test or invariant that exercises their own declarations, When the developer runs t27c seal <spec> --save for each, Then every spec receives a v2 seal with seal_schema 2 and tests.failed 0.

Requirements

FR-001: Each spec under Boundary MUST contain at least one test or invariant block.
FR-002: Every new test or invariant in a spec MUST call a function or read a constant declared in that same spec.
FR-003: For every spec under Boundary, t27c test-report <spec> MUST report at least one pass, FAIL 0, and vacuous passes 0.
FR-004: For every spec under Boundary, t27c seal <spec> --save MUST write a v2 seal file with seal_schema 2 and tests.failed 0.

Success Criteria

• t27c test-report specs/tools/mcp/neon.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/notebooklm.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/railway-mcp-server.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/t27-traceability.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/mesh.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/needle-check.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/needle-search.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/needle.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/omega.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/particles.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/trinity/tri/phi.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/traffic_animator.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/math/math.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/math/measurement.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/pipeline/spec_writer.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/utils/error.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/utils/string.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/lsp/language.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/numeric/formats_catalog.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c test-report specs/tri/agent/faculty_board.t27 exits 0 and outputs at least one pass, FAIL 0, vacuous passes 0
• t27c seal specs/tools/mcp/neon.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/mcp/notebooklm.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/mcp/railway-mcp-server.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/mcp/t27-traceability.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/mesh.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/needle-check.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/needle-search.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/needle.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/omega.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/particles.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tools/trinity/tri/phi.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/traffic_animator.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/math/math.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/math/measurement.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/pipeline/spec_writer.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/utils/error.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/utils/string.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/lsp/language.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/numeric/formats_catalog.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/tri/agent/faculty_board.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0