Skip to content

feat(research): expose explicit yield dimensions - #7092

Closed
ll7 wants to merge 11 commits into
mainfrom
issue-7090-research-yield-reporting-20260813
Closed

feat(research): expose explicit yield dimensions#7092
ll7 wants to merge 11 commits into
mainfrom
issue-7090-research-yield-reporting-20260813

Conversation

@ll7

@ll7 ll7 commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Refs #7090.

Summary

Extend the frozen research_yield_snapshot.v1 reporting contract with four explicit, query-defined
dimensions: duplicate/competing pull requests, post-merge repairs, admitted result packets, and
blocked-age categories. The report preserves each dimension's query, denominator, and complete
bucket counts instead of inferring research yield from live issue or pull-request state.

The v1 contract remains strict: older snapshots without the required dimensions block are
rejected. Generated reports remain scratch diagnostics and are not durable benchmark evidence.

Research and Evidence Boundary

  • Target question: can workflow throughput and answerability dimensions be reported separately
    without turning implementation activity into scientific progress?
  • Comparator/baseline: the versioned frozen snapshot and prior report categories; this slice adds
    reporting dimensions and does not compare experimental arms or rerun a campaign.
  • Evidence tier: diagnostic reporting-contract and fixture proof only.
  • Result classification: implementation proof accepted; no empirical result, benchmark ranking,
    evidence admission, or paper/dissertation claim is made.
  • Stop rule: reject unknown dimensions, fields, buckets, duplicate record IDs, malformed counts,
    denominator mismatches, and non-finite lag values before campaign, compute, or evidence admission.
  • Compute: no campaign, planner execution, SLURM submission, or generated evidence artifact was
    produced.

Changes

  • Added strict schema validation for the four explicit research-yield dimensions and their
    query/denominator/bucket contracts.
  • Added deterministic reporting for duplicate/competing PRs, post-merge repairs, admitted
    packets, and blocked-age categories.
  • Preserved frozen source SHA-256 binding and fail-closed handling of unknown or incomplete
    snapshots.
  • Added fixture and CLI coverage for complete dimensions, malformed fields, duplicate IDs,
    non-finite values, denominator mismatch, and legacy snapshots.
  • Updated docs/benchmark_campaign_manifest.md; production campaign-admission composition remains
    owned by friction: wire answerability into production campaign admission and complete research-yield dimensions #7090.

Domain-Aware Approval

  • Required for this PR: yes; the report can influence workflow and research-yield interpretation.
  • Domains reviewed: answerability/reporting semantics, evidence classification, and
    research-progress interpretation.
  • Status: pending maintainer domain-aware approval.
  • Approver/review source or waiver: no independent domain-aware approval is recorded by this
    implementation loop; maintainer/domain review remains pending.
  • Validity checklist:
    • Target claim/hypothesis: frozen research-yield reports expose query-defined workflow
      dimensions without inferring scientific progress from issue or PR state.
    • Comparator or split/evidence validity: the report preserves the frozen snapshot, source
      digest, explicit denominators, and closed bucket definitions; no experimental split or metric
      is changed.
    • Fallback/degraded exclusions: unknown dimensions, fields, buckets, duplicate records,
      malformed counts, non-finite lags, and denominator mismatches fail closed; no fallback or
      degraded evidence is admitted.
    • Claim boundary: diagnostic reporting-contract repair only; no benchmark, ranking, publication,
      or scientific-progress claim is established.
    • Implementation integrity vs experimental validity: executable contract proof is complete;
      domain review and any downstream research interpretation remain separate.

Validation / Proof

  • Exact head: 780377325d544464bdd5f2ec9566049f640523f4.
  • Base: a1892cf453973cd19e7bbba158a9f4132009bcee (origin/main), merged in cleanly with no conflicts.
  • Current-base delta: the intended four report/manifest/fixture/test paths only.
  • Focused yield and answerability suite: 31 passed.
  • Base-sensitivity selector: ordinary (check_base_sensitive_gates.py --pr 7092 reports no base-sensitive files).
  • Ruff check/format and git diff --check: passed.
  • Hosted CI is running for this refreshed head.

Downstream / Delivery Boundary

gate-verdict: accepted @ 780377325d544464bdd5f2ec9566049f640523f4
base-policy: ordinary-cas @ 780377325d544464bdd5f2ec9566049f640523f4
merge-ready: no (awaiting terminal CI only)

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Important

Review available on request

  • 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7d18e868-9b3b-4755-8fba-5976e6abda76


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.

@github-actions github-actions Bot added the review-bot-auto Managed label that routes code-bearing PRs to CodeRabbit. label Aug 13, 2026

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head self-review for d97684be52ca4942e3a59b1fccbba20e8b25ab6c.

No blocking findings for this bounded reporting-only slice. The implementation:

  • exposes four closed research-yield dimensions with explicit query text, denominators, and
    complete buckets;
  • rejects unknown dimension names, fields, buckets, missing dimensions, malformed counts, and
    denominator mismatches;
  • preserves source snapshot path and SHA-256 identity and renders definitions in Markdown;
  • does not infer counts from live issue/PR state and does not wire launch-gate behavior.

The 28-test focused suite, CLI smoke, Ruff check/format, docs proof-consistency, and exact diff
checks passed. The fixture/report output is implementation proof only, not benchmark or scientific
evidence. Domain-Aware Approval remains pending for this research-reporting surface.

@github-actions

Copy link
Copy Markdown

🔍 PR Contract Check Summary

Overall Status: 🟢 PASSED

Check Status Description
1. Closes-discipline ✅ PASSED Demand Refs #N for epic issues
2. Closure declaration ✅ PASSED Require Closes/Refs for title issues
3. State-refresh-only ✅ PASSED Reject docs/context state updates
4. Evidence hygiene ✅ PASSED Checks markers and provenance fields
5. Evidence writer usage ✅ PASSED Require the shared marked writer path
6. Successor discipline ✅ PASSED Require successor statement on multi-PR issues
7. Worker-lane label ⚪ None Label PRs from cheap worker lane
8. Placeholder docstring ratchet ✅ PASSED Reject NEW TODO/empty docstrings in added diff lines

