fix(security): restack retained evidence path revalidation on 28af0b

[seonghobae]

Purpose

Rebuild only the unique retained commercial-readiness evidence path-stability delta from #374 directly on current protected main 28af0b1c2e76d066a5d41ef1da56157209c89431 after #373 advanced protected truth. No predecessor checks, reviews, scanner results, or coverage evidence transfer.

readBoundedReport() already opens a bounded regular file through O_NOFOLLOW and validates path-to-descriptor plus descriptor pre/post-read identity. Accepted bytes now additionally require the pathname, after reading, to remain a bounded regular file on the same device/inode/size as the opened descriptor.

Test-first lineage

• 0b6c258d23e9d09dd7fe7cfbbf525818db46c286 — RED: final-path symlink/non-file/device/inode/size replacement must fail closed.
• 6bc22d8d17007175c85c8511f835c237b082e312 — GREEN: re-run lstat after the descriptor read and bind final pathname identity to the opened descriptor.
• e6349ccacd08b0bfeed6fbcb86e2df5b3050e1bc — current exact head; records POSIX.1-2024, Node filesystem, and NIST SSDF basis.

Fresh comparison against protected main is exactly three commits ahead, zero behind, changing only:

• scripts/normalize-commercial-readiness-evidence.mjs
• test/commercial-readiness-post-read-stability.test.ts
• docs/doctoring/evidence-path-stability.md

The #373 protected-main advance is preserved byte-for-byte because this successor was rebuilt from 28af0b1c2e76d066a5d41ef1da56157209c89431; no destructive history rewrite was used.

Evidence boundary

This is local retained-file integrity evidence only. It does not prove OS privilege isolation, remote provenance, production truth, release/deployment acceptance, customer/revenue evidence, or legal/licensing authority.

Do not merge until unchanged exact head e6349ccacd08b0bfeed6fbcb86e2df5b3050e1bc has fresh terminal-success application ci, reviewer-ci, eligible protected-base central Security Scan, exact configured 100% owned-production statement/branch/function/line coverage, and zero valid unresolved findings. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

No force update, self-approval, gate weakening, reviewer/secret invention, repair/self-modifying workflow, outbound-license decision, release, deployment, or fabricated production evidence is introduced.

Supersedes #374 and #371.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f6ba85e0-9fcd-4e61-8ff0-4d14d6c33869

📥 Commits

Reviewing files that changed from the base of the PR and between c9cf4c4 and 2743b41.

📒 Files selected for processing (3)

• docs/doctoring/evidence-path-stability.md
• scripts/normalize-commercial-readiness-evidence.mjs
• test/commercial-readiness-post-read-stability.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}