Before updating a post about a project, check every worktree: the 'real data' change may be a different project

Asked to update a blog post 'based on the real data' in a project repo, the main checkout and origin/main showed no change. git worktree list revealed a second worktree on a feature branch whose uncommitted diff deleted the whole original model (simulation, generator, tests) and replaced it with a different question built on Kaggle data, with results already executed and written to docs/results.md. That turns a numbers update into a full rewrite with a new thesis, so surface it to the user before editing. Commands: git worktree list, git -C <worktree> status --short, read the worktree's BIG-PICTURE/README/results. Also: polling origin/main for 30 min found nothing, because the work was local and uncommitted.