ℹ️ Info

  • No worker-lane provenance detected.

This check is mechanized. Please resolve any blockers to pass CI.

@ll7

ll7 commented Aug 13, 2026

Copy link
Copy Markdown
Owner Author

Exact-head implementation gate for PR #7092.

  • Head: d97684be52ca4942e3a59b1fccbba20e8b25ab6c
  • Base: 2987578c7840eaac1bd172550607bc6a046fbfd0
  • Scope: reporting-only research-yield dimensions; no campaign launch, compute, evidence admission, or publication claim.
  • Hosted checks: 28 successes, 1 expected skip, 0 failures, 0 pending.
  • The frozen source snapshot, explicit query/denominator, complete bucket counts, and fail-closed unknown/malformed dimensions are appropriately bounded.
  • Domain-Aware Approval remains pending; implementation integrity is not experimental-validity approval.

Gate conclusion: implementation proof accepted for this exact head; merge remains blocked pending ordinary review and Domain-Aware Approval.

gate-verdict: accepted @ d97684b
merge-ready: no
domain-approval: pending

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head self-review for PR #7092.

  • Reviewed commit: fbb30293952fbbe80bfd36a8287d5e6566eddc81.
  • Base: 4a790accb05575707fe4d66f546ebb9e4bbbfd6.
  • Scope remains report-only: explicit frozen-snapshot research-yield dimensions; production
    admission and launch-gate wiring remain deferred.
  • Validation at this head: 28 focused tests passed, report CLI smoke passed with source SHA-256,
    Ruff check passed, Ruff format check passed, and git diff --check passed.
  • No implementation blocker found in this bounded slice.

Domain-Aware Approval remains pending for the research-yield classifications. This is not a
merge-ready, campaign-admission, benchmark-evidence, execution-authorization, or publication
approval.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head self-review for PR #7092 / issue #7090.

  • Reviewed head: ee908dbc25ec94d3d19e8dc65c750c79e200bff7.
  • Base: 4aac85935985434cf25c25442a1bc5bc216b78e3.
  • The report-only slice computes four explicit research-yield dimensions with closed query,
    denominator, bucket, and unknown-field contracts. It does not admit production results, gate
    launches, submit compute, or establish research claims.
  • Validation at this exact head: 28 focused tests passed; CLI smoke emitted
    research_yield_report.v1 with SHA256 6bebd421...70a7af; Ruff check, format, and diff checks
    passed.
  • No implementation blocker found in this slice. Domain-aware review remains pending; this is
    diagnostic reporting, not benchmark evidence or publication approval.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head self-review for PR #7092 / issue #7090.

  • Reviewed head: 0fc1d2b6bf450f9b609b1e7df16c4d0f9551f12e.
  • Base: ade42921d6b00406f69ae3a39352bff6fa66a53d.
  • The report-only slice computes four explicit research-yield dimensions with closed query,
    denominator, bucket, and unknown-field contracts. It does not admit production results, gate
    launches, submit compute, or establish research claims.
  • Fresh-base validation: 28 focused report tests passed after merging current origin/main; the
    prior CLI smoke, Ruff/format, docs, and diff proofs remain applicable to the unchanged slice.
  • No implementation blocker found in this slice. Domain-aware review remains pending; this is
    diagnostic reporting, not benchmark evidence or publication approval.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head self-review for PR #7092 / issue #7090.

  • Reviewed head: cd2b2ec2a9d554a41113fb02b6146c17ef39e49c.
  • Base: a956b839e877ce18d03a5aa7903ff923952547da.
  • The report-only slice computes four explicit research-yield dimensions with closed query,
    denominator, bucket, and unknown-field contracts. It does not admit production results, gate
    launches, submit compute, or establish research claims.
  • Fresh-base validation: 28 focused report tests passed after merging current origin/main; prior
    CLI smoke, Ruff/format, docs, and diff proofs remain applicable to the unchanged slice.
  • No implementation blocker found in this slice. Domain-aware review remains pending; this is
    diagnostic reporting, not benchmark evidence or publication approval.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head refresh review

  • Reviewed PR #7092 at head 65c169649917728c941736ba05d11a36052e28e8 against base 2cce5e2f0916524916a4592062e47b1b7b1dc433.
  • Scope remains four files: campaign-manifest guidance, the research-yield report, its answerability-focused tests, and the versioned fixture.
  • The implementation preserves frozen source identity, requires explicit query/denominator/bucket accounting, and rejects unknown or inconsistent dimensions.
  • Parent proof: 28 focused tests passed; report CLI smoke emitted all four dimensions and source SHA-256; Ruff check/format, docs proof, and git diff --check passed.
  • Final readiness: follow-up ok, checklist errors none; domain status is explicitly pending_domain_approval because this is research-yield reporting.
  • No benchmark, compute, evidence admission, publication, or merge was performed or inferred.

No blocking implementation findings at this exact head. Domain review remains required before merge readiness.

@ll7

ll7 commented Aug 14, 2026

Copy link
Copy Markdown
Owner Author

Exact-head refresh review

  • Reviewed PR feat(research): expose explicit yield dimensions #7092 at exact head 8f36d812e6eafdc37690a54f44aab58a615b73ba against live base
    c5d3bbacea0370233186bda929238486a92f4630.
  • Scope remains four files: campaign-manifest guidance, the research-yield report, its
    answerability-focused tests, and the versioned fixture.
  • The implementation preserves frozen source identity, requires explicit query/denominator/bucket
    accounting, and rejects unknown or inconsistent dimensions without inferring live state.
  • Delegated self-review found no blocker. It confirmed fallback, degraded, unavailable,
    diagnostic-only, failed, and not-run rows are not promoted into success evidence. Compatibility
    caveat: older v1 snapshots without dimensions are rejected by the strict contract.
  • Parent proof: 28 focused tests; report CLI smoke emitted all four dimensions and source SHA-256;
    Ruff check/format; docs proof; git diff --check; and full interim readiness with core and the
    required optional/predictive lane, ratchets, and clean-tree proof.

