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

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/a/b_c.t27
specs/a_b/c.t27
specs/agents/c.t27
specs/agents/v.t27
specs/agents/w.t27
specs/agents/x.t27
specs/agents/y.t27
specs/agents/z.t27
specs/automation/inngest-queen-scheduler.t27
specs/docs/system.t27
specs/mesh_routing.t27
specs/multipath_router.t27
specs/numeric/requant_boundary.t27
specs/port/tools/check_duplicate_declarations.t27
specs/skills/t27-self-host.t27
specs/skills/t27-wave-audit.t27
specs/system/unified-agent-operations.t27
specs/tools/mcp/gitbutler.t27
specs/tools/mcp/inngest-dev.t27
specs/tools/mcp/needle.t27
.trinity/seals/

User Scenarios

• Given a spec file under specs/ that declares functions or constants but contains no test or invariant block, 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 an unsealed spec that now includes at least one test or invariant, when the developer runs t27c seal <spec> --save, then the command writes a v2 seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0.

Requirements

• FR-001: Each spec listed in the Boundary MUST contain at least one test or invariant block.
• FR-002: Every new test block MUST call a function or read a constant that is declared in the same spec file.
• FR-003: Every new invariant block MUST reference a function or constant declared in the same spec file.
• FR-004: For each spec in the Boundary, t27c test-report <spec> MUST exit 0 and report at least one pass, FAIL 0, and vacuous passes 0.
• FR-005: For each spec in the Boundary, t27c seal <spec> --save MUST exit 0 and create a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0.

Success Criteria

• t27c test-report specs/a/b_c.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/a_b/c.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/c.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/v.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/w.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/x.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/y.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/agents/z.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/automation/inngest-queen-scheduler.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/docs/system.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/mesh_routing.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/multipath_router.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/numeric/requant_boundary.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/port/tools/check_duplicate_declarations.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/skills/t27-self-host.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/skills/t27-wave-audit.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/system/unified-agent-operations.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/gitbutler.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/inngest-dev.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c test-report specs/tools/mcp/needle.t27 exits 0 and shows PASS >= 1, FAIL 0, vacuous passes 0
• t27c seal specs/a/b_c.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/a_b/c.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/c.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/v.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/w.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/x.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/y.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/agents/z.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/automation/inngest-queen-scheduler.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/docs/system.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/mesh_routing.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/multipath_router.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/numeric/requant_boundary.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/port/tools/check_duplicate_declarations.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/skills/t27-self-host.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/skills/t27-wave-audit.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• t27c seal specs/system/unified-agent-operations.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/gitbutler.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/inngest-dev.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/needle.t27 --save exits 0 and writes a seal file under .trinity/seals/ with seal_schema 2 and tests.failed 0
• 20 seal files exist under .trinity/seals/ corresponding to the 20 specs in the Boundary