Cal.com fixtures: task runners, Pages Router routes, stub guard (v0.1.3)#20
Merged
Conversation
…d (v0.1.3) Fixture-driven release from a real proof run against Cal.com (5,736 files, ~5s): - Custom task-runner infrastructure (Tasker classes, enqueue/task-processing verbs) now produces background_job behavior evidence; BullMQ-only patterns missed Cal.com's Tasker. Background Jobs: low/weak -> medium with worker evidence. - Next.js Pages Router API files (pages/api/**) are now extracted as routes; Cal.com's admin surface was invisible. Admin Permissions: missed -> medium with route evidence. - Disabled-endpoint stubs (handlers whose only behavior is a 404/501 response, e.g. community editions stripping features) are not route behavior and cannot confirm a concept. Guards the honest refusal on Cal.com's stubbed stripe/webhook.ts, which Pages Router extraction would otherwise have broken. - Perf: avoid a backtracking regex that took the Cal.com scan from ~4s to 135s. Three new fixtures encode all of the above. 107 tests passing. Version 0.1.3.
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.
Summary
Fixture-driven release from a real proof run against Cal.com (5,736 files scanned in ~5s). Every wrong or missing output became a fix plus a regression fixture.
Fixes
new Worker()/new Queue()patterns were recognized. Custom task-runner classes and enqueue/task-processing verbs now producebackground_jobbehavior evidence. Cal.com result: low/weak -> medium with worker evidence.pages/api/**) produced no route signals, hiding Cal.com's admin surface entirely. Pages Router API routes are now extracted. Cal.com result: not detected -> medium with route evidence.pages/api/stripe/webhook.tsas a handler that always returns 404. Naive Pages Router extraction would have turned that stub into route evidence and confirmed Billing Webhooks on a repo that cannot prove them. New rule: a disabled-endpoint stub (only behavior is a 404/501 response) is not route behavior. Billing Webhooks on Cal.com stays honestly hedged at low.\w*Tasker) that took the Cal.com scan from ~4s to 135s. Final: ~5s.Fixtures added
fixtures/jobs/tasker-is-background-jobsfixtures/nextjs/pages-api-admin-is-admin-permissionsfixtures/webhooks/stub-404-webhook-not-billingVerification
python -m build+twine checkpassVersion bumped to 0.1.3. No tag, no publish - awaiting approval.