Skip to content

🎨 Palette: [μ ‘κ·Όμ„± κ°œμ„ ] HTML 리포트 ν…Œμ΄λΈ”μ˜ row header μ§€μ • - #995

Closed
seonghobae wants to merge 13 commits into
mainfrom
palette/html-report-row-headers-18030566109311953973
Closed

🎨 Palette: [μ ‘κ·Όμ„± κ°œμ„ ] HTML 리포트 ν…Œμ΄λΈ”μ˜ row header μ§€μ •#995
seonghobae wants to merge 13 commits into
mainfrom
palette/html-report-row-headers-18030566109311953973

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

πŸ’‘ What:

  • calibration_report_html.py 및 validation_report_html.py의 데이터 ν…Œμ΄λΈ” λ Œλ”λ§ μ‹œ row_header_column=0을 λͺ…μ‹œν•˜μ—¬ 첫 번째 μ‹λ³„μž 열이 <th scope="row">둜 λ Œλ”λ§λ˜λ„λ‘ μˆ˜μ •ν–ˆμŠ΅λ‹ˆλ‹€.

🎯 Why:

  • 슀크린 리더 μ‚¬μš©μžκ°€ λ³΅μž‘ν•œ 데이터 ν…Œμ΄λΈ”μ„ 탐색할 λ•Œ, 각 데이터 셀이 μ–΄λŠ ν–‰(ν•­λͺ©)에 μ†ν•˜λŠ”μ§€ λͺ…ν™•νžˆ 인식할 수 μžˆλ„λ‘ ν•˜μ—¬ μ›Ή 접근성을 ν–₯μƒμ‹œν‚€κΈ° μœ„ν•¨μž…λ‹ˆλ‹€.

πŸ“Έ Before/After:

  • μ‹œκ°μ  λ””μžμΈμ΄λ‚˜ λ ˆμ΄μ•„μ›ƒμ—λŠ” 변경이 μ—†μŠ΅λ‹ˆλ‹€. HTML λ§ˆν¬μ—… μƒμ˜ μ‹œλ§¨ν‹±(μ ‘κ·Όμ„± 속성)만 κ°œμ„ λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

β™Ώ Accessibility:

  • ν…Œμ΄λΈ” ν–‰μ˜ 식별 데이터λ₯Ό <td>κ°€ μ•„λ‹Œ <th>둜 μ œκ³΅ν•¨μœΌλ‘œμ¨ μ ‘κ·Όμ„± 보쑰 기기의 정보 ꡬ쑰 νŒŒμ•… λŠ₯λ ₯이 ν–₯μƒλ˜μ—ˆμŠ΅λ‹ˆλ‹€.

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

Summary by CodeRabbit

  • Accessibility
    • Improved HTML report tables by correctly identifying their first columns as row headers.
    • Updated calibration and validation reports for clearer navigation and interpretation in assistive technologies.

- 데이터 ν…Œμ΄λΈ”μ˜ 첫 번째 열에 `<th scope="row">`κ°€ μ μš©λ˜λ„λ‘ `row_header_column=0` 인자λ₯Ό λͺ…μ‹œν•¨
- μ‹œκ°μ  ν…Œμ΄λΈ” ꡬ쑰와 슀크린 리더 μŒμ„± 좜λ ₯ κ°„μ˜ 의미적 μ—°κ²°μ„± κ°œμ„ 
@google-labs-jules

Copy link
Copy Markdown

πŸ‘‹ 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

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

βš™οΈ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6f4e1944-34b6-4721-8d8e-c6ce08483845

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • πŸ” Trigger review

No actionable comments were generated in the recent review. πŸŽ‰

ℹ️ Recent review info
βš™οΈ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f8d99a59-e9f6-404b-871b-748532351e12

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 04d0bc2 and 2076282.

πŸ“’ Files selected for processing (2)
  • python/fast_mlsirm/scoring/essay/calibration_report_html.py
  • python/fast_mlsirm/scoring/essay/validation_report_html.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


πŸ“ Walkthrough

Walkthrough

Calibration and validation HTML report tables now pass row_header_column=0. This marks each table’s first column as the row-header column.

Changes

HTML report table rendering

Layer / File(s) Summary
Mark first columns as row headers
python/fast_mlsirm/scoring/essay/calibration_report_html.py, python/fast_mlsirm/scoring/essay/validation_report_html.py
The calibration task, rater, respondent, threshold, and trace tables, plus the validation metrics table, identify column 0 as the row-header column.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: βšͺ Minimal Β· up to 20762

The change adds semantic row headers to improve screen-reader navigation without altering visual layout or report behavior; no actionable merge-blocking risk remains after normal checks and review.

