fix: preserve exact Windows filesystem identities

[faizan-oai]

Summary

Severity: P1. Converting filesystem device and inode identifiers to JavaScript numbers can lose precision, allowing distinct Windows filesystem objects to compare equal during race checks. This keeps those identifiers exact.

Changes

• Request bigint filesystem metadata for multiscan lock and output checks.
• Request bigint filesystem metadata for runtime marketplace and credential-home checks.
• Compare exact device and inode identities throughout the validation window.
• Add regressions using colliding numeric projections of distinct bigint identities.

Testing

• pnpm run format — passed.
• pnpm run types — passed.
• pnpm run build — passed.
• Focused exact-identity regressions — 5 passed.
• git diff --check origin/main...HEAD — passed.

Risk and rollout

Behavior changes only where an identity exceeds JavaScript's safe integer range or a replacement race occurs. The comparison remains device-plus-inode based, with no persistence or schema change.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[mldangelo-oai]

Reviewed 2fc599068f95 for correctness and simplification. One optional simplification around the privacy-check call. Keep the exact bigint identity comparisons.

This is a non-blocking review. I did not run the full SDK suite or native Windows tests locally.

[mldangelo-oai]

Rechecked 2fc5990. The earlier simplification suggestions remain non-blocking. Approving the reviewed head.