No blocking implementation findings remain at this exact head. Domain review remains required before
merge readiness.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

gate-verdict: accepted @ 6f6c7f7
merge-ready: no
pr-metadata: reconciled @ 6afa98db8e608f6afe7d7765b80b41694a25a084b135757224cc556bb8d9ef8c

Implementation review accepted for the reporting-only slice. The four explicit dimensions are query-defined source metadata and remain unable to authorize campaign admission or support a scientific result. The exact-head repair correctly rejects duplicate snapshot IDs, non-finite lag values, and malformed in-memory snapshots through the same validation path used for file-backed snapshots. Focused tests (31), CLI smoke, scoped Ruff/format, documentation/evidence integrity, and exact diff checks passed. Domain-aware approval remains pending, so no merge-ready label is applied.

@ll7

ll7 commented Aug 14, 2026

Copy link
Copy Markdown
Owner Author

Exact-head refresh review

  • Reviewed current PR feat(research): expose explicit yield dimensions #7092 head 6f6c7f71e418b04dfb411d6fc66a78d7552716c5 against live base
    c5d3bbacea0370233186bda929238486a92f4630.
  • The bounded four-file reporting slice preserves frozen source identity, explicit
    query/denominator/bucket accounting, and fail-closed unknown or inconsistent dimensions.
  • Preserved maintainer hardening adds duplicate record-ID rejection, finite non-negative lag
    validation, and validation for in-memory report callers; the current focused suite is 31 passed.
  • Parent proof on the current head: report CLI smoke emitted all four dimensions and source SHA-256;
    Ruff check/format and diff checks passed; full interim readiness including core and the required
    optional/predictive lane, ratchets, and clean-tree proof passed.
  • The prior 8f36d812 hosted snapshot had one aggregate failure amid superseded cancellations and
    is superseded; it is not current evidence. Domain review remains required.

No blocking implementation findings remain at this exact head.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head research-yield review

  • Reviewed PR #7092 at exact remote head 96be21e92734dfb3270f4a97f81def9216800147 against current origin/main 5c4f96468a2bacd3a04133df519f6d8756040073.
  • The report now keeps empirical answers, infrastructure/preflight throughput, explicit lag summaries, and four query-defined research-yield dimensions separate. Snapshot validation rejects duplicate records, non-finite lags, unknown dimensions/buckets/fields, and denominator mismatches rather than inferring values from live issue or PR state.
  • Focused research-yield/manifest tests passed 35. Full BASE_REF=origin/main scripts/dev/pr_ready_check.sh passed through core and optional lanes with a clean tree.
  • Current exact-head hosted checks are terminal green: 29 passing checks and 2 intentional skips.
  • gate-verdict: accepted @ 96be21e92734dfb3270f4a97f81def9216800147; merge-ready: no. Domain-aware approval remains pending for the reporting/evidence-boundary change.
  • This is diagnostic process reporting only: no campaign, planner, benchmark, scientific, productivity, or paper-facing result was generated or admitted.

@ll7
ll7 force-pushed the issue-7090-research-yield-reporting-20260813 branch from 96be21e to 3740a82 Compare August 14, 2026 08:27
@ll7

ll7 commented Aug 14, 2026

Copy link
Copy Markdown
Owner Author

gate-verdict: accepted @ 3740a82
merge-ready: no
domain-approval: pending
pr-metadata: reconciled @ ec7914024c05a9366d3dab27c4f1999df160820d535e20996468d70855602301

Exact-head research implementation review for PR #7092 / issue #7090:

  • Current base: 65ebc834e68e5a19a5a8711c521913dbfa023262.
  • Reviewed head: 3740a828b5bc8df42fc982f621d243ee34a0eca9.
  • Focused research-answerability suite: 31 passed; report CLI smoke emitted all four explicit dimensions and the frozen source SHA-256.
  • Ruff check/format, changed-file docs/evidence integrity, docs/proof consistency, evidence-registry ratchet (419=baseline), and git diff --check origin/main...HEAD: passed.
  • Full PR_READY_MODE=interim BASE_REF=origin/main scripts/dev/pr_ready_check.sh: passed on this exact head with clean-tree proof, core and optional/predictive lanes, and ratchets.
  • Hosted exact-head checks: 31 completed, 29 success, 2 expected skipped, no failure; the exact-head guard matched. The post-reconciliation body and PR-contract checks also passed.

The reporting slice preserves a strict, frozen-snapshot boundary: it does not infer live GitHub state or scientific value, and it rejects malformed or incomplete dimensions. No campaign, compute, evidence admission, benchmark result, publication, or paper/dissertation-facing claim was made. Domain-aware approval remains pending, so this review intentionally does not add merge-ready or authorize merge, compute, evidence promotion, or publication.

@ll7

ll7 commented Aug 14, 2026

Copy link
Copy Markdown
Owner Author

gate-verdict: accepted @ 3740a82
merge-ready: no
domain-approval: pending
pr-metadata: reconciled @ ed0d5e43309b01a33446ddfee3ca060b2425ea9eee5133e425331b51c6273899

Current exact-head refresh for PR #7092 / issue #7090:

  • Head 3740a828b5bc8df42fc982f621d243ee34a0eca9 remains against current base 65ebc834e68e5a19a5a8711c521913dbfa023262.
  • The current body remains within the reviewed four-file reporting-only scope and preserves the frozen-snapshot, explicit-dimension, fail-closed boundary.
  • Current hosted checks: 31 completed, 29 success, 2 expected skipped, no failure; post-body contract checks passed and the exact-head guard matched.
  • Prior local proof remains exact-head proof: 31 focused tests, CLI smoke, Ruff, docs/evidence and docs/proof checks, evidence-registry ratchet, full interim readiness, and diff check passed.

