Docs Health Check — stale files detected 2026-07-19 #1319

Executive Summary

Status: STALE_DOCS_FOUND
Stale files: 12

Key findings:

• Most stale file: petry-projects/TalkTerm/docs/ecc-for-bmad.md (115 days, owner not determinable from data)
• Largest cluster: petry-projects/google-app-scripts/docs/ — 8 files all last touched 2026-03-28, suggesting a bulk-generated doc set that has never been updated

Action required: Review and either refresh or archive stale documentation in google-app-scripts, broodly, and TalkTerm before these docs mislead contributors.

Stale Files by Repo

petry-projects/TalkTerm

petry-projects/google-app-scripts

petry-projects/broodly

Recommendations

1. petry-projects/google-app-scripts — docs/ (8 files) [LOW]
   All 8 files share the same last-modified date (2026-03-28), indicating they were generated together and never updated. The team owning this repo should audit whether project-scan-report.json and source-tree-analysis.md reflect current project structure. If the repo is inactive, archive the docs directory with a redirect notice. Urgency: LOW (113 days stale).

2. petry-projects/broodly — docs/architecture, docs/api, docs/adr [LOW]
   Three doc directories last touched 2026-03-29. The api and adr directories are especially sensitive — outdated API docs mislead integrators, and stale ADRs obscure why architectural decisions were made. The broodly team should verify these against current code or mark them as historical. Urgency: LOW (112 days stale).

3. petry-projects/TalkTerm — docs/ecc-for-bmad.md [LOW]
   Single file, 115 days stale. Determine if this is an active design doc or a one-off analysis; if the latter, move it to a docs/archive/ folder to prevent confusion. Urgency: LOW (115 days stale).