Skip to content

chore(repo): drop generated docs and QA report artifacts - #13

Merged
DavidBabinec merged 1 commit into
mainfrom
agent/cleanup-unwanted-docs
Aug 17, 2026
Merged

chore(repo): drop generated docs and QA report artifacts#13
DavidBabinec merged 1 commit into
mainfrom
agent/cleanup-unwanted-docs

Conversation

@DavidBabinec

@DavidBabinec DavidBabinec commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Removes generated documentation that was committed to the repo and is referenced nowhere in the codebase: STYLESHEETS_IMPLEMENTATION.md (implementation notes for porting the stylesheets feature from www to wp), reports/expert-tester-2026-05-08-1743.md (a QA session report), and the four screenshots under reports/screenshots/ that belong to that report. 535 lines across 6 files.

The legitimate docs stay: README.md, CHANGELOG.md, CONTRIBUTING.md, RELEASING.md, SECURITY.md, CODE_OF_CONDUCT.md, THIRD_PARTY_NOTICES.md, docs.md, docs/assets/, and packages/figma/README.md.

Verification

No code or build change, so there is nothing to run. Checked that nothing references the deleted paths before removing them:

grep -rn "STYLESHEETS_IMPLEMENTATION\|reports/expert-tester\|reports/screenshots" .   # no matches

Notes

Nothing stops reports/ coming back. The expert-tester tooling writes a dated report there by design, so the next QA run recreates it. Adding reports/ to .gitignore would make this stick, and is deliberately not part of this change.

Remove stray generated documentation that isn't referenced anywhere:
implementation notes and a QA session report with its screenshots.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@DavidBabinec
DavidBabinec merged commit 27315a1 into main Aug 17, 2026
6 checks passed
@DavidBabinec
DavidBabinec deleted the agent/cleanup-unwanted-docs branch August 17, 2026 18:07
@DavidBabinec DavidBabinec changed the title Clean up unwanted docs from the repo chore(repo): drop generated docs and QA report artifacts Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant