ctrlrelay 0.12.0__tar.gz → 0.12.1__tar.gz

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/.github/workflows/test.yml

@@ -37,9 +37,4 @@ jobs:
         run: uv run ruff check src/ tests/
 
       - name: Pytest
-        # Deselect the pre-existing unrelated docs-site test that asserts
-        # nav_order uniqueness across docs/ — tracked separately and
-        # unchanged by this PR.
-        run: |
-          uv run pytest tests/ -v \
-            --deselect tests/test_docs_site.py::test_nav_order_unique_per_sibling_group
+        run: uv run pytest tests/ -v

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.12.1] - 2026-10-06
+
+### Fixed
+
+- Every checkpoint snippet creates its own directory (#190)
+- Restate the checkpoint contract when resuming (#188)
+- Run the whole suite, and make the next exclusion defendable (#186)
+
+### Changed
+
+- Both-transports-at-once is not planned, not pending (#187)
+
 ## [0.12.0] - 2026-10-06
 
 ### Added
@@ -1671,7 +1683,8 @@ pipeline).
   per-phase implementation plans (Phase 0 through Phase 4).
 - `docs/Claude_Code_Project_Guide.md` — project development guide.
 
-[Unreleased]: https://github.com/AInvirion/ctrlrelay/compare/v0.12.0...HEAD
+[Unreleased]: https://github.com/AInvirion/ctrlrelay/compare/v0.12.1...HEAD
+[0.12.1]: https://github.com/AInvirion/ctrlrelay/compare/v0.12.0...v0.12.1
 [0.12.0]: https://github.com/AInvirion/ctrlrelay/compare/v0.11.3...v0.12.0
 [0.11.3]: https://github.com/AInvirion/ctrlrelay/compare/v0.11.2...v0.11.3
 [0.11.2]: https://github.com/AInvirion/ctrlrelay/compare/v0.11.1...v0.11.2

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ctrlrelay
-Version: 0.12.0
+Version: 0.12.1
 Summary: Local-first orchestrator for headless coding agents across multiple GitHub repos
 Project-URL: Homepage, https://github.com/AInvirion/ctrlrelay
 Project-URL: Documentation, https://ainvirion.github.io/ctrlrelay/
@@ -97,9 +97,9 @@ are on the roadmap (see [Roadmap](#roadmap)).
   relays it to you and resumes the session once you reply. Choose
   **Telegram** (a DM from a bot) or **Mattermost** (a channel on your own
   server) with one `transport.type` setting. Exactly one is active at a
-  time; running both at once is not supported yet
-  ([#176](https://github.com/AInvirion/ctrlrelay/issues/176)). See
-  [configuration][docs-config].
+  time; running both at once is not supported and not planned
+  ([#176](https://github.com/AInvirion/ctrlrelay/issues/176), closed
+  won't-do). See [configuration][docs-config].
 - **PR watcher.** Tracks the opened PR to merge and closes the loop
   with a notification on whichever chat transport is configured.
 - **In-process scheduler** (APScheduler). Runs periodic jobs inside

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/README.md

@@ -56,9 +56,9 @@ are on the roadmap (see [Roadmap](#roadmap)).
   relays it to you and resumes the session once you reply. Choose
   **Telegram** (a DM from a bot) or **Mattermost** (a channel on your own
   server) with one `transport.type` setting. Exactly one is active at a
-  time; running both at once is not supported yet
-  ([#176](https://github.com/AInvirion/ctrlrelay/issues/176)). See
-  [configuration][docs-config].
+  time; running both at once is not supported and not planned
+  ([#176](https://github.com/AInvirion/ctrlrelay/issues/176), closed
+  won't-do). See [configuration][docs-config].
 - **PR watcher.** Tracks the opened PR to merge and closes the loop
   with a notification on whichever chat transport is configured.
 - **In-process scheduler** (APScheduler). Runs periodic jobs inside

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/config/orchestrator.yaml.example

@@ -34,7 +34,7 @@ agent:
 # EXACTLY ONE transport is active, and it is the one named by `type`.
 # The other blocks below are inert: they may stay in the file, but nothing
 # reads them. Running Telegram and Mattermost at the same time is NOT
-# supported - that is tracked as issue #176.
+# supported and NOT planned - designed in issue #176 and closed won't-do.
 #
 # Choose:
 #   type: "telegram"    production, 1:1 chat with a bot

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/docs/bridge.md

@@ -22,9 +22,11 @@ one-line config change and no pipeline code moves.
 **One at a time.** `transport.type` names the transport that is active, and the
 other block is inert — it may stay in the file, but nothing reads it, including
 its `question_ttl_seconds`. There is no fallback: a question goes to the one
-you named or nowhere. Running both at once is
-[issue #176](https://github.com/AInvirion/ctrlrelay/issues/176) and is not
-built.
+you named or nowhere. Running both at once is **not supported and not
+planned** — it was designed in
+[#176](https://github.com/AInvirion/ctrlrelay/issues/176) and closed
+won't-do. Reopen that issue rather than re-deriving the design if you need
+it.
 
 | | Telegram | Mattermost |
 |---|---|---|

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/docs/configuration.md

@@ -104,10 +104,11 @@ block in the file is inert — it may stay there, but nothing reads it.
 | A channel on your own server | `"mattermost"` | A server URL, a bot token, and the channel's 26-character ID. |
 | No chat at all | `"file_mock"` | Nothing. Questions go to a file; **nobody is asked anything.** |
 
-**Running Telegram and Mattermost at the same time is not supported.** Setting
-`type` to one does not fall back to the other, and a question is delivered to
-one place or not at all. That is tracked as
-[issue #176](https://github.com/AInvirion/ctrlrelay/issues/176).
+**Running Telegram and Mattermost at the same time is not supported, and is
+not planned.** Setting `type` to one does not fall back to the other, and a
+question is delivered to one place or not at all. It was designed in
+[#176](https://github.com/AInvirion/ctrlrelay/issues/176) and closed won't-do;
+the design is still in that issue if anyone wants it.
 
 Switching is a two-line change — set `type`, add that transport's block — plus
 a restart of **both** daemons, which share `state.db`.

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ctrlrelay"
-version = "0.12.0"
+version = "0.12.1"
 description = "Local-first orchestrator for headless coding agents across multiple GitHub repos"
 readme = "README.md"
 requires-python = ">=3.12"

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/src/ctrlrelay/pipelines/dev.py

@@ -318,7 +318,20 @@ class DevPipeline:
 
     async def resume(self, ctx: PipelineContext, answer: str) -> PipelineResult:
         """Resume blocked dev session with user answer."""
-        prompt = f"User answered: {answer}\n\nContinue from where you left off."
+        # The checkpoint contract is restated here, not just in the
+        # initial prompt (#173). A resumed agent that is told "continue"
+        # and nothing else can do its work, exit 0, write no state, and
+        # be indistinguishable from one that crashed - which is what
+        # happened on 2026-09-16, after three of four pull requests had
+        # already been merged.
+        contract = self._checkpoint_contract(
+            str(ctx.state_file), ctx.session_id
+        )
+        prompt = (
+            f"User answered: {answer}\n\n"
+            "Continue from where you left off.\n\n"
+            f"{contract}"
+        )
 
         # Resume uses Claude's own session UUID (captured on the first spawn
         # and persisted to state_db). Passing our composite id here makes
@@ -444,7 +457,34 @@ Do NOT merge the PR - wait for human review.
 The orchestrator re-verifies CI and mergeability after you hand off; if it
 finds the PR broken it will resume this session asking you to fix it.
 
-## Signaling Completion
+{self._checkpoint_contract(state_file_path, session_id)}"""
+
+    def _checkpoint_contract(
+        self, state_file_path: str, session_id: str
+    ) -> str:
+        """How the agent signals how it stopped.
+
+        Extracted so the RESUME prompt can carry it too (#173). The
+        initial prompt spent ~30 lines establishing this; the resume
+        prompt was 58 characters and said only "continue", so a resumed
+        agent could do its work, exit 0, write no state, and be
+        indistinguishable from one that crashed.
+
+        Measured case, 2026-09-16:
+        secops-AInvirion-Product-Telemetry-bbb99925 resumed after an
+        "Approved", ran 27.4s, exited 0 and wrote no checkpoint - having
+        in fact merged three of four pull requests. The operator was told
+        the resume failed, which was wrong in both directions: most of
+        the work had landed, and the one thing outstanding was never
+        named.
+
+        Per-pipeline rather than shared, because the three contracts
+        differ in substance and not only wording: the dev DONE block
+        carries pr_url and pr_number outputs, and each names different
+        conditions for DONE. One shared block would have quietly changed
+        what two of them promise.
+        """
+        return f"""## Signaling Completion
 
 **CRITICAL**: Before exiting, you MUST write a checkpoint file to signal completion.
 

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/src/ctrlrelay/pipelines/secops.py

@@ -126,7 +126,20 @@ class SecopsPipeline:
 
     async def resume(self, ctx: PipelineContext, answer: str) -> PipelineResult:
         """Resume blocked secops with user answer."""
-        prompt = f"User answered: {answer}\n\nContinue from where you left off."
+        # The checkpoint contract is restated here, not just in the
+        # initial prompt (#173). A resumed agent that is told "continue"
+        # and nothing else can do its work, exit 0, write no state, and
+        # be indistinguishable from one that crashed - which is what
+        # happened on 2026-09-16, after three of four pull requests had
+        # already been merged.
+        contract = self._checkpoint_contract(
+            str(ctx.state_file), ctx.session_id
+        )
+        prompt = (
+            f"User answered: {answer}\n\n"
+            "Continue from where you left off.\n\n"
+            f"{contract}"
+        )
 
         # Resume uses Claude's own session UUID (captured on the first spawn
         # and persisted to state_db). Our composite id is not a UUID and will
@@ -425,7 +438,34 @@ yourself about to write a phrase like "no open PRs at all" or "N open
 PRs total", you have already stepped outside the fence — you can only
 speak to the author-filtered results.
 
-## Signaling Completion
+{self._checkpoint_contract(state_file_path, session_id)}"""
+
+    def _checkpoint_contract(
+        self, state_file_path: str, session_id: str
+    ) -> str:
+        """How the agent signals how it stopped.
+
+        Extracted so the RESUME prompt can carry it too (#173). The
+        initial prompt spent ~30 lines establishing this; the resume
+        prompt was 58 characters and said only "continue", so a resumed
+        agent could do its work, exit 0, write no state, and be
+        indistinguishable from one that crashed.
+
+        Measured case, 2026-09-16:
+        secops-AInvirion-Product-Telemetry-bbb99925 resumed after an
+        "Approved", ran 27.4s, exited 0 and wrote no checkpoint - having
+        in fact merged three of four pull requests. The operator was told
+        the resume failed, which was wrong in both directions: most of
+        the work had landed, and the one thing outstanding was never
+        named.
+
+        Per-pipeline rather than shared, because the three contracts
+        differ in substance and not only wording: the dev DONE block
+        carries pr_url and pr_number outputs, and each names different
+        conditions for DONE. One shared block would have quietly changed
+        what two of them promise.
+        """
+        return f"""## Signaling Completion
 
 **CRITICAL**: Before exiting, you MUST write a checkpoint file to signal completion.
 

{ctrlrelay-0.12.0 → ctrlrelay-0.12.1}/src/ctrlrelay/pipelines/task.py

@@ -80,7 +80,20 @@ class TaskPipeline:
         return self._session_to_result(result)
 
     async def resume(self, ctx: PipelineContext, answer: str) -> PipelineResult:
-        prompt = f"User answered: {answer}\n\nContinue from where you left off."
+        # The checkpoint contract is restated here, not just in the
+        # initial prompt (#173). A resumed agent that is told "continue"
+        # and nothing else can do its work, exit 0, write no state, and
+        # be indistinguishable from one that crashed - which is what
+        # happened on 2026-09-16, after three of four pull requests had
+        # already been merged.
+        contract = self._checkpoint_contract(
+            str(ctx.state_file), ctx.session_id
+        )
+        prompt = (
+            f"User answered: {answer}\n\n"
+            "Continue from where you left off.\n\n"
+            f"{contract}"
+        )
         resume_uuid = self.state_db.get_agent_session_id(ctx.session_id)
         log_event(
             _logger,
@@ -181,7 +194,34 @@ pipeline. Don't BLOCK on things you can figure out yourself.
 
 ## Signaling completion
 
-**CRITICAL**: Before exiting, write a checkpoint file.
+{self._checkpoint_contract(state_file_path, session_id)}"""
+
+    def _checkpoint_contract(
+        self, state_file_path: str, session_id: str
+    ) -> str:
+        """How the agent signals how it stopped.
+
+        Extracted so the RESUME prompt can carry it too (#173). The
+        initial prompt spent ~30 lines establishing this; the resume
+        prompt was 58 characters and said only "continue", so a resumed
+        agent could do its work, exit 0, write no state, and be
+        indistinguishable from one that crashed.
+
+        Measured case, 2026-09-16:
+        secops-AInvirion-Product-Telemetry-bbb99925 resumed after an
+        "Approved", ran 27.4s, exited 0 and wrote no checkpoint - having
+        in fact merged three of four pull requests. The operator was told
+        the resume failed, which was wrong in both directions: most of
+        the work had landed, and the one thing outstanding was never
+        named.
+
+        Per-pipeline rather than shared, because the three contracts
+        differ in substance and not only wording: the dev DONE block
+        carries pr_url and pr_number outputs, and each names different
+        conditions for DONE. One shared block would have quietly changed
+        what two of them promise.
+        """
+        return f"""**CRITICAL**: Before exiting, write a checkpoint file.
 
 STATE_FILE: {state_file_path}
 SESSION_ID: {session_id}
@@ -196,6 +236,7 @@ printf '{{"version":"1","status":"DONE","session_id":"{session_id}",'\\
 
 **BLOCKED** (need operator input):
 ```bash
+mkdir -p "$(dirname '{state_file_path}')"
 printf '{{"version":"1","status":"BLOCKED_NEEDS_INPUT",'\\
 '"session_id":"{session_id}","timestamp":"%s","question":"%s"}}' \\
   "$(date -u +%Y-%m-%dT%H:%M:%SZ)" "<QUESTION>" > '{state_file_path}'
@@ -203,6 +244,7 @@ printf '{{"version":"1","status":"BLOCKED_NEEDS_INPUT",'\\
 
 **FAILED** (genuine failure, no way forward):
 ```bash
+mkdir -p "$(dirname '{state_file_path}')"
 printf '{{"version":"1","status":"FAILED",'\\
 '"session_id":"{session_id}","timestamp":"%s","error":"%s"}}' \\
   "$(date -u +%Y-%m-%dT%H:%M:%SZ)" "<ERROR>" > '{state_file_path}'

ctrlrelay-0.12.1/tests/test_docs_site.py

@@ -0,0 +1,244 @@
+"""Validation tests for the Jekyll documentation site under ``docs/``.
+
+These tests do not invoke Jekyll. They assert the structural invariants the
+site relies on so a misconfigured page is caught before GitHub Pages builds.
+"""
+
+from __future__ import annotations
+
+from collections import defaultdict
+from pathlib import Path
+
+import pytest
+import yaml
+
+REPO_ROOT = Path(__file__).resolve().parent.parent
+DOCS = REPO_ROOT / "docs"
+
+
+def _split_front_matter(text: str) -> tuple[dict, str]:
+    if not text.startswith("---\n"):
+        return {}, text
+    end = text.find("\n---", 4)
+    if end == -1:
+        return {}, text
+    raw = text[4:end]
+    body = text[end + 4 :].lstrip("\n")
+    data = yaml.safe_load(raw) or {}
+    if not isinstance(data, dict):
+        raise ValueError("front matter must be a mapping")
+    return data, body
+
+
+def _markdown_files() -> list[Path]:
+    return sorted(p for p in DOCS.rglob("*.md") if "_site" not in p.parts)
+
+
+def test_config_is_valid_yaml():
+    config_path = DOCS / "_config.yml"
+    assert config_path.exists(), "docs/_config.yml must exist"
+    data = yaml.safe_load(config_path.read_text())
+    assert isinstance(data, dict)
+    assert data.get("remote_theme"), "remote_theme must be set for GitHub Pages"
+    assert "jekyll-remote-theme" in (data.get("plugins") or []), (
+        "jekyll-remote-theme plugin required"
+    )
+
+
+def test_landing_page_exists():
+    assert (DOCS / "index.md").exists(), "docs/index.md landing page required"
+
+
+def test_all_markdown_pages_have_title_front_matter():
+    missing: list[str] = []
+    for md in _markdown_files():
+        front, _ = _split_front_matter(md.read_text())
+        if not front.get("title"):
+            missing.append(str(md.relative_to(REPO_ROOT)))
+    assert not missing, f"pages missing title front matter: {missing}"
+
+
+def test_parent_pages_declare_has_children():
+    """Any page referenced as ``parent`` must itself set ``has_children: true``."""
+    titles_with_children: set[str] = set()
+    referenced_parents: set[str] = set()
+    for md in _markdown_files():
+        front, _ = _split_front_matter(md.read_text())
+        if front.get("has_children"):
+            titles_with_children.add(front["title"])
+        parent = front.get("parent")
+        if parent:
+            referenced_parents.add(parent)
+    missing = referenced_parents - titles_with_children
+    assert not missing, f"parents referenced but not declared with has_children: {missing}"
+
+
+def test_nav_order_unique_per_sibling_group():
+    """Pages sharing a parent (or all top-level) must have distinct nav_order."""
+    groups: dict[str, dict[int, list[str]]] = defaultdict(lambda: defaultdict(list))
+    for md in _markdown_files():
+        front, _ = _split_front_matter(md.read_text())
+        parent = front.get("parent", "__root__")
+        order = front.get("nav_order")
+        if order is None:
+            continue
+        groups[parent][order].append(str(md.relative_to(REPO_ROOT)))
+    for parent, by_order in groups.items():
+        collisions = {o: files for o, files in by_order.items() if len(files) > 1}
+        assert not collisions, (
+            f"duplicate nav_order under parent {parent!r}: {collisions}"
+        )
+
+
+def test_no_stray_bare_markdown_outside_structure():
+    """Every page must either be the index, a top-level nav page, or have a parent."""
+    offenders: list[str] = []
+    for md in _markdown_files():
+        rel = md.relative_to(DOCS)
+        if rel.name == "index.md":
+            continue
+        front, _ = _split_front_matter(md.read_text())
+        if front.get("parent") or front.get("nav_order") is not None:
+            continue
+        offenders.append(str(md.relative_to(REPO_ROOT)))
+    assert not offenders, (
+        f"pages without parent or top-level nav_order: {offenders}"
+    )
+
+
+@pytest.mark.parametrize("path", _markdown_files())
+def test_front_matter_parses(path: Path):
+    front, _ = _split_front_matter(path.read_text())
+    assert isinstance(front, dict)
+
+
+def test_ci_runs_the_whole_suite():
+    """No workflow may exclude tests from the run (#179).
+
+    `test.yml` carried `--deselect
+    tests/test_docs_site.py::test_nav_order_unique_per_sibling_group` under
+    the comment "tracked separately and unchanged by this PR". The test
+    passed the whole time - verified by making two pages collide on
+    `nav_order`, which it catches and names both files for - so CI had
+    been skipping a working guard for months and under-counting itself.
+
+    The transferable part is the justification, not the flag. "Unchanged
+    by this PR" is a pull-request-scoped reason frozen into a file that
+    runs for every change. It was true the day it was written and stays
+    plausible forever, because it is true of almost every pull request -
+    so every reader nods and moves on. **Such a reason cannot expire on
+    its own.**
+
+    This makes the next exclusion something that has to be defended
+    rather than inherited: adding one fails here, and the person adding
+    it has to come and say why in this file, where a reviewer will see
+    it next to this paragraph.
+
+    If an exclusion is ever genuinely needed, prefer deleting or fixing
+    the test. Do not leave the third state - a test that exists, is not
+    run, and is believed to be covering something.
+
+    **Reads the parsed `run:` values, not lines of the file.** A review
+    round found three faults in the line-grep version, and parsing fixes
+    all of them: a step `name:` mentioning a flag was reported as an
+    offender (a false positive invites relaxing the guard, and a relaxed
+    guard stops guarding); `--ignore tests/x` with a space slipped past a
+    pattern that required `--ignore=`; and the guard reported clean when
+    it had inspected no pytest command at all.
+
+    **What this does NOT stop, stated so the paragraph above is not the
+    false sentence.** It reads text, so an author actively evading it
+    wins: `--ig"nore"` reaches pytest as `--ignore` and no pattern here
+    sees it. That is not worth chasing - every fix is defeated by the
+    next quoting trick, and anyone editing the workflow to dodge this
+    guard can edit this file just as easily. The fault in #179 was
+    **inherited, not evasive**: a reason that was true once, left in
+    place, nodded past by every later reader. That is what this catches.
+
+    One known false positive: a run script that *prints* an example
+    containing an exclusion flag - `echo "e.g. pytest --ignore tests/x"` -
+    is reported. Deliberately not fixed, because telling the quoted from
+    the executed needs a shell parser, which is more machinery than the
+    defect. Do not write that line; if you must, name it here.
+    """
+    import re
+
+    import yaml
+
+    wf_dir = REPO_ROOT / ".github" / "workflows"
+    workflows = sorted(
+        [*wf_dir.glob("*.yml"), *wf_dir.glob("*.yaml")]
+    )
+    assert len(workflows) >= 3, f"only found {len(workflows)} workflows"
+
+    # Every `run:` script in every step, with where it came from.
+    runs: list[tuple[str, str]] = []
+    for wf in workflows:
+        doc = yaml.safe_load(wf.read_text()) or {}
+        for job_name, job in (doc.get("jobs") or {}).items():
+            for step in (job or {}).get("steps") or []:
+                script = (step or {}).get("run")
+                if isinstance(script, str):
+                    runs.append((f"{wf.name}:{job_name}", script))
+
+    def _code_lines(script: str) -> list[str]:
+        """The lines of a run script that are not comments."""
+        return [
+            line
+            for line in script.splitlines()
+            if not line.lstrip().startswith("#")
+        ]
+
+    invocations = [
+        (where, script)
+        for where, script in runs
+        if any(
+            re.search(r"(?<![\w-])pytest(?![\w-])", line)
+            for line in _code_lines(script)
+        )
+    ]
+
+    # Invariant D, as a POSITIVE assertion. `offenders == []` alone passes
+    # when no pytest command exists at all - a workflow replaced with
+    # `run: true` would have reported clean.
+    assert invocations, (
+        "no workflow step runs pytest. Either CI stopped running the "
+        "suite, or this guard can no longer see it - both are faults, "
+        f"and neither is a clean result. Scanned: {[w for w, _ in runs]}"
+    )
+
+    # Flags that remove tests from a run, accepting `=` or a space.
+    # `--maxfail` is not one: it stops early on failure, it does not hide
+    # a passing test. `-m` selects by marker, which this suite does not
+    # use for exclusion.
+    excluders = re.compile(
+        r"--deselect(?:[=\s]|$)"
+        r"|--ignore(?:-glob)?(?:[=\s]|$)"
+        r"|(?<!\w)-k(?:[=\s]|$)"
+    )
+
+    offenders: list[str] = []
+    for where, script in invocations:
+        for lineno, line in enumerate(script.splitlines(), start=1):
+            if line.lstrip().startswith("#"):
+                continue
+            if excluders.search(line):
+                offenders.append(f"{where} run line {lineno}: {line.strip()}")
+
+        # Narrowing the target paths excludes tests without any flag at
+        # all, which is the bypass a flag list cannot see.
+        targets = [
+            tok
+            for tok in script.split()
+            if tok.startswith("tests") and not tok.startswith("-")
+        ]
+        if targets and not any(t.rstrip("/") == "tests" for t in targets):
+            offenders.append(
+                f"{where}: runs only {targets}, not the whole tests/ tree"
+            )
+
+    assert offenders == [], (
+        "a workflow excludes tests from the run. Delete the test, fix it, "
+        "or change this guard and say why here - do not leave a test that "
+        f"exists, is not run, and is assumed to pass (#179): {offenders}"
+    )