fix(analysis): report completed-file extraction progress

[SHAURYAKSHARMA24]

Summary

Publish monotonic progress from 35 to 70 as source files finish processing; reserve 75 for relationship resolution and 100 for completion. Reuse guarded lease checkpoints and keep full evidence.

Linked issue

Related to #511.

Scope

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

What changed

Publish monotonic progress from 35 to 70 as source files finish processing; reserve 75 for relationship resolution and 100 for completion. Reuse guarded lease checkpoints and keep full evidence.

Acceptance criteria completed

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

Testing performed

24 worker tests passed, including cancellation, lease loss, recovery, and completed-file progress; Ruff lint and format passed.

Current head: 4a11be6c1d0cd223809d76148b1aabd80e0f3cc7; 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

Payload bounding and large-browser benchmarks remain separately tracked in #506–#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: 4a11be6c1d0cd223809d76148b1aabd80e0f3cc7.

24 worker tests passed, including cancellation, lease loss, recovery, and completed-file progress; Ruff lint and format passed.

Payload bounding and large-browser benchmarks remain separately tracked in #506–#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.