🛡️ Sentinel: [보안 개선] 파일 쓰기 시 원자적(Atomic) 교체 적용

[seonghobae]

• src/main/kotlin/html4tree/main.kt: write_index_file 함수에 ATOMIC_MOVE 적용 및 예외 시 fallback 처리 로직 추가.
• src/test/kotlin/html4tree/MainTest.kt: testWriteIndexFileAtomicMoveFallback 및 testWriteIndexFileDefaultFallbackLambda 등 예외 및 디폴트 파라미터 분기 커버를 위한 테스트 케이스 추가 (JaCoCo 100% 명령어 커버리지 달성).
• .jules/sentinel.md: 원자적 파일 교체와 관련된 학습 내용 기록.

---

PR created automatically by Jules for task 13656010329942583966 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 6dd9f025-cb1a-4aa5-b9aa-19062c7222c8

📥 Commits

Reviewing files that changed from the base of the PR and between a859a11 and a153851.

📒 Files selected for processing (3)

• .jules/sentinel.md
• src/main/kotlin/html4tree/main.kt
• src/test/kotlin/html4tree/MainTest.kt

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sentinel/atomic-move-13656010329942583966

---

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

[Copilot]

Pull request overview

This PR improves the robustness of index.html generation by attempting an atomic file replacement when writing index files, falling back safely when atomic moves aren’t supported. It also adds tests to cover the new fallback branches and records the related security learning in the Jules notes.

Changes:

• Update write_index_file to try StandardCopyOption.ATOMIC_MOVE first and fall back on AtomicMoveNotSupportedException.
• Add unit tests covering atomic-move fallback and default-parameter branches to maintain 100% JaCoCo coverage.
• Document the atomic replacement learning in .jules/sentinel.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/main/kotlin/html4tree/main.kt	Attempt atomic move for index replacement with a fallback path when unsupported.
src/test/kotlin/html4tree/MainTest.kt	Add tests to cover the new atomic-move fallback and default lambda branches.
.jules/sentinel.md	Record learning about atomic replacement; wording needs a small accuracy tweak.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[seonghobae]

Closing as superseded by draft canonical #296. The same atomic move and fallback branches are retained there under an accurate reliability contract. #296 must still update to post-#363 master, add deterministic all-old/all-new and cleanup/failure tests, complete JaCoCo branches, KDoc, APA 7 doctoring, changelog, exact-head checks, and independent approval. No result from this duplicate head is reused.

[google-labs-jules]

Closing as superseded by draft canonical #296. The same atomic move and fallback branches are retained there under an accurate reliability contract. #296 must still update to post-#363 master, add deterministic all-old/all-new and cleanup/failure tests, complete JaCoCo branches, KDoc, APA 7 doctoring, changelog, exact-head checks, and independent approval. No result from this duplicate head is reused.

Understood. Acknowledging that this work is now superseded by #296 and stopping work on this task.