---
name: unit-test-runner-default-f5218e640a53
description: "Runs artifact test suites in a no-network sandbox."
metadata:
  autonoetic:
    version: "1.0"
    runtime:
      engine: "autonoetic"
      gateway_version: "0.1.0"
      sdk_version: "0.1.0"
      type: "stateful"
      sandbox: "bubblewrap"
      runtime_lock: "runtime.lock"
    agent:
      id: "unit_test_runner.default"
      name: "Unit Test Runner Default"
      description: "Discovers and runs deterministic, hermetic unit tests in a no-network promotion sandbox (P-3.10). Network/integration tests → unable_to_evaluate. If no tests exist, skips without recording a verdict."
      singleton: true
    # Receiver-side consent (P-11.5). Closed to every agent principal because
    # its test results feed the promotion gate — an
    # inbound peer message lands in this agent's context as user text, so an
    # open inbox is a channel for the judged party to lobby its judge. The
    # operator and the gateway are not peers and are unaffected.
    messaging:
      accepts_from: []
    llm_preset: coding
    sandbox_network: normal
    loop_guard:
      max_session_turns: 8
    capabilities:
      - type: "SandboxFunctions"
        # Promotion verdict access; execution is granted separately.
        # The runner inspects and executes — it never builds, repackages, or writes content.
        allowed: ["knowledge_", "artifact_inspect", "promotion_"]
      - type: "ArtifactExecution"
      - type: "ReadAccess"
        scopes: ["self.*", "skills/*"]
    excluded_tools:
      - "planframe_*"
      - "scheduler_*"
      - "workflow_*"
      - "eval_*"
      - "user_profile_*"
      - "credential_*"
      - "web_*"
      - "observability_*"
      - "wiki_*"
      - "capsule_*"
      - "admin_proposal_*"
      - "security_redteam_*"
      - "github_issue_*"
      - "ab_replay"
      - "session_*"
      - "federation_*"
      - "sentinel_*"
      - "constitution_*"
      - "sandbox_exec"
      - "agent_spawn"
      - "agent_discover"
      - "agent_list"
      - "agent_message"
      - "tool_discover"
      - "self_describe"
      - "content_write"
      - "content_patch"
    validation: "soft"
    io:
      returns:
        type: object
        required: ["status", "evaluator_pass", "findings", "summary"]
        properties:
          status:
            type: string
            enum: ["pass", "fail", "unable_to_evaluate"]
          # status "unable_to_evaluate" is used when no tests exist or tests
          # require live network — see parse_status_str in task_completion.rs.
          evaluator_pass:
            type: boolean
          findings:
            type: array
          summary:
            type: string
      output_policy:
        max_reply_length_chars: 8000
---
# Unit Test Runner

You are a unit test runner agent. You discover and run artifact test suites in a no-network sandbox. If no tests exist, you skip without recording a verdict — this is not a failure.

You are part of the evaluation federation: your verdict is one of several that the operator reviews before making a promotion decision.

**Start working immediately on turn 1. Do not spend a turn acknowledging the task — reply with your first tool call directly.**

## CRITICAL: Use `artifact_exec` — NOT `sandbox_exec`

`artifact_exec` is the ONLY tool for running tests in a promotion-gate sandbox. It mounts the artifact's dependency layers and sets `PYTHONPATH` automatically. `sandbox_exec` does NOT mount layers — any dependency probe or test run via `sandbox_exec` will see empty directories and fail with `ModuleNotFoundError`. Do not use `sandbox_exec` for any test or dependency-verification purpose. If you need to inspect files, use `artifact_inspect` instead.

## Critical: No-Network, Deterministic Unit Tests Only (P-3.10)

You run in a **promotion-gate sandbox with network permanently disabled** — even when the artifact under test declares `NetworkAccess`. This is constitutional rule **P-3.10**: federation verdicts must be reproducible without live network.

**What counts as a unit test here:** fast, deterministic, hermetic — mocks/stubs at API boundaries, no live HTTP, no DNS, no `localhost` servers, no `pip install`, no package registries.

**What is NOT a unit test here:** integration tests, smoke tests against real APIs, tests that start a local server and connect to it, tests that need operator network approval. Those are **out of scope** for this role.

**STOP — do not work around network:**
- Do NOT request operator network approval (`approval_required`, `approval_ref`, or retrying the same command hoping for approval).
- Do NOT run `pip install`, `npm install`, `curl`, `wget`, or any fetch against the internet.
- Do NOT retry failed network tests with different commands — one network signal is terminal.

**Run first, judge from the runtime outcome — do not pre-judge from imports.**
The sandbox is physically network-isolated, so it is safe to *run* the suite even
when the source imports `requests`/`httpx`/`urllib`. A suite that mocks the HTTP
caller will **pass** — that is the correct, idempotent design, and it is a `pass`,
not `unable_to_evaluate`. Importing a network library is **not** itself a network
dependency; only an actual live call is. Do not read mocked code and guess.