Domain-aware approval remains pending. This PR is not merge-ready and authorizes no merge, compute, evidence promotion, publication, or scientific claim.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Review gate

Accepted implementation proof for the exact current-base revision:

  • Head: 3740a828b5bc8df42fc982f621d243ee34a0eca9
  • Base: 65ebc834e68e5a19a5a8711c521913dbfa023262
  • Research-yield/answerability focused tests: 31 passed.
  • BASE_REF=origin/main scripts/dev/pr_ready_check.sh: passed with a clean stamp; optional lane and all ratchets passed.
  • Hosted checks for this head: 34 total, 32 success, 2 skipped, and no failures.

The implementation gate is accepted at this exact head. This remains merge-ready: no: the change is diagnostic process reporting, domain-aware approval remains required, and the report cannot authorize campaigns or establish scientific value. No benchmark execution, compute, evidence admission, publication claim, or merge authorization is inferred from this review.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Review evidence correction

The exact-head implementation review remains valid at 3740a828b5bc8df42fc982f621d243ee34a0eca9 against 65ebc834e68e5a19a5a8711c521913dbfa023262.

The canonical latest-run REST monitor now reports 31 checks, 29 success, 2 skipped, 8 superseded reruns, and overall success. The raw check-run total includes superseded contract reruns; the PR body records the canonical latest-run count. merge-ready: no remains unchanged: domain-aware approval is pending, and no campaign, compute, evidence admission, or scientific claim is authorized.

@ll7

ll7 commented Aug 14, 2026

Copy link
Copy Markdown
Owner Author

Exact-head audit handoff

Proof

  • Focused answerability/yield suite: 31 passed.
  • Issue-selected research_yield or answerability suite: 33 passed, 8208 deselected.
  • Current-main regression slice: 31 passed.
  • Report CLI help, two-file docs/evidence integrity, Ruff check/format, and git diff --check passed.
  • Full advisory readiness passed with clean-tree stamp output/validation/pr_ready/review-pr-7092-live-20260815.json; core, optional/predictive, and ratchet lanes passed.

Boundary and disposition

This is a frozen-snapshot research-process/reporting contract. It does not infer live GitHub or
campaign state and does not establish a scientific result. No campaign, compute, evidence
admission, publication claim, dissertation admission, or issue closure was performed. Domain-aware
approval for the reporting/evidence-boundary semantics remains pending; #7090 and #7031 retain
the downstream admission and answerability-workflow gates.

gate-verdict: accepted @ 52c8693f1b1729e2f82ee3c7ae0ee01d21640196

merge-ready: no

pr-metadata: reconciled @ 44c58a040f36a28fc27c04784f4fc50527b2ef507e449d1303455161adf0e35f

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head review: #7092

  • Reviewed head: 52c8693f1b1729e2f82ee3c7ae0ee01d21640196
  • Current base used for local proof: origin/main at 50a511d2336c37ae3957660a0141494d516be668
  • Scope: reporting/process support for explicit research-yield dimensions; this does not establish a scientific, benchmark, or paper-facing result.

Evidence at this exact head:

  • Focused tests: 62 passed (tests/benchmark/test_research_answerability.py and tests/docs/test_next_issue_shortlist.py).
  • Ruff, format, and git diff --check: passed.
  • Final scripts/dev/pr_ready_check.sh against the current origin/main: passed with a clean tree. The readiness stamp records base 50a511d2, head 52c8693f, and status passed.
  • Hosted checks for the exact head: terminal green; the known skipped checks are non-blocking, and superseded duplicate contract runs were cancelled.
  • No unresolved, non-outdated review threads were found.

Decision boundary:

  • Domain approval remains pending.
  • No campaign, compute, benchmark-evidence, or paper-claim admission is implied by this review.
  • merge-ready: no until the domain owner accepts the reporting contract and the PR is explicitly promoted.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head review: #7092

  • Reviewed PR head: 1ecd16c3f0cfa0378eef48f6962eeb68b5572726
  • Current base: origin/main=59e7f9e9ca4898dcdb977b8809e6ccedfc434601
  • Local final readiness: passed with a clean tree, current-base stamp, core and optional/predictive
    lanes, coverage diagnostics, TODO-docstring and broad-exception ratchets.
  • Focused proof: 62 answerability/yield and current-main shortlist tests; report CLI JSON/Markdown
    generation from the frozen fixture; docs/evidence integrity; docs proof consistency; Ruff,
    format, and diff checks passed.
  • Hosted exact-head CI: terminal success with 29 successful checks and 2 expected skips; expected
    head matched and no superseded run was used as evidence.

The report preserves explicit query-defined dimensions and source snapshot identity. It does not
run a campaign, establish a scientific or benchmark result, rank planners, promote evidence, or
admit paper, visual, or dissertation claims. Fallback/degraded/blocked/unavailable states remain
explicit boundaries.

Domain-aware approval is still pending. merge-ready: no; no merge or scientific-admission
decision is made by this review.

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Reviewed PR #7092 / issue #7090 at exact live head 1ecd16c3f0cfa0378eef48f6962eeb68b5572726 against current origin/main 59e7f9e9ca4898dcdb977b8809e6ccedfc434601.

Exact-head implementation and reporting-boundary review:

  • Focused answerability/yield suite: 31 passed.
  • Current-main regression slice tests/docs/test_next_issue_shortlist.py: 31 passed.
  • Frozen-snapshot dimension vocabulary, query/denominator/bucket checks, finite-lag validation,
    duplicate-record rejection, CLI help, docs/evidence integrity, evidence-registry ratchet,
    Ruff, format, and git diff --check passed.
  • Full PR_READY_MODE=final core and optional readiness passed with a clean exact-head stamp.
  • Hosted exact-head CI is terminal success: 31 checks, 29 success, 2 skipped, no failures,
    expected-head match true.

