All tasks

Patch Conflict Forecaster

TypeScriptHardClorvin Labs original task

Before parallel edits are applied, we need to know which edits overlap. Implement the conflict report using the task's interval rules rather than treating touching boundaries as automatically conflicting.

Build the implementation in TypeScript under /app, with /app/run.sh as its entry point. Read one JSON request from standard input and write one JSON result to standard output. Input is a list of edits with unique string id and integer start/end, where 0 <= start <= end. Nonempty ranges are half-open and conflict when their interiors overlap. Two insertions (start=end) conflict at the same position. An insertion conflicts with a nonempty range only strictly inside it, not at either boundary. Return all conflicting ID pairs, each sorted internally, then sort pairs lexicographically. Reject duplicate IDs and invalid ranges.

Reject inputs that violate an explicit validation rule with exit status 2, no standard output, and {"error":"invalid_input"} on standard error. For valid input, exit with status 0. Keep the implementation reusable for new inputs; it must work offline and must not depend on the example data being the only data it receives.

Repair or replace the unfinished /app/run.sh and add source files under /app. Malformed JSON must use the same invalid-input response. Do not read /tests or /oracle from the application.

Inspect the checks. Explore the results.

9 recorded reference checks

Review the checks and explore the evaluation view for patch conflict forecaster.

Example dataExplore the controls with illustrative values. These are not recorded GPT-5.5 or Opus 4.8 results.
Read the example values
Illustrative reward values, not model test results
AttemptGPT-5.5 (demo)Opus 4.8 (demo)
100.25
20.250.5
30.50.5
40.751
50.50.75
610.75
70.751
811

Tell us what needs doing.

Share the scope, the expected volume and your timeline.
We’ll work out where our team can help.