Skip to content

Keep parity candidates out of published package - #12

Merged
DennisSmolek merged 1 commit into
mainfrom
chore-cleanups
Jul 29, 2026
Merged

Keep parity candidates out of published package#12
DennisSmolek merged 1 commit into
mainfrom
chore-cleanups

Conversation

@DennisSmolek

Copy link
Copy Markdown
Member

Summary

  • move source-parity shader graphs and orchestration into a frozen bench-owned upscaler while preserving all benchmark identities
  • guard the built and packed library against candidate leakage, reducing dist/index.js from about 189 kB to 120 kB
  • verify the linked TSL guides graph through the packed npm artifact on a real GPU and graduate that surface from @experimental

Closes #2.
Closes #3.

Test plan

  • npm test (202 tests)
  • npm run typecheck
  • npm run lint
  • npm run build
  • npm run examples:build
  • npm run verify:packed-guides
  • npm run verify:packed-guides:gpu (16 ordered split frames, 2 backing textures, 0 monolithic fallbacks)
  • GPU smoke all three source-bundle candidates against rcas-fsr315-limiter

Made with Cursor

Preserve the source-style variants as a frozen bench fork and graduate the linked guides node after packed-package GPU verification.

Co-authored-by: Cursor <cursoragent@cursor.com>
@DennisSmolek
DennisSmolek merged commit e4c8179 into main Jul 29, 2026
1 check passed
@DennisSmolek
DennisSmolek deleted the chore-cleanups branch July 29, 2026 12:51
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.

Drop @experimental from the TSL guides node once an external consumer wires it Keep parity-candidate shader bundles out of the published build

1 participant