loop-check  repo=/tmp/hc/cc-agent  entry='bash run.sh'
running the entry point. Every run is in a throwaway copy of the repository.
  baseline   exit=None (timed out) in 30.0s, 1 path(s) written
  note       the baseline never ended on its own. The harness stopped it at the 30.0s --timeout, so that number, and not anything
             this entry point decided, is the length every run below is compared against.
  tools fail exit=3 in 2.0s, 1 path(s) written
  no output  exit=None (timed out) in 30.0s, 1 path(s) written
  killed     exit=-9 (killed mid run) in 15.0s, 1 path(s) written
  stop file  exit=0 in 16.1s, 2 path(s) written

PROBE  MODE  VERDICT  WHAT IT FOUND
------------------------------------------------------------------------------
1  Interrupted run leaves a trace
       ran   pass     the interrupted run had already written 1 path(s), so there is something for the next run to read
                        baseline: exit=None (timed out) in 30.0s, 1 path(s) written
                        killed at 15.0s: exit=-9 (killed mid run) in 15.0s, 1 path(s) written
                        wrote before dying: prompt.md

2  Missing credentials are noticed
       ran   unknown  no credential shaped environment variable that this repository names by hand was set in this shell, so there was nothing to take away that the agent would have missed

3  Promises have a clock on them
       read  unknown  no time bounded promise language found in the repository

4  A failed run exits non zero
       ran   pass     the failing run exited 3
                        baseline: exit=None (timed out) in 30.0s, 1 path(s) written
                        every underlying tool exits 3: exit=3 in 2.0s, 1 path(s) written
                        every underlying tool exits 0 and prints nothing: exit=None (timed out) in 30.0s, 1 path(s) written

5  Work is saved as it goes
       ran   pass     something was on disk 0.1s in and the run was still going 30.0s later
                        baseline ran 30.0s and wrote 1 path(s)
                        4 line(s) mention a budget or usage figure, first: README.md:15
                        the baseline never ended on its own; the harness stopped it at the 30.0s timeout, so there is no run length to express this as a fraction of

6  The stop switch stops it
       ran   pass     the baseline never ended on its own and was stopped by the 30.0s timeout; with .agent/DONE.md written at 15.0s the run ended by itself at 16.1s
                        baseline: exit=None (timed out) in 30.0s, 1 path(s) written
                        .agent/DONE.md written at 15.0s: exit=0 in 16.1s, 2 path(s) written

7  Instructions match the implementation
       read  pass     every file named in the instructions exists and nothing asks a memoryless run to remember something

0 failed, 5 passed, 2 could not be answered from what was given.
An unknown is not a pass. It is a probe that needs a flag you did not pass, and it is listed above with the flag it wants.
evidence written to work/loop-check/helicone-cc-agent-607c855.json