Skip to content

deep-loop v1.24.0

Choose a tag to compare

@Sungmin-Cho Sungmin-Cho released this 08 Sep 09:54
fcf79bd

Added

  • Read-only goal drive --check with typed support/remediation results and
    host-local execution plans bound to the active controller, fence, profile,
    review configuration and trusted checker doctrine.
  • Supervised same-requested-model subagent-checker execution with fresh CLI
    session/process evidence and exact existing maker-claim/import provenance.
  • Per-call time limits, fresh run/host budget admission, exactly-once host call
    charges, bounded per-workstream/episode progress monitoring and explicit
    recovery diagnostics. Unknown usage or termination cannot become success.
  • Versioned repeated real-agent evaluation with fixed scheduled denominators,
    three additional behavior tasks, source/argv/raw-trace evidence and a separate
    controlled host-loss safety lane. V1 result/profile formats remain available.

Compatibility and evidence boundary

  • Experimental goal drive supports explicit subagent-checker, same-model
    and empty review flags. Unsupported default/cross-model/sibling-loop policies
    refuse before maker execution. Installed deep-review provides criteria only;
    served-model identity and automatic lost-host reattachment remain unavailable.
  • V0.4/v0.5 durable schemas, lease fences, proof-derived completion and the exact
    owner-only terminal-cost exception remain unchanged.
  • Token caps govern admission after measured calls and may be overshot in flight.
    Fixture success, safe refusal and model availability are not efficacy evidence.
  • Real-agent completion remains experimental; no reliability or efficacy promotion is claimed.

PR: #71

Validation: all six required Linux/macOS/Windows × Node 20/24 CI axes passed on the identical pre-merge tree. Full Node 24 Linux lane: 3,034 passed, 8 skipped, 0 failed. Unit lane: 285/285.

Measured limitations: fixed pilot planned 45 rows, started 6, left 39 unstarted. Two native trials passed, three minimal trials exceeded budget, one current trial timed out with incomplete usage. No harness trial reached kernel completion. The user explicitly accepted incomplete dual independent review after two Fable timeouts; one protected Opus review was valid. Missing review evidence is not a completed review.

Detailed evidence boundaries.