Check a project's status against artifacts, not commit messages

When a user asks 'what's going on' in a repo that has a dated plan or schedule doc, list each planned deliverable and check that its concrete artifact exists: the module file, the raw-data folder, the git tag for pre-registration, the decisions or roles doc. Commit messages and plan docs describe intent, and a quiet week only shows up when you compare them with the tree. Also check git branch -vv for '[gone]' upstreams (stale merged branches), and look at the author email on commits to main: a users.noreply.github.com address usually means a web-UI commit that skipped the PR flow. Finish with the nearest deadline and the critical-path items, not a full inventory.