Repository navigation
feat(pr-pipeline): name merge.rung values merge and merge-reviewed - #11903
melodic-automation-lanes[bot] wants to merge 2 commits into
Conversation
Lane-Activity: work-resolve-issue/resolve-issue
|
claude-security-review reviewed Security review (incremental, since cb670cb)I found no security issues in this change. Scope. The only change since the last review is in
What changed. All five hunks are wording changes. The term "seam" now reads "hook", "notification hook", "notification path" or "the hook working as specified", in the escalation-record and HTTP-hook sections of the loop-lane contract. The facts stay the same:
Instruction-surface lens. No rule is deleted, narrowed or softened. Each sentence forbids and requires the same things as before. Neither file matches a Skip gate. Item 2 applies (no security-relevant surface): the change is prose-only and removes no control. No plugin manifest changed, so there are no critical-findings: 0 |
|
claude-review reviewed Incremental review (cb670cb → 9b6dfb3)Scope: What changed: a fix-docs pass swaps the word "seam" for "hook", "notification hook" or "notification path" in six places. None of these edits relates to the Findings (2, advisory):
Closing issue #7469: this increment adds or removes nothing against its three criteria. The earlier review covered them on the files this increment does not touch. Embedded text: none in the PR context file that tries to direct this lane. Spend: none in this increment (documentation only). |
Lane-Activity: pr-refine/fix-docs
|
Unattended merge: native auto-merge leaves this pull request unarmed at head |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Hold: replaced by an owner-login PR because the fix lane could not clear the failure. Releases when: the replacement merges and this PR is closed. |
…-read - An id inside a region span that the region pages omit is dropped only when its own read answers 404 or an expired record; a live record keeps it, and any other answer leaves the listing over, so it takes the one whole listing. Pages read one at a time skip the boundary entry when an artifact above it is deleted between reads (#10486); a skipped live FAIL plus a leftover surplus entry no longer passes the exact count. This covers the incremental and top-up paths, both through _near_expiry. NEAR_EXPIRY_ID_READ_CAP (34, the largest surplus behind #11903) bounds the id reads; cold_cost adds it (1,681 at 7,522 artifacts, 264 FAILs). - `.overcount-fallback` is created only when the over-count's whole listing starts paging, and holds its outcome: a refusal before paging leaves it free, and a later over-count's refusal keeps the DEADLINE_UNREADABLE prefix when that listing ran out of a caller's time, so verify-cap.mjs still skips the round. - The upward walk's docstring states the code's bound, surplus // LISTING_PAGE_SIZE + 2 pages; two tests reach the climb and the ups == 0 cutoff. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Superseded by #11914, which merged at 2026-11-01T13:34:20Z. |
Closes #7469
Summary
Opened by the work-resolve-issue lane. The run's own summary:
Not verified
off(orC2). That is a protected path this lane cannot write, and it is outside the issue's docs/ and plugins/ scope. A person can reword it to namemergeFix
Verification
The runner ran each check from the base copy against cb670cb:
The run reports:
Left out: the items under Not verified.
Related
#7469