Research/evidence boundary accepted for implementation integrity only: this reports explicit
process/evidence-readiness dimensions from a frozen snapshot. It does not reconstruct live issue,
PR, campaign, planner, or metric state; run campaigns; submit compute; admit evidence; close
issues; publish; or establish scientific, benchmark, planner, paper, or dissertation results.
Fallback, degraded, unavailable, blocked, and diagnostic-only states remain explicit.

Domain-aware approval remains pending for evidence classification, experimental comparison,
benchmark interpretation, and paper-facing claim boundaries. Counts must not be promoted into
scientific progress or empirical answers without the required domain decision.

gate-verdict: accepted @ 1ecd16c
pr-metadata: reconciled @ c0795d9f360b7377c1ea4cc12edb003b759db90bab11d3069b38e084de4230ec
merge-ready: no

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Reviewed PR #7092 / issue #7090 at exact live head 5f18e9a4c1a0afb4a1aa3b8282a2b8d82f412cdb against current origin/main 60124e812c693a8b14f0130ed7565f11588cc9ee.

Exact-head implementation and reporting-boundary review:

  • Focused answerability/yield suite and current-main regression slice: 62 passed.
  • Frozen-snapshot dimension vocabulary, query/denominator/bucket checks, finite-lag validation,
    duplicate-record rejection, CLI help, docs/evidence integrity, evidence-registry ratchet,
    Ruff, format, and git diff --check passed.
  • Full PR_READY_MODE=final core and optional readiness passed with a clean exact-head stamp
    output/validation/pr_ready/review-pr-7092-20260815c.json.
  • Hosted CI for the refreshed head must settle before final gate evaluation.

Research/evidence boundary accepted for implementation integrity only: this reports explicit
process/evidence-readiness dimensions from a frozen snapshot. It does not reconstruct live issue,
PR, campaign, planner, or metric state; run campaigns; submit compute; admit evidence; close
issues; publish; or establish scientific, benchmark, planner, paper, or dissertation results.
Fallback, degraded, unavailable, blocked, and diagnostic-only states remain explicit.

Domain-aware approval remains pending for evidence classification, experimental comparison,
benchmark interpretation, and paper-facing claim boundaries. Counts must not be promoted into
scientific progress or empirical answers without the required domain decision.

gate-verdict: accepted @ 5f18e9a
pr-metadata: reconciled @ 7584bf6af4f3a3b82d6c514bfffaf000ff75750e2ac3edf1810f265f2852ebad
merge-ready: no

@ll7

ll7 commented Aug 15, 2026

Copy link
Copy Markdown
Owner Author

Exact-head audit handoff

Proof

  • Focused/current-base answerability and yield suite: 62 passed.
  • Shared repository contract bundle: 63 passed.
  • Benchmark transition/lazy-import slice: 31 passed.
  • Report CLI help and JSON/Markdown generation passed, including source snapshot SHA and explicit yield dimensions.
  • Ruff check/format, four-file docs/evidence integrity, docs/proof consistency, evidence-registry ratchet (419/419), and git diff --check passed.
  • Final readiness passed with clean-tree stamp output/validation/pr_ready/review-pr-7092-current-20260815-v2.json, recorded at 2026-08-15T10:24:23.113949+00:00 UTC.
  • Fresh exact-head hosted checks: 31 total, 29 success, 2 skipped; pr-contract-check run 31879439295 and pr-body-contracts run 31879437306 completed successfully.

Boundary and disposition

This is a frozen-snapshot research-process/reporting contract. It does not infer live GitHub or
campaign state and does not establish a scientific result. The implementation exposes explicit
research-yield dimensions while production campaign admission remains deferred to #7090 and
#7031. No campaign, compute, evidence admission, publication claim, dissertation admission, or
issue closure was performed. Domain-aware approval for the reporting/evidence-boundary semantics
remains pending.

gate-verdict: accepted @ 5f18e9a4c1a0afb4a1aa3b8282a2b8d82f412cdb

merge-ready: no

pr-metadata: reconciled @ de84a31702bc5b989ff1f4c7bfbe6e9b87f9202e303510dc37db0773d686eab3

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Terminal exact-head review: PR #7092 / issue #7090

Reviewed the current implementation at exact head e0f7354e0d1499cc1f4ebe5dc35b8a4c2708f5e8 against current origin/main=752e05f5574543bae4fbbde61be7ff79f501d9d9.

Implementation evidence:

  • The linked worktree is clean and the diff remains limited to the four intended frozen-snapshot reporting, fixture, test, and documentation paths.
  • Current changed report/answerability validation passed 31 tests.
  • Source-backed CLI generation emitted all four explicit query-defined dimensions, preserved the frozen source SHA-256, and generated both JSON and Markdown outputs.
  • The prior shared contract and benchmark transition/lazy-import bundles remain 63 and 31 passed respectively; Ruff, formatting, docs/evidence integrity, proof/catalog consistency, evidence-registry ratchet 419/419, and diff checks passed.
  • Full BASE_REF=origin/main PR_READY_MODE=final PR_READY_ADVISORY=1 scripts/dev/pr_ready_check.sh passed at 2026-08-15T16:59:33.941743+00:00 on this exact head and current base with a clean tree, core/optional lanes, and ratchets. Stamp: output/validation/pr_ready/review-pr-7092-current-20260815-v2.json.
  • Hosted checks are terminal and healthy: 31 total, 29 successful, 2 intentional skips, 0 pending, 0 failed; 2 superseded historical runs are excluded by the queue classifier.
  • Base freshness is fresh and the review-thread audit is complete with 0 unresolved threads.
  • PR metadata is reconciled at d01c4935b0ed173b7b685766b8d77fcde29b01393b57d446e65c17bd44bb0f19.

