test(e2e): cover graphs with more than 500 relationships

[SHAURYAKSHARMA24]

Summary

Add deterministic 80-source-module/8-package fixture with 640 sealed relationships, real-browser interaction regression, timing attachment and screenshot.

Linked issue

Related to #506.

Scope

Audit F11; baseline dev df0e82be3d7b2b7d846eefc1bcf82bde834936f2. This corrects independently verified existing behavior and advances the linked issue without adding product scope.

What changed

Add deterministic 80-source-module/8-package fixture with 640 sealed relationships, real-browser interaction regression, timing attachment and screenshot.

Acceptance criteria completed

Implementation and targeted regression coverage below. See remaining work for conditions not verified.

Testing performed

Actual Chromium fixture: 88 nodes / 640 relationships, graph ready in 2.108 seconds, edges withheld until focus, zoom/focus usable. Mutation disabling the limiter demonstrably removes the notice and draws all edges; source restored. No Firefox/Safari test.

Current head: 5e072c28b29ea27be5a7b440d232c12f92f44ef9; check snapshot appears below.

Screenshots

Local screenshots and browser measurements are recorded in the remediation delivery report where applicable. Backend-only changes use contract/regression evidence.

Security and data considerations

Preserves owner scoping, source provenance, sealed graph contracts and historical data. No security gate weakened. Rollback: revert this scoped commit; see issue for migration/deployment implications.

Dependencies and blocked work

Independent dev-based PR unless explicitly stated in the issue. No unmerged changes included.

Scope changes or remaining work

Runs through explicit E2E workflow with seeded disposable backend; Linux CI/browser run still required. Full API payload bounding remains #508.

Please review @parthrohit22.

Contributor checklist

• Targets dev; dedicated fork branch from latest dev; issue claimed.

• Scope/evidence recorded; unrelated changes and secrets excluded.

• Targeted validation results reported accurately.

• Required current-head CI and maintainer review complete.

Current-head remediation validation

Head: 5e072c28b29ea27be5a7b440d232c12f92f44ef9.

Actual Chromium fixture: 88 nodes / 640 relationships, graph ready in 2.108 seconds, edges withheld until focus, zoom/focus usable. Mutation disabling the limiter demonstrably removes the notice and draws all edges; source restored. No Firefox/Safari test.

Runs through explicit E2E workflow with seeded disposable backend; Linux CI/browser run still required. Full API payload bounding remains #508.

Checks at delivery: Repository Hygiene: SUCCESS; Analyze (javascript-typescript): SUCCESS; Analyze (python): SUCCESS; API Contract Drift: SUCCESS; Frontend: FAILURE; Backend: SUCCESS; Docker Build: SUCCESS; Marketing Site: SUCCESS; Prototype Browser Acceptance: SKIPPED; Vercel: FAILURE; CodeQL: SUCCESS. Required checks/reviews must pass before merge; deployment authorization was not granted.

[vercel]

@SHAURYAKSHARMA24 is attempting to deploy a commit to the parthrohit60-3117's projects Team on Vercel.

A member of the Team first needs to authorize it.

[SHAURYAKSHARMA24]

Additional validation

Threshold mutation check: changing 500 to 100000 in an isolated build produced 640 drawn edges and no large-graph notice, so the regression assertions detect removed limiting. Original source restored; no mutation committed.
No merge or public deployment performed.