🛡️ Sentinel: [보안 향상] 검색엔진 인덱싱 방지 메타 태그 추가

[seonghobae]

🚨 Severity: LOW / ENHANCEMENT
💡 Vulnerability: 디렉토리 인덱싱을 위한 정적 HTML 파일들이 퍼블릭하게 서비스될 때 검색엔진에 의해 내부 파일 구조가 노출될 수 있는 위험(Information Exposure)이 존재합니다.
🎯 Impact: 의도치 않은 정보 누출로 인해 내부 파일 목록이 구글 등 검색엔진에 인덱싱될 수 있습니다.
🔧 Fix: 생성되는 HTML에 <meta name="robots" content="noindex, nofollow"> 태그를 추가하여 크롤러의 접근 및 인덱싱을 차단합니다.
✅ Verification: MainTest.kt의 테스트가 정상적으로 통과하며 생성된 HTML 파일에서 해당 메타 태그를 확인할 수 있습니다.

---

PR created automatically by Jules for task 18157264581451827063 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.

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head de3cc0a3c352a6e24c14c122dc92caa52506e745.

• Head SHA: de3cc0a3c352a6e24c14c122dc92caa52506e745

• Workflow run: 30424234101

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: de3cc0a3c352a6e24c14c122dc92caa52506e745
• Workflow run: 30424234101
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head de3cc0a3c352a6e24c14c122dc92caa52506e745.

• Head SHA: de3cc0a3c352a6e24c14c122dc92caa52506e745

• Workflow run: 30424234101

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[seonghobae]

Closing as superseded by draft canonical #349. The same robots directive is retained there under an accurate search-discoverability boundary: it does not block access and does not replace server-side protection. #349 remains blocked for post-#363 update, current Google Search Central APA 7 doctoring, changelog, product-level tests, exact-head checks, and independent approval. No evidence from this duplicate head is reused.

[google-labs-jules]

Closing as superseded by draft canonical #349. The same robots directive is retained there under an accurate search-discoverability boundary: it does not block access and does not replace server-side protection. #349 remains blocked for post-#363 update, current Google Search Central APA 7 doctoring, changelog, product-level tests, exact-head checks, and independent approval. No evidence from this duplicate head is reused.

Understood. Acknowledging that this work is now obsolete as it is superseded by canonical PR #349, and stopping work on this task.