Check README claims against code before rewriting the prose

When asked to make a README read less like AI-written text, check each factual claim against the repo before changing the wording. In a Databricks bundle project, the README still said the AI/BI dashboard had to be built by hand, but the latest commit had added it to databricks.yml as a resources.dashboards entry. The Limitations section also said a combined overtime + transfer option didn't exist, even though scenario S4 did. Run git show --stat HEAD and read the bundle config, test count and generated docs first, then rewrite. If a doc file is generated by a script that CI checks for drift, edit the template in the script, not the generated file.