The headline of this release isn't a feature, it's a field test. A user ran ponytail across a from-scratch rewrite of a real system: nine phases, protocol plus desktop app plus simulator plus Raspberry Pi daemon plus ESP32 firmware. The verdict was "net win, kept it on the whole build," and across all nine phases "it never once trimmed a failsafe, validation, or auth check." It also flagged where the laziness needed a tighter leash. v4.4.0 is the result.
- Sharper rules from that feedback: hardware is never the spec ideal (leave the calibration knob), the one-runnable-check rule is now a headline ("lazy code without its check is unfinished"), and explanation you explicitly asked for isn't debt.
/ponytail-debt: harvests theponytail:shortcuts you've deferred into a ledger, so "later" doesn't quietly become "never."- A behavior-gate eval so those rules can't silently regress.
- A dark-background logo (community-contributed) and a cleaner README.
What's Changed
- feat: refine ruleset from a full-project field review by @DietrichGebert in #39
- feat: add ponytail-debt skill by @DietrichGebert in #40
- docs: commands reference + portability accuracy by @DietrichGebert in #41
- feat: add a dark-background logo by @DietrichGebert in #43
- docs: use the dark logo in the README header on dark themes by @DietrichGebert in #44
- chore: bump version to 4.4.0 by @DietrichGebert in #45
- chore: untrack one-off social images committed by mistake by @DietrichGebert in #46
Full Changelog: v4.3.0...v4.4.0