chore: remove internal artifacts and simplify repository tooling#15
Conversation
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 94056dffd3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
What changed
.gitignore,AGENTS.md, contributor guidance, and a CI test that rejects tracked local/ignored artifactsWhy
Generated development metadata and speculative planning material had been committed alongside product code. The Pages workflow and static frontend tests also accumulated historical complexity that was not needed by current users. Release tests additionally left hundreds of megabytes of ignored artifacts in the repository root.
Impact
The current product behavior remains unchanged. The repository is smaller, current-only deployment is easier to maintain, accidental local artifact commits now fail CI, and installer tests no longer pollute the checkout.
Validation
Passed locally on Windows:
npm run test:frontend— 4 passedtests/test_github_pages_demo.pyplus Windows README contract — 5 passedtests/test_public_mvp.py— 14 passedtests/test_installer_release.py— 13 passed;dist-releaseremained absentgit diff --check— passedFull local pytest result: 418 passed, 4 skipped, 12 failed. The 12 failures are existing Windows-platform assumptions in untouched areas: file-URI handling, POSIX path separator expectations, symlink privilege requirements, and missing Unix command-line tools. GitHub Actions remains the cross-platform release gate.