Repository navigation
Description
Executive Summary
Status: STALE_DOCS_FOUND
Stale files: 15
Key findings:
- Most stale:
petry-projects/TalkTerm/docs/ecc-for-bmad.md— 178 days stale (last updated 2026-03-26); owner not determinable from available data - Largest cluster:
petry-projects/google-app-scripts/docs/— 8 files all stale 176 days, suggesting documentation was generated or mass-committed and never revisited - Secondary cluster:
petry-projects/broodly/docs/— 4 directories across architecture, api, adr, and runbooks, ranging 94–175 days stale
Action required: Review and either refresh, archive, or redirect all 15 stale doc files, prioritizing the google-app-scripts and broodly clusters as they represent the broadest coverage gaps.
Stale Files by Repo
petry-projects/TalkTerm
| File | Last Updated | Days Stale |
|---|---|---|
docs/ecc-for-bmad.md |
2026-03-26 | 178 |
petry-projects/google-app-scripts
| File | Last Updated | Days Stale |
|---|---|---|
docs/source-tree-analysis.md |
2026-03-28 | 176 |
docs/project-scan-report.json |
2026-03-28 | 176 |
docs/project-overview.md |
2026-03-28 | 176 |
docs/index.md |
2026-03-28 | 176 |
docs/development-guide.md |
2026-03-28 | 176 |
docs/deployment-guide.md |
2026-03-28 | 176 |
docs/component-inventory.md |
2026-03-28 | 176 |
docs/architecture.md |
2026-03-28 | 176 |
petry-projects/broodly
| File | Last Updated | Days Stale |
|---|---|---|
docs/architecture |
2026-03-29 | 175 |
docs/api |
2026-03-29 | 175 |
docs/adr |
2026-03-29 | 175 |
docs/runbooks |
2026-06-18 | 94 |
petry-projects/.github-private
| File | Last Updated | Days Stale |
|---|---|---|
docs/token-report.md |
2026-06-07 | 105 |
docs/actions-fleet-monitor.md |
2026-06-07 | 105 |
Recommendations
-
petry-projects/google-app-scripts— 8 stale files, 176 days [MEDIUM]
All docs appear to have been generated together (same date, same directory) and have had no follow-up commits. The owning team should determine whether these were auto-generated artifacts (archive or regenerate from source) or living documentation (refresh). Theproject-scan-report.jsonin particular should either be regenerated on a schedule or removed from version control. Suggested action: archive or automate regeneration. -
petry-projects/broodly— 4 stale directories, 94–175 days [MEDIUM]
Architecture, API, and ADR docs are 175 days stale while runbooks are 94 days stale — suggesting the repo is active but documentation is not being maintained alongside code. Runbooks are the most operationally critical; the broodly team should prioritize a runbook review pass first, then ADRs. Suggested action: refresh, starting withdocs/runbooksanddocs/api. -
petry-projects/TalkTerm— 1 stale file, 178 days [MEDIUM]
Single fileecc-for-bmad.mdis approaching the high-staleness threshold. Determine whether this is still relevant to active work (refresh) or was written for a feature/investigation that has concluded (archive). Suggested action: refresh or archive. -
petry-projects/.github-private— 2 stale files, 105 days [LOW]
token-report.mdandactions-fleet-monitor.mdare monitoring-output documents that likely need to be regenerated rather than manually edited. If these are produced by automated workflows, check whether the scheduled jobs are still running. Suggested action: verify and re-run generating workflows, or mark as deprecated if superseded.
Activity