Repository navigation
Measure Puritanical against its alternatives and probe the rules it added - #20
Merged
Merged
Conversation
Run Ponytail, Superpowers and the Karpathy guidelines from pinned checkouts alongside Puritanical, with nothing vendored. Probe the rules this fork added: stated reading, dead-code reporting and not-run reporting. Add Caveman's MIT notice and SECURITY.md, compare the alternatives in the README, and stop a v* tag from triggering an npm publish that cannot succeed.
Fail replies that report dead code and delete it, hedge and then claim a result, or state an assumption unrelated to the ambiguous request. Record each rival's remote and commit, and stop before any spend on a bad checkout.
Drop a negated clause whole so 'cannot verify that the tests pass' claims nothing, narrow what counts as a reading of 'old', and give the rival selftest its own git fixture so a source archive still runs it.
'Sorted before pruning' no longer counts as a reading of 'old', and a clause after 'but' or 'and' is no longer dropped with the negation before it.
Same 23 cases, without the repeated test blocks.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lets Puritanical be measured against its popular alternatives, and tests whether the rules this fork added change what the agent does. Also closes licence and trust gaps. No rule text changes.
Evidence
After:
tests/behavior.test.jshas 31 passed, 0 failed, with both as expected failures.run.py --selftestcovers this and passes from a checkout and from a source archive.sync --check,check-versionsandpi-extension(30 of 30) pass.Merge danger
Door: two-way. Blast radius: benchmarks, docs
A
v*tag no longer publishes to npm; run thepublishworkflow by hand once trusted publishing is set up. Nothing is published to npm today.Unverified
notrunwrongly, and 'created before 1 January 2020' failsambiguitywrongly.SECURITY.mdpoints to private vulnerability reporting, which is off until the owner enables it.correctness.test.jscases (email bare unfenced code, csv timeout) fail, as they do on unmodifiedmain; cause not established. CI decides.