πŸš₯ Pre-merge checks | βœ… 5
βœ… Passed checks (5 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check βœ… Passed The title clearly describes the accessibility improvement by specifying row headers for HTML report tables, which matches the changes.
Docstring Coverage βœ… Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check βœ… Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check βœ… Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
πŸ“ Generate docstrings
  • Create stacked PR
  • Commit on current branch
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch palette/html-report-row-headers-18030566109311953973

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

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

@seonghobae
seonghobae enabled auto-merge (squash) August 18, 2026 20:11
seonghobae and others added 5 commits August 18, 2026 13:28
- 데이터 ν…Œμ΄λΈ”μ˜ 첫 번째 열에 `<th scope="row">`κ°€ μ μš©λ˜λ„λ‘ `row_header_column=0` 인자λ₯Ό λͺ…μ‹œν•¨
- μ‹œκ°μ  ν…Œμ΄λΈ” ꡬ쑰와 슀크린 리더 μŒμ„± 좜λ ₯ κ°„μ˜ 의미적 μ—°κ²°μ„± κ°œμ„ 

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 86f1bd7a1269fef1a2edb59d158134f1111b9584.

  • Head SHA: 86f1bd7a1269fef1a2edb59d158134f1111b9584

  • Workflow run: 32194301299

  • 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["Docs (2 files)"]
  S1 --> I1["operator or user guidance"]
  I1 --> R1["Review risk: Docs (2 files)"]
  R1 --> V1["docs review"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (2 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Test: test_scoring_essay_report_row_headers.py"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test: test_scoring_essay_report_row_headers.py"]
  R3 --> V3["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 86f1bd7a1269fef1a2edb59d158134f1111b9584
  • Workflow run: 32194301299
  • 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 86f1bd7a1269fef1a2edb59d158134f1111b9584.

  • Head SHA: 86f1bd7a1269fef1a2edb59d158134f1111b9584

  • Workflow run: 32194301299

  • 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["Docs (2 files)"]
  S1 --> I1["operator or user guidance"]
  I1 --> R1["Review risk: Docs (2 files)"]
  R1 --> V1["docs review"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (2 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Test: test_scoring_essay_report_row_headers.py"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test: test_scoring_essay_report_row_headers.py"]
  R3 --> V3["targeted test run"]
Loading

Copy link
Copy Markdown
Contributor Author

@opencode-agent Please re-review the unchanged exact head 86f1bd7a1269fef1a2edb59d158134f1111b9584. Repository CI, Security Scan, CodeQL, and Semgrep are terminal-success on this SHA. The current formal CHANGES_REQUESTED is tied to central dispatch run 32194301299, which ran on .github@b71a02a310e77f70c1e59f4719f6857cb33ca886 but ultimately ended cancelled after coverage evidence failed to publish. Please generate fresh same-head formal review evidence; do not reuse the cancelled run as current approval evidence.

seonghobae and others added 2 commits August 19, 2026 00:11
- 데이터 ν…Œμ΄λΈ”μ˜ 첫 번째 열에 `<th scope="row">`κ°€ μ μš©λ˜λ„λ‘ `row_header_column=0` 인자λ₯Ό λͺ…μ‹œν•¨
- μ‹œκ°μ  ν…Œμ΄λΈ” ꡬ쑰와 슀크린 리더 μŒμ„± 좜λ ₯ κ°„μ˜ 의미적 μ—°κ²°μ„± κ°œμ„ 

Copy link
Copy Markdown
Contributor Author

@opencode-agent Please re-review current exact head 8e9ff650578f1d30b28be3c6d6da7e9a87fce764. The existing REQUEST_CHANGES is anchored to predecessor 86f1bd7a1269fef1a2edb59d158134f1111b9584 / coverage run 32194301299. The current head restores the focused row-header regression, changelog fragment, and WCAG doctoring after a compatible branch update; current Security Scan, CodeQL, and Semgrep are successful while repository CI/coverage evidence must be assessed on this exact SHA. Please do not transfer predecessor-head evidence.

- 데이터 ν…Œμ΄λΈ”μ˜ 첫 번째 열에 `<th scope="row">`κ°€ μ μš©λ˜λ„λ‘ `row_header_column=0` 인자λ₯Ό λͺ…μ‹œν•¨
- μ‹œκ°μ  ν…Œμ΄λΈ” ꡬ쑰와 슀크린 리더 μŒμ„± 좜λ ₯ κ°„μ˜ 의미적 μ—°κ²°μ„± κ°œμ„ 

Copy link
Copy Markdown
Contributor Author

Superseded by #997. This branch repeatedly retained the two production row_header_column=0 call-site edits while later commits deleted the focused public regression, governed changelog fragment, and WCAG doctoring. The current head 306d675268e8e824afd2ce10367e470345bcac54 therefore no longer carries the evidence needed to prevent the accessibility regression from returning. #997 reconstructs the same bounded behavior from protected main with an explicit RED-only first commit, then will add the two production edits and evidence only after the regression is observed failing. Do not merge both lanes.

@seonghobae seonghobae closed this Aug 19, 2026
auto-merge was automatically disabled August 19, 2026 01:27

Pull request was closed

@google-labs-jules

Copy link
Copy Markdown

Superseded by #997. This branch repeatedly retained the two production row_header_column=0 call-site edits while later commits deleted the focused public regression, governed changelog fragment, and WCAG doctoring. The current head 306d675268e8e824afd2ce10367e470345bcac54 therefore no longer carries the evidence needed to prevent the accessibility regression from returning. #997 reconstructs the same bounded behavior from protected main with an explicit RED-only first commit, then will add the two production edits and evidence only after the regression is observed failing. Do not merge both lanes.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant