Skip to content

docs: remove stale verification map and restore LCS/LPC boundaries - #334

Merged
lemone112 merged 3 commits into
mainfrom
agent/c2d-verification-map
Jul 16, 2026
Merged

docs: remove stale verification map and restore LCS/LPC boundaries#334
lemone112 merged 3 commits into
mainfrom
agent/c2d-verification-map

Conversation

@lemone112

@lemone112 lemone112 commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Outcome

  • removes the hand-written global verification index and points surviving claims at executable tests or source contracts
  • restores the canonical Labpics Colors Space and Labpics Perceptual Contrast names
  • narrows current CAM16-UCS, H-K and APCA-shaped code to characterized candidate components
  • adds anti-vacuum guards against promoting those components into complete LCS, LPC or readability evidence

Verification

  • cargo fmt --all -- --check
  • cargo test -p labcolors-core --locked: pass
  • npm test: 154 pass
  • npm run typecheck: pass
  • public claim anti-drift suite: 13 pass
  • git diff --check: pass

No product bytes or public function signatures are intentionally changed.

Summary by CodeRabbit

  • Документация

    • Уточнены определения LCS/LPC и границы текущих реализаций контрастных компонентов.
    • Обновлены пояснения о WCAG, APCA-shaped диагностике, CAM16/H-K и нейтральном оттенке.
    • Удалена устаревшая карта верификации и актуализированы ссылки на проверки.
    • Уточнены описания API, производительности и reference-проверок.
  • Тесты

    • Расширены проверки документации репозитория: выявляются неподтверждённые заявления, дрейф терминологии LCS/LPC и устаревшие сведения о производительности.

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 24 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fe2883f4-5faf-40c6-9044-236da8f70e50

📥 Commits

Reviewing files that changed from the base of the PR and between 2e5b7a5 and c114d4a.

📒 Files selected for processing (6)
  • README.md
  • crates/labcolors-core/src/lcs.rs
  • crates/labcolors-core/src/spaces/cam16.rs
  • docs/decisions/0003-hk-scope.md
  • docs/whitepaper.md
  • packages/colors/test/public-claims.test.mjs

Walkthrough

PR уточняет документацию о статусе LCS/LPC, контрастных компонентах и источниках verification checks. Также добавлены live-repository проверки дрейфа терминологии, ручных verification-утверждений и неподтверждённых runtime-оценок.

Changes

Контракт LCS/LPC и контрастные компоненты

Layer / File(s) Summary
Уточнение терминологии и статуса реализации
README.md, docs/whitepaper.md, docs/decisions/0003-hk-scope.md, crates/labcolors-core/src/lcs.rs, crates/labcolors-core/src/lpc.rs, crates/labcolors-core/src/semantic.rs, crates/labcolors-core/src/spaces/cam16.rs, packages/colors/README.md
Документация описывает LCS/LPC как незавершённые контракты, а текущие APCA-shaped, legacy-WCAG и H-K/CAM16 пути — как компоненты без полного LPC evaluator. Исправлены описания CAM16-UCS рескейлинга и влияния диагностик на WCAG verdict.

Источники reference и feasibility-проверок

Layer / File(s) Summary
Перенос ссылок на исполняемые проверки
crates/labcolors-core/README.md, crates/labcolors-core/src/lib.rs, crates/labcolors-core/src/golden_tests.rs, crates/labcolors-core/src/pair_label_tests.rs, crates/labcolors-core/src/reference_vectors_deep.rs, crates/labcolors-core/tests/reference_vectors.rs, docs/verification-map.md
Документация и комментарии указывают на Rust-тесты как источники WCAG 2.2 feasibility и reference checks; устаревшая карта верификации удалена.

Сканирование repository claims

Layer / File(s) Summary
Live-проверки документационных утверждений
packages/colors/test/public-claims.test.mjs, crates/labcolors-wasm/src/lib.rs
Добавлены сканеры ручной verification-прозы и LCS/LPC drift, расширен обход текстовых файлов и детектор runtime false claims; обновлён тест проверки документации runtime.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

🚥 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 Заголовок точно отражает удаление карты верификации и восстановление границ LCS/LPC.
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 unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent/c2d-verification-map

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

@lemone112

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review

1 similar comment
@lemone112

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 9

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/labcolors-core/src/semantic.rs`:
- Around line 133-137: Обновите rustdoc у `RoleChroma::Curve`, заменив
утверждение о «постоянной перцептивной красочности» описанием фиксированной
CAM16-UCS-координаты `M'` (`TINT_TARGET_MP`). Явно укажите, что эта координата
является выбранной design-policy величиной и не представляет универсальную шкалу
перцептивной цветности.

