superstition-verification

Superstition verification systematically tests observations that may be outdated, limited, or confirmed. The workflow selects unverified superstitions from logs, assesses evidence weight, creates minimal repros using Playwright, deploys and tests them, and produces framework-author-reviewed verification documentation for each claim.

Create a minimal repro under community-docs/superstitions/repros that isolates the superstition claim. Deploy and test it with Playwright to confirm or disconfirm the behavior, then document findings before cleanup of original patterns for framework author review.

Read the superstition's metadata and context to determine evidence strength. Investigate using documentation, code inspection, and community knowledge to understand the claim, then decide whether the superstition is no longer relevant, has limitations, or is actually confirmed.

Yes. Playwright executes test deployments of minimal repros to verify superstition behavior. Test results and verification logs are generated for framework authors to review before disconfirmation or confirmation is documented.

Before disconfirming, locate and clean up the original patterns without workarounds. This ensures the disconfirmation is based on current behavior and framework-author review can validate the pattern cleanup is complete and accurate.

Unverified superstitions are listed in VERIFICATION-LOG.md. Select the oldest unverified entry to begin the systematic verification workflow, assessing evidence weight and creating minimal repros as needed.