A line diff on a config file tells you eleven lines changed. It does not tell you that a required key was removed, which is the only thing you wanted to know.
Flecto watches structured config files and reports the change in terms of what it did, not where it happened.
Classifying intent, not text
A lightweight NLP layer sorts each change into a category — schema modification, value drift, key removal — and describes it in plain English. The categories are chosen because they map onto how a change actually breaks things: a key removal is an outage, a value drift is usually a deploy, a schema modification is a review.
Zero dependencies on purpose
The package ships with no runtime dependencies. For a tool that installs into a developer toolchain, every transitive dependency is a supply-chain surface and an install-time cost that someone else pays. Keeping the footprint at zero means it can go into a project without an argument about it.
Zero-config too: install it and run it.