slice-impl

Summary

Triggered when a failing tracer test exists for the slice. Eagerly loads anti-pattern entries scoped to the slice's touched_paths before writing anything. Reads the slice definition (including out_of_scope) and the failing test in full. Writes the minimum implementation that makes the failing test pass and keeps all existing tests green. Refuses to add any feature listed in out_of_scope. Refuses to modify the test. Stops if no failing test exists or if the failing test does not belong to this slice.

Procedure

Step 1 — Verify a failing test exists for this slice

Before reading any artifact, confirm that:

1. A test file for this slice exists. The failing tracer test for slice <slice_id> is produced by tracer-test — confirm the file is present.
2. The test is currently failing (exits non-zero). Run the test suite or the single test file to confirm. If the test is passing, stop and output:

Cannot start slice-impl: no failing test found for slice <slice_id>.
The test at <test_path> is already passing (or no test file exists).
Run tracer-test for this slice first, then run slice-impl.