Docs Health Check — stale files detected 2026-10-11 #2272

Executive Summary

Status: STALE_DOCS_FOUND
Stale files: 18

Key findings:

• Most stale: petry-projects/TalkTerm/docs/ecc-for-bmad.md, last updated 2026-03-26 (199 days). Owner can't be determined from the data. TalkTerm maintainers are the likely owners.
• google-app-scripts has the largest cluster: 8 files in docs/, all last updated 2026-03-28 (197 days). They look like one generated doc set (a project scan), left unrefreshed since then.
• broodly has 4 stale paths: architecture, api, adr (196 days) and runbooks (115 days).
• .github-private has 4 stale paths (99–126 days): token-report.md, actions-fleet-monitor.md, postmortems and evals.
• .github has 1 stale path (docs/bootstrap, 94 days), just past the threshold.
• No file is over 365 days stale, and 10 of the 18 are over 180 days.

Action required: Refresh or archive the google-app-scripts and broodly docs first, since they have been unchanged for about 197 days.

Stale Files by Repo

petry-projects/TalkTerm

petry-projects/google-app-scripts

petry-projects/broodly

petry-projects/.github-private

petry-projects/.github

Recommendations

1. google-app-scripts, full docs/ set (8 files)
   • Owner: google-app-scripts maintainers.
   • Action: Regenerate the project scan and the docs built from it, or archive the set if the project is dormant. If it is dormant, add a README pointer to the current source of truth.
   • Urgency: [MEDIUM] (197 days)
2. TalkTerm, ecc-for-bmad.md
   • Owner: TalkTerm maintainers.
   • Action: Check whether the content still matches the current BMAD/ECC setup. Refresh it if it does, or archive it or redirect to the current guidance if not.
   • Urgency: [MEDIUM] (199 days)
3. broodly, architecture, api and adr
   • Owner: broodly maintainers.
   • Action: Check them against the current code. Refresh the architecture and API docs. ADRs are historical records, so don't edit them. Add new ADRs or mark old ones superseded if decisions have changed.
   • Urgency: [MEDIUM] (196 days)
4. broodly, runbooks
   • Owner: broodly maintainers or on-call.
   • Action: Run through the runbooks and update any steps that no longer work.
   • Urgency: [LOW] (115 days)
5. .github-private, token-report.md and actions-fleet-monitor.md
   • Owner: org platform/automation maintainers.
   • Action: These look like generated reports. Regenerate them, or automate their refresh in a scheduled workflow.
   • Urgency: [LOW] (126 days)
6. .github-private, postmortems and evals
   • Owner: org platform/automation maintainers.
   • Action: Postmortems are historical records, so no refresh is needed. Confirm the directory is current and add any missing recent incidents. Update evals if the agent or prompt behavior has changed.
   • Urgency: [LOW] (99–108 days)
7. .github, docs/bootstrap
   • Owner: org standards maintainers.
   • Action: Check the bootstrap steps against current AGENTS.md standards. Re-validate soon, since it is close to the threshold.
   • Urgency: [LOW] (94 days)