Repository navigation
fix: unblock publication checks for native JavaScript validators - #4115
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. |
Collaborator
Author
|
The unchanged original @gitruck/gtrk-ai-drama 1.3.9 is now published and installable, verified 2026-10-28 10:43 UTC.
Scanner repair #123 is active through production adoption #4115. This resolves AI Drama's original upload. This issue remains open for gtrk-cover and the other unresolved original uploads reported here. |
This branch was successfully deployed
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
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.
What Problem This Solves
Fixes blocked publication checks for uploads whose JavaScript validators use statically provable native storage and function results.
User Impact
Adopts the reviewed scanner repair so unchanged eligible uploads can pass ordinary checks. Production activation and original-upload recovery are separate operations; no issue is automatically closed by this PR.
Why This Change Was Made
Consumes ClawScan #123 and adds its exact source-to-lock binding while retaining every prior diagnostic binding. Extends the existing matrix and updates the policy pin. Scanner budgets, models, reasoning, service tiers and installer verification remain unchanged.
Evidence
After: that same validator accepts the qualified source with its exact lock; unknown/cross-source locks remain rejected. The installed scanner fully inspects 3/3 original files, removing only three generated incomplete-reference rows and retaining all six missing-reference caveats. Other 29 originals retain full finding payloads and coverage counts; one evidenced Feishu reason refines to opaque_content while remaining partial under the same budget. All 30 suppression payloads/counts match.
sha256:de7f6f6f77a201dd0f4f02b0b8cbeca91f033e1a382db3993389756ca536fc18.ci:static,ci:types-build,ci:packages, explicit schema/CLI type checks, Convex typecheck and independent P0–P3 integration review passed.setTypeOfService EINVALin unchangedplaywright-local-convex.test.ts. Its candidate isolated runs also pass all three assertions but retain that error; one unchanged-main isolated run exits cleanly. Cause remains unproven; the full hosted unit gate must pass before merge. No assertion or error policy was weakened.Merge Danger
Door: two-way. Revert the source pin and its binding to roll back.
Blast Radius: publication. This changes the scanner source selected by publication workers; deployment and ordinary original-upload checks must be verified separately.