mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-13 01:10:52 +01:00
Krzysztof kuhy Rudnicki
4e016622b6
Probed the two remaining candidates at HEAD instead of guessing: nvidia_troubleshoot.sh is ruled OUT. Its trace dies at step 3 because backup_file writes /etc/profile.backup.<stamp>, a new SIBLING in unbound /etc — a file bind cannot cover siblings and bare /etc is refused. 239 of its 336 lines never execute, so keeping the unproven ones in the entry (the rule the pacman split established) leaves the entry at ~265, still over the cap. The file cannot satisfy both the rule and the goal. install_leechblock.sh is the best-conditioned target left: exit 0, 93 files written, and all 93 hashes byte-identical across two consecutive runs. Only the echoed prefix path and curl's progress meter vary. But it fires an unstubbed `pkill` at every Chromium-family browser. pkill is not in the stub set and --prefix cannot contain it, because signals are not filesystem writes. Two probe runs fired it, harmless only because no browser happened to be open. That is now documented as its own trap, and the brief tells the next session to pass --stub pkill and check for a live victim first. Also recorded: for a target embedding $(date), diff the written files' CONTENTS with the date normalized rather than falling back to comparing sizes — that still catches a dropped line, which a size comparison does not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY |
||
|---|---|---|
| .. | ||
| explanations | ||
| superpowers | ||
| app-split-recipes.md | ||
| device-owner-wipe-checklist.md | ||
| dns-filtering-parked.md | ||
| mcp-shortlist.html | ||
| python-split-recipes.md | ||
| shared-checkout-safety.md | ||
| shell-split-recipes.md | ||
| shell-split-verification.md | ||
| syncyomi-restore-runbook.md | ||