aboutsummaryrefslogtreecommitdiff
path: root/playwright-js/lib
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-22 14:26:43 -0500
committerCraig Jennings <c@cjennings.net>2026-05-22 14:26:43 -0500
commit3916dc446c8925f64a974498d326637b34d46575 (patch)
treec6f685d27707511a6f0bd8fc18279e70371d45f7 /playwright-js/lib
parent282a35d30edca8c5ae7a5955111440908413f267 (diff)
downloadrulesets-3916dc446c8925f64a974498d326637b34d46575.tar.gz
rulesets-3916dc446c8925f64a974498d326637b34d46575.zip
docs(skills): tighten debug, root-cause-trace, and five-whys
Three audit-pass fixes across the debugging skills. debug now captures environment and recent-change context (versions, flags, dataset, seed/clock, concurrency, recent commits) as a Phase-1 step. Many intermittent bugs live in state or environment, not a local code path, and "what changed recently" is often the fastest route to the cause. root-cause-trace's defense-in-depth said to add a check at every layer that could have caught the bad value, which breeds validation spam. It now adds checks only at boundary-owning layers (ingress, persistence, the invariant owner, final render), and says a pass-through function that owns neither a boundary nor an invariant shouldn't get a duplicate null check. five-whys now makes each link carry an evidence field and a counterfactual: if you remove this cause, does the symptom above still happen? That's the guard against a tidy chain that reads well but wouldn't have prevented the failure.
Diffstat (limited to 'playwright-js/lib')
0 files changed, 0 insertions, 0 deletions