The explicit query/denominator/bucket reporting contract and fail-closed snapshot validation are accepted for the recorded diagnostic scope. Domain-Aware Approval remains pending for answerability/reporting semantics, evidence classification, and research-progress interpretation. The report does not infer live workflow state or scientific progress, and this review establishes no empirical result, benchmark ranking, evidence admission, publication, compute, or paper-facing claim.

gate-verdict: accepted @ e0f7354
pr-metadata: reconciled @ d01c4935b0ed173b7b685766b8d77fcde29b01393b57d446e65c17bd44bb0f19
merge-ready: no

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head research-result/reporting review

Reviewed PR #7092 / issue #7090 at exact head ba2f029042d55833ddff192749dfe0ef43574ab2
against current origin/main 9b96aac9cf7a1a190662d6a499fcbbffbd0b8a77.

  • The isolated worktree was refreshed by merging the live base; the current-base delta remains
    exactly the four report/manifest/fixture/test paths.
  • Focused yield/answerability proof passed: 31 tests. Related manifest, campaign-runner, and
    benchmark lazy-import regression proof passed: 28 tests.
  • The CLI emitted all four explicit query-defined dimensions and preserved frozen source SHA-256
    6bebd421e7eaaa74883b2a9a6c477357cfe43ac90704050a342c4fd41070a7af; JSON/Markdown outputs
    remain scratch diagnostics.
  • Final readiness passed at 2026-08-16T13:57:59.133097+00:00 UTC with a clean tree, exact
    base/head, core and optional/predictive lanes, ratchets, and diff checks. Metadata was
    reconciled through REST with digest 1b071f64ddf0ebaaee649e16c4ab7695127a4d1bf14e9046136fbb5aed8bc296.

Implementation integrity is accepted at this exact head. This remains diagnostic workflow
reporting only: it does not infer scientific progress from issue/PR state and establishes no
benchmark ranking, empirical result, evidence admission, publication, or paper-facing claim.

Domain-aware approval remains pending. This review does not add merge-ready, authorize a
campaign, or promote generated report output to durable evidence.

gate-verdict: accepted @ ba2f029042d55833ddff192749dfe0ef43574ab2
pr-metadata: reconciled @ 1b071f64ddf0ebaaee649e16c4ab7695127a4d1bf14e9046136fbb5aed8bc296
merge-ready: no
compute: none

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head research-result/reporting review — PR #7092

  • Reviewed head: 379e848bbce84742e887f4c7bf9e9c394c25f448.
  • Reviewed base: 462032df2abc3e086655935288c806b9df8bda2b (origin/main).
  • Rebased/merged cleanly onto current main. The 4-path diff remains diagnostic research-yield reporting infrastructure.
  • Local validation: 31 focused yield/answerability tests passed. Ruff check and format passed. git diff --check passed.
  • Domain-aware approval: pending maintainer decision.
  • Reconciled PR metadata: pr-metadata: reconciled @ 4142fc0eb94c1b27881bde286b60ba437318a3ee07bc6ac38f269220caa88c54.

gate-verdict: accepted @ 379e848bbce84742e887f4c7bf9e9c394c25f448
merge-ready: no (domain-aware approval pending)

@ll7

ll7 commented Aug 17, 2026

Copy link
Copy Markdown
Owner Author

Maintainer Decision Required

What is complete:

  • Refreshed against current main (462032df2abc3e086655935288c806b9df8bda2b) at exact head 379e848bbce84742e887f4c7bf9e9c394c25f448.
  • Full local test suite (31 passed) and linting passed cleanly.
  • PR metadata reconciled at 4142fc0eb94c1b27881bde286b60ba437318a3ee07bc6ac38f269220caa88c54.

What is missing for merge:

  • Domain-Aware Approval for Research Yield Dimensions: This PR extends the research yield reporting schema with four explicit dimensions (duplicate/competing PRs, post-merge repairs, admitted result packets, and blocked-age categories).
  • Action Required by Maintainer:
    1. Review the reporting contract in scripts/analysis/report_research_yield.py and tests/fixtures/research_yield_snapshot.v1.json.
    2. Confirm whether these four explicit dimensions align with desired research progress tracking.
    3. If approved, submit a review comment with domain-decision: approved @ 379e848bbce84742e887f4c7bf9e9c394c25f448.
    4. Remove decision-required and apply merge-ready when ready.

@ll7 ll7 added the decision-required Author input needed; not yet prepared as a decision packet label Aug 17, 2026
@ll7

ll7 commented Aug 18, 2026

Copy link
Copy Markdown
Owner Author

Exact-head review: PR #7092 / issue #7090

  • Reviewed head: 780377325d544464bdd5f2ec9566049f640523f4
  • Base: a1892cf453973cd19e7bbba158a9f4132009bcee (origin/main), merged in cleanly (no conflicts)
  • Scope verified against the PR body: exactly four files — scripts/analysis/report_research_yield.py,
    tests/benchmark/test_research_answerability.py, tests/fixtures/research_yield_snapshot.v1.json,
    docs/benchmark_campaign_manifest.md.

Why this is not author-reserved

The change is diagnostic workflow tooling. It adds strict schema validation and rendering for four
closed, query-defined process dimensions (duplicate/competing PRs, post-merge repairs, admitted
result packets, blocked-age buckets) read from an already-frozen research_yield_snapshot.v1. It
edits no claim ledger, no manuscript or dissertation prose, no locked evidence record, and no
preregistration; it admits no evidence and changes no benchmark metric, split, planner, or scoring
rule. It changes no orchestrator authority or auto-merge behavior. report_research_yield.py is not
invoked by any workflow, gate, or check — its only reference in the repository is the example command
in docs/benchmark_campaign_manifest.md — so it cannot decide what is admitted; it only reports
counts the snapshot already declares. Every added code path is fail-closed (unknown dimensions,
unknown fields, unknown/missing buckets, duplicate record IDs, non-integer or negative counts,
non-finite lag values, and denominator/bucket-sum mismatches all raise). The admitted_result_packets
dimension is a count copied from the frozen snapshot, not an admission decision. The docs change
records the reporting contract without asserting any result. The decision-required label was
conservative; the residual uncertainty here is reducible by review, so it is being removed.

Validation at this exact head

  • Focused answerability/yield suite: 31 passed.
  • Downstream check: no workflow, script, or gate consumes report_research_yield.py.
  • ruff check, ruff format --check, git diff --check: passed.
  • check_base_sensitive_gates.py --pr 7092: gate_required: false (selector ordinary).
  • check_docs_evidence_integrity.py --base-ref origin/main: 4 changed files passed.
  • Unresolved review threads: 0. Requested reviewers: 0.
  • PR body reconciled to this head before this review.
  • Hosted CI at this head is queued, not green: at review time the repository had 100+ queued and
    15 in-progress Actions runs, and none of this PR's 25 checks had started. That is runner
    starvation, not a defect of this PR.

Remaining gate

Only terminal green CI at 780377325d544464bdd5f2ec9566049f640523f4. No further push is planned, so
the gate-verdict trailer below stays current at that exact head. decision-required is removed
because the domain question it encoded is answered above; merge-ready is intentionally not
applied yet and is the single remaining action once checks conclude green.

Claim boundary unchanged: diagnostic reporting contract only. No campaign, compute, SLURM
submission, evidence admission, publication, ranking, or scientific-progress claim is made or
authorized by this review. Merge authority remains with the guarded merger.

gate-verdict: accepted @ 780377325d544464bdd5f2ec9566049f640523f4

base-policy: ordinary-cas @ 780377325d544464bdd5f2ec9566049f640523f4

pr-metadata: reconciled @ 3158fb64cf5d60ce781c2ae4d126f989c212de96932f2f1cd0b8df27edbdb18c

merge-ready: no (awaiting terminal CI only; not a domain block)

@ll7 ll7 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Exact-head review: PR #7092 / issue #7090

  • Reviewed head: 780377325d544464bdd5f2ec9566049f640523f4
  • Base: a1892cf453973cd19e7bbba158a9f4132009bcee (origin/main), merged in cleanly (no conflicts)
  • Scope verified against the PR body: exactly four files — scripts/analysis/report_research_yield.py,
    tests/benchmark/test_research_answerability.py, tests/fixtures/research_yield_snapshot.v1.json,
    docs/benchmark_campaign_manifest.md.

Why this is not author-reserved

The change is diagnostic workflow tooling. It adds strict schema validation and rendering for four
closed, query-defined process dimensions (duplicate/competing PRs, post-merge repairs, admitted
result packets, blocked-age buckets) read from an already-frozen research_yield_snapshot.v1. It
edits no claim ledger, no manuscript or dissertation prose, no locked evidence record, and no
preregistration; it admits no evidence and changes no benchmark metric, split, planner, or scoring
rule. It changes no orchestrator authority or auto-merge behavior. report_research_yield.py is not
invoked by any workflow, gate, or check — its only reference in the repository is the example command
in docs/benchmark_campaign_manifest.md — so it cannot decide what is admitted; it only reports
counts the snapshot already declares. Every added code path is fail-closed (unknown dimensions,
unknown fields, unknown/missing buckets, duplicate record IDs, non-integer or negative counts,
non-finite lag values, and denominator/bucket-sum mismatches all raise). The admitted_result_packets
dimension is a count copied from the frozen snapshot, not an admission decision. The docs change
records the reporting contract without asserting any result. The decision-required label was
conservative; the residual uncertainty here is reducible by review, so it is being removed.

Validation at this exact head

  • Focused answerability/yield suite: 31 passed.
  • Downstream check: no workflow, script, or gate consumes report_research_yield.py.
  • ruff check, ruff format --check, git diff --check: passed.
  • check_base_sensitive_gates.py --pr 7092: gate_required: false (selector ordinary).
  • check_docs_evidence_integrity.py --base-ref origin/main: 4 changed files passed.
  • Unresolved review threads: 0. Requested reviewers: 0.
  • PR body reconciled to this head before this review.
  • Hosted CI at this head is queued, not green: at review time the repository had 100+ queued and
    15 in-progress Actions runs, and none of this PR's 25 checks had started. That is runner
    starvation, not a defect of this PR.

Remaining gate

Only terminal green CI at 780377325d544464bdd5f2ec9566049f640523f4. No further push is planned, so
the gate-verdict trailer below stays current at that exact head. decision-required is removed
because the domain question it encoded is answered above; merge-ready is intentionally not
applied yet and is the single remaining action once checks conclude green.

Claim boundary unchanged: diagnostic reporting contract only. No campaign, compute, SLURM
submission, evidence admission, publication, ranking, or scientific-progress claim is made or
authorized by this review. Merge authority remains with the guarded merger.

gate-verdict: accepted @ 780377325d544464bdd5f2ec9566049f640523f4

base-policy: ordinary-cas @ 780377325d544464bdd5f2ec9566049f640523f4

pr-metadata: reconciled @ 3158fb64cf5d60ce781c2ae4d126f989c212de96932f2f1cd0b8df27edbdb18c

merge-ready: no (awaiting terminal CI only; not a domain block)

@ll7 ll7 added merge-ready Verified by the PR gate and ready to merge and removed decision-required Author input needed; not yet prepared as a decision packet labels Aug 18, 2026

ll7 commented Aug 18, 2026

Copy link
Copy Markdown
Owner Author

PR reconciliation — superseded by #7469

PR #7469 contains this PR's complete research-yield reporting surface (report_research_yield.py, fixture, tests, and documentation) and integrates it with the canonical answerability-to-campaign-admission path.

Keeping both branches open creates overlapping ownership of the same schema, fixture, tests, and documentation. Close this PR as superseded; preserve its commits as review history. Any review findings specific to the yield dimensions must be carried to #7469.

Canonical owner: #7469.