In `@crates/labcolors-core/src/spaces/cam16.rs`:
- Around line 244-247: Update the CAM16-UCS helper comment above lcs and lpc to
describe the transforms as analytically mutually inverse, not exactly or
bit-exactly invertible; explicitly state that binary64/f64 behavior is validated
within the 1e-12 tolerance used by ucs_rescale_round_trips.

In `@docs/decisions/0003-hk-scope.md`:
- Around line 90-95: В описании APCA/LPC переведите англоязычные термины на
русский: замените “channel power” на русский эквивалент, “readability-путь” на
“путь читаемости”, “legacy-WCAG luminance” на русское описание устаревшей
яркости WCAG, а также переведите “brightness” и “appearance” при их наличии в
этом фрагменте. Сохраните идентификаторы APCA, Ys, LPC и названия стандартов без
изменений.

In `@docs/whitepaper.md`:
- Around line 409-418: Переведите англоязычные термины в секции 3.1 на русские
формулировки: замените candidate, readability, legacy-WCAG luminance,
apparent-brightness, characterization-кандидаты, full LPC evaluator и shipped
продукт, сохранив только необходимые названия API и стандартов вроде LPC, APCA,
WCAG и CAM16.
- Around line 33-43: Переведите добавленный текст в docs/whitepaper.md на
русский, заменив англоязычные термины design-system, candidate contrast paths,
admitted contract, perceived-contrast solver и conformance естественными
русскими описаниями. Сохраните без перевода только имена LCS/LPC и ссылки на
исходники, не изменяя технический смысл разделов 1.2 и окружающего контекста.
- Around line 33-43: Перепишите определения `J'` и `s` в §1.2 как описания
текущих представлений и implementation inputs, убрав утверждения о
«перцептуальной яркости» и «насыщенности». Не представляйте `s` как CAM16
saturation или часть завершённого LCS/LPC-контракта; сохраните только смысл,
подтверждённый опубликованными данными и документацией `lcs.rs`.

In `@packages/colors/test/public-claims.test.mjs`:
- Around line 20-21: Расширьте регулярное выражение REPOSITORY_TEXT_EXT, добавив
поддерживаемые расширения jsx, go, java, kt и mdx, чтобы repository-wide
сканирование охватывало все форматы, указанные в правилах; сохраните
существующие расширения и текущую проверку границы имени файла.

In `@README.md`:
- Around line 5-8: Переведите описательный текст фрагмента README на русский,
заменив английское выражение “perceptual superiority” на «перцептуальное
превосходство». Сохраните технические идентификаторы LCS, LPC, CAM16, Oklab и
APCA-shaped без изменений.
- Line 232: Обновите русскоязычную формулировку в README.md, заменив
англо-русское «appearance-результат» на однозначное русское выражение, например
«результат модели внешнего вида», не изменяя остальную часть утверждения.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0d69508b-3ac5-4581-89d9-b0aac495578e

📥 Commits

Reviewing files that changed from the base of the PR and between f8b7a5d and 2e5b7a5.

📒 Files selected for processing (17)
  • README.md
  • crates/labcolors-core/README.md
  • crates/labcolors-core/src/golden_tests.rs
  • crates/labcolors-core/src/lcs.rs
  • crates/labcolors-core/src/lib.rs
  • crates/labcolors-core/src/lpc.rs
  • crates/labcolors-core/src/pair_label_tests.rs
  • crates/labcolors-core/src/reference_vectors_deep.rs
  • crates/labcolors-core/src/semantic.rs
  • crates/labcolors-core/src/spaces/cam16.rs
  • crates/labcolors-core/tests/reference_vectors.rs
  • crates/labcolors-wasm/src/lib.rs
  • docs/decisions/0003-hk-scope.md
  • docs/verification-map.md
  • docs/whitepaper.md
  • packages/colors/README.md
  • packages/colors/test/public-claims.test.mjs
💤 Files with no reviewable changes (1)
  • docs/verification-map.md

Comment thread crates/labcolors-core/src/semantic.rs
Comment thread crates/labcolors-core/src/spaces/cam16.rs Outdated
Comment thread docs/decisions/0003-hk-scope.md
Comment thread docs/whitepaper.md Outdated
Comment thread docs/whitepaper.md Outdated
Comment thread packages/colors/test/public-claims.test.mjs Outdated
Comment thread README.md
Comment thread README.md Outdated
@lemone112
lemone112 merged commit 1bbe173 into main Jul 16, 2026
10 checks passed
@lemone112
lemone112 deleted the agent/c2d-verification-map branch July 16, 2026 17:44
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