You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[v0.5] Plant evidence states what it shows: generator refusals by locus, SP-16's forged-program plant, the SM-32 records (follow-up to #167) #179
assert_targeted (crates/conformance/src/cases/preservation.rs:91-101) counts any generator refusal as a caught lowering plant. It checks only that the function owns a relation, not that the refusal names the mutated function and site. The SP-15 record (VERIFICATION.md:1471-1530) shows that the six observed refusals do name the site, but the case does not assert it. Both Buffer plants are refused by the generator, so no Buffer mutation reaches the kernel.
SP-16's plant "forged program literal" forges the crate term, not the program row.
VERIFICATION.md:8870-8885: the two SM-32 plants cite bit_contribution, is_fixed_integer() and is_unsigned_fixed_integer(), which exist in no version of the code, and an output ("check fails with LLT4001: ()") the harness does not print.
Definition of done:
A refusal counts as caught only when its message names the mutated function and site, and the case asserts it.
At least one Buffer mutation is carried to the kernel by a plant that bypasses the lockstep refusal, or the SP-02 statement says which kinds the generator alone refuses.
SP-16 gains a plant on the program row, or the plant is renamed.
Both SM-32 plants are re-run against widen.rs and semantic.rs, with the real edit and the real output recorded.
changed the title [-][v0.4] Plant evidence states what it shows: generator refusals by locus, SP-16's forged-program plant, the SM-32 records (follow-up to #167)[/-][+][v0.5] Plant evidence states what it shows: generator refusals by locus, SP-16's forged-program plant, the SM-32 records (follow-up to #167)[/+]on Oct 18, 2026
I can take this one. I'd make assert_targeted in crates/conformance/src/cases/preservation.rs count a refusal as caught only when its message names the mutated function and site, give SP-16 a plant on the program row, and correct the SM-32 records in VERIFICATION.md so they cite code and output that exist. For the Buffer plants, would you rather I carry one mutation to the kernel past the lockstep refusal, or update the SP-02 statement to say which kinds the generator alone refuses?
Activity
[-][v0.4] Plant evidence states what it shows: generator refusals by locus, SP-16's forged-program plant, the SM-32 records (follow-up to #167)[/-][+][v0.5] Plant evidence states what it shows: generator refusals by locus, SP-16's forged-program plant, the SM-32 records (follow-up to #167)[/+]sharmis-tp commentedon Oct 19, 2026
I can take this one. I'd make
assert_targetedincrates/conformance/src/cases/preservation.rscount a refusal as caught only when its message names the mutated function and site, give SP-16 a plant on theprogramrow, and correct the SM-32 records in VERIFICATION.md so they cite code and output that exist. For the Buffer plants, would you rather I carry one mutation to the kernel past the lockstep refusal, or update the SP-02 statement to say which kinds the generator alone refuses?