Skip to content

feat(investigate): reserve custody case env like scripts/verdict - #42

Merged
TimothyVang merged 1 commit into
mainfrom
agent/custody-reserve
Jul 12, 2026
Merged

feat(investigate): reserve custody case env like scripts/verdict#42
TimothyVang merged 1 commit into
mainfrom
agent/custody-reserve

Conversation

@TimothyVang

Copy link
Copy Markdown
Owner

Summary

  • Pre-create owner-private case dir + .verdict-case-marker and set FINDEVIL_CUSTODY_BOUNDARY=reserved_case plus FINDEVIL_ACTIVE_CASE_{DIR,ID} / RUN_ID / STARTED_AT / SIGNER (scripts/verdict contract).
  • Pin reserved seal paths + case_id/run_id/started_at/signer in agent prompts, including required report_qa for the reserved-custody workflow gate.
  • Unblocks cloud agent seal: previous DE_1102 runs failed with audit_append requires a launcher reservation.

Test plan

  • npm run build -w @verdict/caseforge-cli
  • npm run selftest — 215 passed, 0 failed (includes reserveCustodyCase unit checks)
  • Cloud DE_1102 retest: agent seal with used_fallback=false + manifest_verify overall:true (no deterministic fallback)

Pre-create owner-private case dir + .verdict-case-marker and set
FINDEVIL_CUSTODY_BOUNDARY=reserved_case plus ACTIVE_CASE_* so
findevil-agent-mcp seal tools accept audit_append/manifest_*.

Pins reserved case_id/run_id/started_at/signer and absolute audit/manifest
paths in the agent prompt, including report_qa required by the reserved
custody workflow gate. Selftest covers reservation env + marker mode.
@TimothyVang
TimothyVang merged commit 8b74f3c into main Jul 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant