Fix warm binary request cache hits

[pirate]

Summary

• make absolute-path requests reuse the same validated projection as their cached basename record, using identical normalized path identity on read and write
• validate managed and global pnpm packages against the installed package.json version instead of accepting a desired literal override as observed state
• verify global package ownership through the real pnpm launcher target before trusting package metadata
• invalidate stale pnpm records when the cached version differs from the installed package

This fixes the root cache misses behind repeated ArchiveBox plugin installation checks. It does not add skip logic or parallelize the ordered installer.

Root causes

• request projections were written under basename identities but looked up using absolute request names
• the read and write sides normalized absolute paths differently
• literal pnpm version overrides could replace observed package metadata, allowing a stale image dependency to appear current
• global pnpm records skipped installed-version validation and did not verify package ownership
• none of these cases had real regression coverage

Verification

• absolute-path projection tests prove second real BinaryService requests, including a normalized .. path, never enter _load
• a real pnpm test installs zx 7.2.3 with a conflicting literal 999.0.0 override and pins package.json plus the returned Binary to 7.2.3
• a real pnpm-style global shell launcher test resolves its package target, ignores unrelated nearer metadata, and validates the owning package without spawning pnpm
• focused cache regressions: 4 passed
• changed-file prek hooks, ty, and pyright: passed
• full related pair before the final ownership tightening: 55 passed, 1 skipped; six macOS /var vs /private/var assertions also fail unchanged on pristine main

[cubic-dev-ai]

All reported issues were addressed across 5 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 2 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>