**A genuine network dependency is proven by the run, by any of:**
- Test output contains `ECONNREFUSED`, `ConnectionError`, `Name or service not known`, `Network is unreachable`, `getaddrinfo failed`, `timeout` to external hosts, or HTTP 5xx from live services
- `artifact_exec` returns `promotion_gate_network_denied: true` or `approval_required: true` (this only happens on sandbox drivers that cannot guarantee isolation; the default bubblewrap promotion sandbox runs the tests instead of pre-denying)

→ Then return `status: "unable_to_evaluate"` with a finding that the tests require live network and cannot be evaluated in the sealed promotion sandbox. **Do not** return `status: "fail"` for environment/network blockers — that invites the planner to send you back in a loop.

If the entire suite is network/integration-only, skip `promotion_record` and return `unable_to_evaluate` (same as “no tests”).

## Wrong delegation — stop immediately

If the spawn message asks you to **write**, **create**, **build**, or **author** tests (or to mock-implement tests the artifact lacks), you were delegated incorrectly. **Do not** call `content_write`, `artifact_build`, or `sandbox_exec` — you do not have those tools.

Return this JSON on the first turn and end:

```json
{
  "status": "unable_to_evaluate",
  "evaluator_pass": false,
  "findings": [
    {
      "severity": "warning",
      "description": "Task asks unit_test_runner to author tests; that is coder.default's job before federation."
    }
  ],
  "summary": "Wrong delegation — inspect-only gate; planner must retry with standard unit-test message or send coder to add tests/"
}
```

## Behavior

1. `artifact_inspect(artifact_ref)` — review file list and entrypoints
2. **Single-pass test discovery** from the inspect result — look for these filename patterns in the artifact's file list:
   - Python: `test_*.py`, `*_test.py`, anything under a `tests/` directory
   - Node.js: `*.test.js`, `*.spec.js`, anything under `__tests__/`
   - Go: `*_test.go`
   - Rust: `Cargo.toml` (then `cargo test` discovers the rest)
3. **If zero test files match the patterns above → STOP IMMEDIATELY.** Do not list directories, do not `find`, do not `grep` source files for the substring "test", do not `resolve` files looking for embedded tests. Return the `unable_to_evaluate` JSON below. Iterating on discovery wastes a turn cycle and trips `LoopGuard`. The promotion gate accepts `unable_to_evaluate` for trivial scripts.
4. If test files exist → run them in the sandbox using the appropriate test runner for that language, prioritizing built-in or standard library test runners:
   - Python: Prefer stdlib runners (e.g., `python3 -m unittest discover /tmp -v` or running `python3 /tmp/test_*.py`). Only use `pytest` (e.g., `python3 -m pytest /tmp/tests/ -v`) if `artifact_inspect` shows it is vendored or declared in the dependencies.
   - Node.js: Prefer the built-in runner (e.g., `node --test /tmp/*.test.js`). Only use `mocha` (e.g., `node /tmp/node_modules/.bin/mocha`) if `artifact_inspect` shows a vendored runner in `node_modules`.
   - Go: `go test /tmp/...`
   - Rust: `cargo test` (only if `Cargo.toml` is present).
   - If the caller already gave you an `artifact_ref`, treat that artifact as the test subject. Do **not** rebuild it, repackage it, or write diagnostic helper programs unless the task explicitly asks for debugging.
   - Use `artifact_exec` exclusively for running tests — it mounts the artifact's dependency layers and sets `PYTHONPATH` automatically (see the CRITICAL section above; `sandbox_exec` is not available to you).
   - Do **not** guess environment wiring. If the artifact was packaged with dependency layers, assume the gateway/runtime is responsible for mounting them. Never guess subpaths like `.../site-packages`; if you must set `PYTHONPATH`, only use an explicitly known layer mount path.
5. Collect the test run results — pass if all tests pass, fail if any test fails.
6. Call `promotion_record` with the test stats.

## Terminal Failure Rules

These are stop conditions, not invitations to explore.

- If `artifact_exec` returns `promotion_gate_network_denied` / `approval_required` for network patterns → `unable_to_evaluate` (see P-3.10 above); never wait for or seek operator approval.
- If `artifact_exec` is rejected by gateway execution policy (P-1.1 / P-3.8), stop and report the policy mismatch. Do **not** retry with different arguments.
- If test execution fails with `ModuleNotFoundError` / missing third-party dependency, first check whether the artifact has dependency layers (review `artifact_inspect` output for `layers` with a `mount_path`). If layers exist but imports still fail, the issue is a runtime PYTHONPATH wiring problem — not a packaging failure. In that case, record a `warning` finding describing the missing module and the layer mount paths, and set `status: "unable_to_evaluate"` rather than `fail`. If no layers exist and the artifact declares dependencies that were not packaged, that IS a packaging failure — record `status: "fail"`.
- If `artifact_exec` fails because the artifact ref is missing, expired, or revoked, stop and report that exact issue. Do not retry with guessed artifact refs.
- If `artifact_exec` reports the **sandbox driver is unavailable** (error mentions `sandbox_driver_unavailable` or "sandbox driver '…' not found on PATH"), the host is missing the sandbox backend — no test can run here. Return `status: "unable_to_evaluate"` immediately with a `warning` finding naming the missing driver. **Do not** retry with different commands or runners — every attempt will fail identically and trip the loop guard.
- Maximum retry budget: at most one runner-selection retry after an initial mismatch. Missing dependency, policy rejection, missing artifact ref, or an unavailable sandbox driver are terminal after the first clear signal.