@ll7 ll7 closed this Aug 18, 2026
ll7 added a commit that referenced this pull request Aug 18, 2026
## Summary
Harden the `goal-pr-review` skill for the situation observed on
2026-08-18: many reviewer lanes plus the autonomous factory acting on
the same PR set, a red shared `main`, `decision-required` labels that
were mostly reducible, and PR bodies whose metadata was reconciled
byte-wise but not truth-wise. Docs-only; no runtime behavior changes.

## Linked Issues
- Relates to `#7448` (fabricated exact-head SHAs in gate-verdict
trailers)
- Relates to `#7491` (merge-ready + stale "not merge-ready" narrative
reaching main)
- Relates to `#7482` (shared-main namespace baseline that made unrelated
PRs look red)

## Stack / Dependency
- Base dependency: none
- Required prior PRs: none
- Stack follow-up issues: none
- Safe to review independently: yes
- Review dependency reason, if any: none

## What Changed
- `.agents/skills/goal-pr-review/SKILL.md` (Codex mirror is a directory
symlink; no separate copy):
- **Concurrent Writers** section: read-live-before-mutate with an
active-writer window; advisory `review-claim: <lane> @ <head> until
<UTC>` marker; content-identical head moves (main refresh only) transfer
findings but require re-publishing exact-head carriers after green CI;
factory/owner label sweeps are authoritative ("one label away"
reporting, no re-apply in-run); successor/superset detection across open
PRs on the same issue.
- **Shared-Main Baseline Before Per-PR Diagnosis**: run the
base-sensitive marker suite on `origin/main` first; classify matching PR
failures as `shared_main_blocked`; route one bounded repair instead of
per-PR "fixes".
- **Decision-Required Triage**: author-reserved taxonomy (claim/evidence
admission, preregistration authorization, release/settings/secrets,
authority *expansion* vs fail-closed narrowing) vs reducible; new
`author_decision` parking state mapped to `AUTHOR_DECISION_REQUIRED`;
≤25-line decision-packet format; keep the branch mergeable while parked.
- Step 4 body check: every 40-hex SHA in the body must resolve and equal
live carriers (never prefix-complete); not-ready sentences must be
re-narrated before `merge-ready`.
- Step 9 + **Shared Resource Budget**: stop waiting under runner
starvation and publish what exists; API-quota guard; no background
pollers; worktrees on repo disk / free-space check; detached-HEAD
inventory-test gotcha.
- Output Requirements now include a terminal state, "one label away"
detail, packet location, parked/racing writers.
- `CHANGELOG.md`: Unreleased/Changed entry.

## Why It Matters
- Added value: turns the ad-hoc rules ten parallel review agents had to
be told out-of-band into the skill contract itself; each item is tied to
an incident (evidence voided by mid-run rebases on 6 PRs; #7092/#7102
closed and a full `merge-ready` sweep while merges were queued; #7482
re-diagnosed per PR; 12 of 15 `decision-required` PRs proved reducible;
#7374/#7435 bodies said "not merge-ready" while labeled/merged; API
quota exhausted twice; `/dev/shm` full twice).
- Expected impact: fewer racing writes, fewer wasted CI reruns, fewer
author packets for reducible decisions, no unverifiable SHAs or stale
narratives in squashed history.
- Why this is worth merging now: the same review-drain pattern is
running daily.

## Research Result Guidance
- Target claim / hypothesis / blocker this should affect: NA — workflow
docs only
- Comparator or baseline, if applicable: NA
- Evidence tier: docs-only
- Result classification: NA
- Decision or stop rule, if applicable: NA
- Parent issue, claim map, registry, context note, or synthesis surface
to update: none
- New research/benchmark/metric/paper-facing analysis tool, if any: NA -
support helper (skill contract text)

## Domain-Aware Approval
- Required for this PR: no - docs-only skill contract; no evidence
classification or claim surface changed
- Domains reviewed: NA
- Status: not required
- Approver/review source or waiver: NA
- Validity checklist. Keep these machine-detected labels unchanged:
  - Target claim/hypothesis: NA
  - Comparator or split/evidence validity: NA
  - Fallback/degraded exclusions: NA
  - Claim boundary: NA
  - Implementation integrity vs experimental validity: NA

## Falsification / Non-Transfer Check
NA — no empirical claim.

## Next Empirical Action
NA.

## Validation / Proof
- `uv run python scripts/dev/check_skills.py` → Validated 55 skills,
typed registry, generated README, and routing tests.
- `uv run pytest tests/dev/test_check_skills.py
tests/dev/test_factory_v2_skill_contract.py
tests/dev/test_token_efficient_thread_profile_snapshot_command.py -q` →
64 passed, 1 skipped.
- `uv run python scripts/tools/sync_ai_config.py --check` → 7 symlinks
validated.
- `uv run python scripts/dev/check_docs_evidence_integrity.py --files …`
→ 2 changed files passed.
- `uv run pre-commit run --files .agents/skills/goal-pr-review/SKILL.md
CHANGELOG.md` → passed.

## Performance Evidence
NA — docs only.

## Risks / Rollout
- The `review-claim` marker is advisory until tooling (factory /
`pr_loop_policy.py`) recognizes it; the text says so.
- `author_decision` is a documented parking state, not a new
`pr_loop_policy.py` classification; a follow-up could add machine
detection of `decision-required` + packet presence.

## Docs / Provenance
- Skill contract updated in place; CHANGELOG entry added.

## Downstream Propagation
NA — not an evidence-producing PR.

## Follow-Up Issues
- Optional: teach `pr_loop_policy.py` / merge gate to recognize the
`review-claim` marker and the not-ready-sentence check (#7491 already
tracks the gate side).

## Reviewer Notes
Diff is additive apart from one table row (`failed_ci` mapping) and the
Output Requirements list. Long lines are inside Markdown table rows,
matching the existing file style.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-ready Verified by the PR gate and ready to merge review-bot-auto Managed label that routes code-bearing PRs to CodeRabbit.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant