Declare the smoke driver as not part of the default suite

Message

test/smoke-driver.sgl is a real test file, with two test-groups, that runs only against a provisioned enclave-server with bot tokens in the environment. It is invoked explicitly, never by a bare sigil test.

sigil 0.21.0 makes sigil test --strict the default, and it fails the run when a .sgl file in test/ registers tests and discovery did not select it, on the reasoning that such a file has never run and nothing said so. That is the right question to ask; for this file the answer is that it is deliberately outside the suite, and .testignore is where that gets said.

Verified control first against 0.21.0: without this file the run exits 1 and names test/smoke-driver.sgl. With it, strict inspects 1 unselected file, classifies 0 as test-like, and stands down.

The ignore removes nothing real. With and without it, --no-strict gives byte-identical results: Files: 3 of 3 run, Tests: 135 passed, 1 failed.

That one failure is PRE-EXISTING and unrelated to this commit (test-enclave > bounded connect > a blackholed endpoint fails WITHIN the bound). It is present on master before this change and is reported separately, not fixed here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PjGdGaMFAoRxUYgBufZ22U

Changed

 .testignore | 10 ++++++++++
 1 file changed, 10 insertions(+)

Diff

.testignoreadded

@@ -0,0 +1,10 @@

# Files in test/ that are NOT part of the default suite.

#

# `sigil test` (0.21.0+) fails when a .sgl file in test/ registers tests and

# discovery did not select it, on the reasoning that such a file has never run

# and nothing said so. These are the deliberate exceptions.

# End-to-end smoke driver. Runs only against a provisioned enclave-server with

# bot tokens in the environment; see the header of the file and test/smoke.sh.

# Invoked explicitly: sigil test test/smoke-driver.sgl

+10

test/smoke-driver.sgl