Skip to content

0.9.106

Choose a tag to compare

@michael-denyer michael-denyer released this 27 Oct 23:29
· 124 commits to main since this release
abd512a

backnotprop/pstack#14, filed by @yasuyuki, reports a /no-comments run that marked a correct Cargo comment for deletion, one saying that profile settings come only from the workspace root. The same run ended when a second report was rejected, before any accepted edit landed. The comment-sicko prompt deletes a comment whenever it is unsure a keep clause applies, and it named no source to check a dependency's rule against.

The agent now takes a comment that states a rule of a dependency, platform, vendor, or protocol to that system's documentation or source code. A kill of such a comment cites the page or file that refutes the rule or shows it binds something else, and the report lists each one. When the agent cannot reach either, or what it reads leaves the rule unsettled, the comment stays as a HOLD that names the rule and where to check it. /no-comments leaves each such HOLD in place and reports it open, and it restores as a HOLD any kill of such a comment that lacks a refuting citation. A rejected second report now fails /no-comments for that report's findings, not for the run, and the accepted findings still go through steps 3 to 6.

Both files are declared policy forks, and five rule pins in tests/skill-rules.test.mjs fail if a sync drops either rule. A run of the new prompt with Sonnet on that Cargo comment, with web tools off, kept it as a HOLD that named the Cargo Reference page. The previous prompt also kept it in that run, on the model's recollection with no check, so the run does not tell the two prompts apart. The second-rejection path and the reached-but-unsettled path were not run live.