chore: clean up untracked working-tree files - #134
Merged
Conversation
Four unrelated leftovers had been sitting untracked in the working tree. Resolving each rather than carrying them further. Deleted backend/debug-mastery.ts and debug-mastery2.ts. Standalone Prisma scripts from April that dump one hardcoded user's mastery state to the console. Nothing imports them and the UUIDs they target are stale. Deleted backend/src/config/cors-origin.ts and its spec. An unwired second implementation of CORS origin checking. main.ts imports buildStaticOrigins, createCorsOriginGuard and isOriginAllowed from ./config/cors, and nothing referenced createCorsOriginHandler. Keeping a duplicate of a security control next to the live one risks someone wiring up the wrong one later. The behaviour it was exploring, answering a disallowed origin by omitting CORS headers instead of returning 403, can be revisited in config/cors.ts directly if that turns out to be wanted. Gitignored .posthog-audit-checks.json. Regenerated wizard output, and the committed copy was already stale on SDK versions. Committed .claude/skills/audit and integration-nextjs-app-router. Same shape as the tracked integration-javascript_node skill; they were just never added. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves the four unrelated leftovers that had been sitting untracked in the working tree.
Deleted
backend/debug-mastery.ts,backend/debug-mastery2.tsStandalone Prisma scripts from April that dump one hardcoded user's mastery state to the console. Nothing imports them and the UUIDs they target are stale.
backend/src/config/cors-origin.ts+ specAn unwired second implementation of CORS origin checking.
main.tsimportsbuildStaticOrigins,createCorsOriginGuardandisOriginAllowedfrom./config/cors; nothing referencedcreateCorsOriginHandler. Keeping a duplicate of a security control beside the live one risks someone wiring up the wrong one later.The behaviour it was exploring, answering a disallowed origin by omitting CORS headers rather than returning 403, can be revisited in
config/cors.tsdirectly if that turns out to be wanted.Gitignored
.posthog-audit-checks.json— regenerated wizard output, and the copy on disk was already stale on SDK versions.Added
.claude/skills/audit/,.claude/skills/integration-nextjs-app-router/— same shape as the already-trackedintegration-javascript_nodeskill; they were just never added.Testing
bun run test: 7/7 turbo tasks pass. Backend is 650 tests, down exactly 4 from 654, which iscors-origin.spec.tsbeing removed. No other suite changed.🤖 Generated with Claude Code