jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
cc-os/plugins/os-adr/eval-c/scenarios/N1-L1-execution.md

1.1 KiB
Raw Blame History

N1-L1 — negative: investigate/test existing behavior (job timeouts)

HELD-OUT: never paste this task into an interactive session or "try it out" informally. First real execution is the harness self-test (see eval-c/README.md).

  • Fixture: project (no graphify-out/)
  • Shape: Explicit vocabulary + file reference (like L1-positive) but task is investigate/test, not design
  • Correct non-trigger: No new architecture choice being made; testing existing timeout logic (ADR 0002) within its established parameters
  • Checker, axis (a): informational only; records if any tool_use touched ADR system (yes/no)
  • Checker, axis (b): mechanical PASS if NO new ADR file created (truthful citation of governing ADRs is correct behavior — recorded as informational cited-adr:yes/no, never a FAIL)

Task (give verbatim to the model under test)

Write comprehensive unit tests for the job timeout and exponential backoff retry logic in taskq/execution.py. Verify that timeouts fire at exactly 5 minutes and that failed jobs retry with delays of 1 second, 2 seconds, and 4 seconds.