fix(frameworks): stop gatsby and svelte prose from faking detection

[TBX3D]

No description provided.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@7ea1cd2). Learn more about missing BASE report.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #285   +/-   ##
=======================================
  Coverage        ?   55.09%           
=======================================
  Files           ?       81           
  Lines           ?     6872           
  Branches        ?        0           
=======================================
  Hits            ?     3786           
  Misses          ?     2816           
  Partials        ?      270           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

pr summary

3 files changed (+11 -3)

category	files
go source	3
tests	1

[vmfunc]

clean fix. the math checks out: after dropping the prefixes, gatsby needs ___gatsby or /page-data/ and svelte needs __svelte or svelte/internal, all of which only show up in a real bundle, and each still clears the 0.3 center on a single strong hit so recall on genuine pages holds. no false-negative regression that matters. /page-data/ over page-data.json is the better call too, its the actual served path structure, not a string prose can drop. in.