Skip to content

Docs: маршрут дуального доказательства после мержа PR 559 и 560 - #567

Merged
lemone112 merged 1 commit into
mainfrom
docs/full-domain-dual-proof-559-560
Aug 10, 2026
Merged

lemone112 merged 1 commit into
mainfrom
docs/full-domain-dual-proof-559-560

Conversation

@lemone112

Copy link
Copy Markdown
Collaborator

Что

\docs/how-to/full-domain-dual-proof.md: раздел «Открытые PR» был журналом статуса Issue-графа (AGENTS.md запрещает коммитить такой статус). После мержа #559 (\628ec22d) и #560 (\

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

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: 59 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: 3f2d1c59-2526-451c-8050-f524f1e5453a

📥 Commits

Reviewing files that changed from the base of the PR and between 08b6f26 and 2ad36ea.

📒 Files selected for processing (1)
  • docs/how-to/full-domain-dual-proof.md

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

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2ad36eadcb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +183 to +184
На `main` приём полосы проверяет координаты до `checkout`: вход `expect_lanes`
в `verification-lanes.yml` обязателен (#560, `08b6f265`), полоса отвергает

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Обновите пины инвентаря после удаления предупреждения

После этой замены документ описывает маршрут как уже живущий на main после #559/#560, но ниже в «Граблях» остались значения инвентаря с 3ad5091e (284 и 3284dccf...), тогда как текущие пины в proof/region/v1/tests/test_build.py — ARB_TEST_COUNT_V1 = 293 и e61831a.... Удалённый блок раньше явно предупреждал, что эти числа устареют после мержа, а теперь оператор, чинящий пины по этому how-to, получит расходящиеся с кодом/тестами данные.

AGENTS.md reference: AGENTS.md:L47-L50

Useful? React with 👍 / 👎.

@lemone112
lemone112 merged commit 8ef36aa into main Aug 10, 2026
10 checks passed
@lemone112
lemone112 deleted the docs/full-domain-dual-proof-559-560 branch August 10, 2026 17:06
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