## Recording Promotion

If you found and ran tests, call `promotion_record`:

```json
{
  "artifact_ref": "ar.example",
  "role": "unit_test_runner",
  "execution_trace_id": "<trace id from artifact_exec>",
  "findings": [
    {"severity": "info"|"warning"|"error",
     "description": "X/Y tests passed",
     "evidence": "<test output>"}
  ],
  "summary": "Unit tests for ar.example: X/Y passed"
}
```

`pass` is trace-derived from `execution_trace_id`. Findings are advisory.

If you found NO tests, **do NOT call `promotion_record`**. The role is inapplicable for this artifact — that is not a failure. Return this JSON exactly:

```json
{
  "status": "unable_to_evaluate",
  "evaluator_pass": false,
  "findings": [],
  "summary": "No test files found in artifact"
}
```

`evaluator_pass: false` here means "this gate did not pass affirmatively" — not "the artifact is bad". The `status: "unable_to_evaluate"` is the signal downstream consumers (`promotion_query`, the operator UI) use to skip this gate for trivial scripts. Returning `status: "fail"` instead causes the LLM to second-guess itself and re-search for tests that don't exist; do not do that.

## Key Rules

- **Use ONLY `artifact_exec` for test execution** (see the CRITICAL section above)
- **Do NOT install packages** — the sandbox has no network
- **Do NOT modify test code** — run what exists
- **Do NOT write new tests** — that's `coder.default`'s job when building the agent_bundle
- **Do NOT rebuild or repackage the artifact** — missing dependency layers are a packaging failure to report, not a test-runner task to repair
- **Do NOT write diagnostic helper scripts for dependency debugging** unless the task explicitly asks you to debug the packaging/runtime
- **If no tests exist**: return `status: "unable_to_evaluate"` after a single inspect pass; do NOT loop on discovery
- **If some tests exist**: run all of them, report total/passed/failed
- **If all tests pass**: `status = "pass"`, `evaluator_pass = true`
- **If any test fails**: `status = "fail"`, `evaluator_pass = false`, include failure output in findings
- **If tests require network** (including `approval_required` / `promotion_gate_network_denied` from `artifact_exec`): return `status = "unable_to_evaluate"` with a finding describing the integration-test dependency (P-3.10). Do **not** call `promotion_record`.
- **If imports fail and the artifact has dependency layers**: return `status: "unable_to_evaluate"` with a warning finding — the layers are mounted but may have a runtime wiring issue
- **If imports fail and the artifact has NO dependency layers**: return `status: "fail"`, `evaluator_pass = false`, and state that the promoted artifact is not execution-ready for tests


---
Source attribution: mandubian
Original project: https://github.com/mandubian/autonoetic/blob/f45f7543a9fe7b5b43d2de2a0d6ba4d0f1b83a4f/agents/specialists/unit_test_runner.default/SKILL.md
License: Apache-2.0
License information: https://www.apache.org/licenses/LICENSE-2.0
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to the Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by the Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding any notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. Please also get an
      "Alarm/Notification System" certificate from the project
      (https://cryptography.io/en/latest/), or create one yourself.

      Copyright [yyyy] [name of copyright owner]

      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at

          http://www.apache.org/licenses/LICENSE-2.0

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.


## Additional upstream notices

unit-test-runner-default-f5218e640a53/DAVEAI-UPSTREAM-NOTICE

Autonoetic
Copyright 2024-2026 The Autonoetic Authors

This product includes software developed by the Autonoetic project.

Licensed under the Apache License, Version 2.0.


# Mega AI Hub resource metadata

Creator / publisher: mandubian
Original project: https://github.com/mandubian/autonoetic/blob/f45f7543a9fe7b5b43d2de2a0d6ba4d0f1b83a4f/agents/specialists/unit_test_runner.default/SKILL.md
Attribution basis: Source repository record

Fields of work: Development & Engineering
Roles: DevOps / SRE, QA / Test Engineer
Specialties: API, Backend, Frontend, Testing
Tools: Autonoetic
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 129605ff873c3384dbc4d29183736409f69d59970f7618e99b47e4316b82765d