ponytail-reviewlisted

# Ponytail Review Run one bounded review of the requested diff. Do not edit files, persist a mode, install hooks, or turn this into a whole-repository audit unless the user explicitly asks for a wider scope. This skill is adapted from [`DietrichGebert/ponytail`](https://github.com/DietrichGebert/ponytail) version 4.9.0, commit `0a4dd63ad4541f4f655c4108a295916f3c1d8fda`. Its MIT license is stored beside this file. ## Establish the review base Name the exact base and head commits or state that the review covers an uncommitted working-tree diff. Read the repository rules and the product, architecture, and testing guidance that apply to the changed surface. Project requirements outrank this review. Treat required tests, documentation, validation, error handling, security controls, accessibility, calibration for real hardware, compatibility work, and explicitly requested behavior as protected scope. ## Look for avoidable complexity Check the changed flow for: - speculative abstractions, configuration, extension points, or wrappers with no current consumer; - code that duplicates an existing project pattern, standard-library feature, native platform capability, or already-installed dependency; - dependencies added for behavior that a small, clear local implementation already covers; - policy spread across callers that belongs at one cohesive boundary; - hidden side effects or extra public contracts created to save a few local lines; - dead flexibility and code that