Local workflow · Go · Medium (estimated)
Repair a supplied job ledger and execute only unfinished local jobs.
Acceptance gates · all three must pass
No measured result. Open a gate to read its exact criterion.
Classification
Recover matching orphan output, skip the completed job, execute the pending job, and classify conflicting orphan output by the documented digest rule.
jobs-recovery-g1Preservation
Never rewrite a completed output or conflicting orphan; preserve unrelated historical output bytes. If any conflict exists, report nonzero status while retaining successfully committed nonconflicting work.
jobs-recovery-g2Replay and accounting
Report exact alphabetical ID lists, with no ID in two lists. Repeating the procedure executes no completed job and leaves output bytes unchanged.
jobs-recovery-g3
Required evidence files →Required deliverables
- Produce the reconciled ledger, required job outputs, and recovery.json; retain a reproducible local procedure.
Success also requires normal completion within the shared time, token, and cost limits. Each gate result must retain its ID and assertion evidence in grade.json.
Full task and output contract
Using the documented job processor interface, reconcile a frozen jobs.jsonl, ledger.json, and output directory. The inputs contain a completed job, a matching committed output with a missing ledger entry, a pending job with no output, and an unrelated historical output. Recover the matching orphan into the ledger, execute only pending work, and create recovery.json listing recovered, executed, skipped, and conflicting IDs alphabetically. A conflicting orphan must be preserved and reported, not overwritten. Job payloads are UTF-8 strings; compare lowercase SHA-256 of their exact bytes. Expected output is outputs/<id>.txt containing the uppercase payload and one final newline. recovery.json has arrays recovered, executed, skipped, and conflicting. Ledger entries contain id, payload_sha256, and status=completed.
Difficulty rationale and specification
Existing partial progress must be classified before any work is repeated.
Intended demands: Evidence selection · State management · Tool use.
Specification: jobs-recovery · Workspace: go-jobs. Workspace, reference solution, and grader are not built or validated.