feat(agents): add offset-based pagination to file_read #85

2026-07-30T21:48:56Z

CoreRasurae commented

2026-07-30 21:48:56 +00:00

Summary

Adds an optional offset parameter to the file_read tool (schema in llm_tools.py, implementation in ToolAgent._file_read_tool) so large files can be paginated across multiple bounded calls instead of only ever returning the first max_chars characters.
offset is a character position, defaults to 0, and reproduces the exact prior output when omitted.
Truncated responses now include a MORE_CONTENT_AT_OFFSET: <N> header marker giving the exact next offset; requesting an offset at/beyond EOF returns a NO_MORE_CONTENT_AT_OFFSET success response (empty content) rather than an error. Negative/non-integer offsets raise ExecutionError.
Full design rationale in docs/adr/ADR-2033-file-read-offset-pagination.md (unit choice, continuation-signaling format, out-of-range semantics, and why directory-listing pagination + byte-level seeking are deferred).

Closes #83

Note on base branch: this PR is stacked on feature/m2-tool-timeout-awareness (PR #84, still open) rather than master, since this branch was rebased on top of it per request. The diff here is limited to the single offset-pagination commit; PR #84's changes are not part of this review. This PR's base should be retargeted to master once #84 merges.

Test plan

nox -s lint / nox -s format -- --check
nox -s typecheck (pyright strict, 0 errors)
nox -s security_scan (bandit + semgrep, 0 findings) / nox -s dead_code
nox -s complexity
nox -s unit_tests — 2789 scenarios passed, including 8 new Behave scenarios covering: offset=0 regression, mid-file windowed read, two-call pagination with no gap/overlap, negative offset, non-integer offset, offset at EOF, offset beyond EOF, explicit offset: null
nox -s coverage_report — 96.8% (>= 96.5% threshold)
nox -s integration_tests — 319 Robot Framework tests passed
nox -s build
nox -s benchmark_regression — running (ASV, informational-only, not required for merge)

🤖 Generated with Claude Code

## Summary - Adds an optional `offset` parameter to the `file_read` tool (schema in `llm_tools.py`, implementation in `ToolAgent._file_read_tool`) so large files can be paginated across multiple bounded calls instead of only ever returning the first `max_chars` characters. - `offset` is a character position, defaults to `0`, and reproduces the exact prior output when omitted. - Truncated responses now include a `MORE_CONTENT_AT_OFFSET: <N>` header marker giving the exact next offset; requesting an offset at/beyond EOF returns a `NO_MORE_CONTENT_AT_OFFSET` success response (empty content) rather than an error. Negative/non-integer offsets raise `ExecutionError`. - Full design rationale in `docs/adr/ADR-2033-file-read-offset-pagination.md` (unit choice, continuation-signaling format, out-of-range semantics, and why directory-listing pagination + byte-level seeking are deferred). Closes #83 **Note on base branch:** this PR is stacked on `feature/m2-tool-timeout-awareness` (PR #84, still open) rather than `master`, since this branch was rebased on top of it per request. The diff here is limited to the single offset-pagination commit; PR #84's changes are not part of this review. This PR's base should be retargeted to `master` once #84 merges. ## Test plan - [x] `nox -s lint` / `nox -s format -- --check` - [x] `nox -s typecheck` (pyright strict, 0 errors) - [x] `nox -s security_scan` (bandit + semgrep, 0 findings) / `nox -s dead_code` - [x] `nox -s complexity` - [x] `nox -s unit_tests` — 2789 scenarios passed, including 8 new Behave scenarios covering: offset=0 regression, mid-file windowed read, two-call pagination with no gap/overlap, negative offset, non-integer offset, offset at EOF, offset beyond EOF, explicit `offset: null` - [x] `nox -s coverage_report` — 96.8% (>= 96.5% threshold) - [x] `nox -s integration_tests` — 319 Robot Framework tests passed - [x] `nox -s build` - [ ] `nox -s benchmark_regression` — running (ASV, informational-only, not required for merge) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

CoreRasurae added this to the v2.1.0 milestone 2026-07-30 21:49:14 +00:00

CoreRasurae added the

Type

Feature

label 2026-07-30 21:49:19 +00:00

CoreRasurae added a new dependency 2026-07-30 21:49:40 +00:00

#83 feat(agents): add offset-based pagination to file_read

CoreRasurae commented

2026-07-30 21:51:27 +00:00

Two items flagged for reviewer attention rather than silently resolved:

Coverage threshold wording mismatch (pre-existing, not introduced by this PR): the issue's acceptance criteria say nox -s coverage_report must stay ≥ 97%. The actual enforced gate in noxfile.py (COVERAGE_THRESHOLD = 96.5) is 96.5%, not 97% — this constant predates this PR and isn't touched here. Actual result: 96.8%, which passes the code's real gate but is technically below the ticket's literal 97% wording. Left both boxes for that criterion/subtask unchecked pending a maintainer call on which number is authoritative (I didn't want to unilaterally bump COVERAGE_THRESHOLD to 97 as a drive-by change unrelated to file_read pagination).
"Run nox (all default sessions)": I did not run bare nox, because two of its default sessions aren't safe/appropriate for this: serve_docs starts an mkdocs serve dev server that blocks indefinitely, and e2e_tests requires real LLM API keys and isn't part of ci.yml at all. Instead I ran every session that maps to an actual required or informational CI job individually — lint, format -- --check, typecheck, security_scan, dead_code, complexity, unit_tests (2789 scenarios), coverage_report, integration_tests (319 Robot tests), build, and benchmark_regression (ASV, informational) — all green. Left that subtask box unchecked since it doesn't literally match what was run, even though I believe the intent (full quality gate) is satisfied.

Both Robot Framework integration tests and the ASV benchmark/benchmark_regression sessions were already wired into noxfile.py and ci.yml before this PR — confirmed active and passing, no changes needed there.

🤖 Generated with Claude Code

Two items flagged for reviewer attention rather than silently resolved: 1. **Coverage threshold wording mismatch (pre-existing, not introduced by this PR):** the issue's acceptance criteria say `nox -s coverage_report` must stay ≥ 97%. The actual enforced gate in `noxfile.py` (`COVERAGE_THRESHOLD = 96.5`) is 96.5%, not 97% — this constant predates this PR and isn't touched here. Actual result: **96.8%**, which passes the code's real gate but is technically below the ticket's literal 97% wording. Left both boxes for that criterion/subtask unchecked pending a maintainer call on which number is authoritative (I didn't want to unilaterally bump `COVERAGE_THRESHOLD` to 97 as a drive-by change unrelated to `file_read` pagination). 2. **"Run nox (all default sessions)":** I did not run bare `nox`, because two of its default sessions aren't safe/appropriate for this: `serve_docs` starts an `mkdocs serve` dev server that blocks indefinitely, and `e2e_tests` requires real LLM API keys and isn't part of `ci.yml` at all. Instead I ran every session that maps to an actual required or informational CI job individually — `lint`, `format -- --check`, `typecheck`, `security_scan`, `dead_code`, `complexity`, `unit_tests` (2789 scenarios), `coverage_report`, `integration_tests` (319 Robot tests), `build`, and `benchmark_regression` (ASV, informational) — all green. Left that subtask box unchecked since it doesn't literally match what was run, even though I believe the intent (full quality gate) is satisfied. Both Robot Framework integration tests and the ASV benchmark/benchmark_regression sessions were already wired into `noxfile.py` and `ci.yml` before this PR — confirmed active and passing, no changes needed there. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

hurui200320 requested changes 2026-07-31 06:11:58 +00:00

Dismissed

hurui200320 left a comment

PR Review: !85 (Ticket #83)

Verdict: Request Changes

The implementation correctly adds offset-based pagination and the new Behave scenarios cover the main pagination paths, validation errors, and EOF cases. However, two major blockers need resolution before this can merge: the reported coverage is below the project’s documented 97% gate, and the MORE_CONTENT_AT_OFFSET marker is currently appended to all truncated reads, which changes existing max_chars-only output and violates the issue’s regression guard.

Critical Issues

None.

Major Issues

Coverage is below the documented 97% merge gate
- File: project-wide / noxfile.py
- Problem: The PR author reports nox -s coverage_report at 96.8%. CONTRIBUTING.md §Project-Specific Guidelines states: “Unit test coverage must remain above 97% at all times… for this project, 97% is the enforced merge gate.” Issue #83’s acceptance criteria also require nox -s coverage_report stays ≥ 97%. The noxfile.py constant COVERAGE_THRESHOLD = 96.5 predates this PR and conflicts with the documented gate. The author flagged this explicitly for a maintainer call.
- Recommendation: Resolve before merging by either (a) adding tests to bring coverage to ≥ 97% and aligning noxfile.py to 97%, or (b) obtaining an explicit, documented maintainer waiver that updates the issue acceptance criteria / CONTRIBUTING.md threshold. Without that, the PR does not satisfy the issue’s own acceptance criteria.
MORE_CONTENT_AT_OFFSET changes output for existing max_chars-only calls
- File: src/cleveractors/agents/tool.py, lines 736–747
- Problem: Issue #83 acceptance criterion #2 requires that omitting offset “reproduces byte-for-byte identical output to current behavior (regression guard).” The implementation appends MORE_CONTENT_AT_OFFSET: <N> to every truncated response, including calls that set only max_chars and omit offset. That changes the header for existing max_chars-only users and breaks the regression guard.
- Recommendation: Only emit MORE_CONTENT_AT_OFFSET when the caller is actually paginating. The simplest fix consistent with the existing offset > 0 guard is:
```
if truncated:
    header += f" | TRUNCATED to {max_chars} chars"
    if offset > 0:
        header += f" | MORE_CONTENT_AT_OFFSET: {window_end}"
```
  This preserves the legacy max_chars-only header exactly while still signaling continuation for paginated reads. Update ADR-2033 D-3 and the CHANGELOG wording accordingly.

Minor Issues

_file_read_tool docstring does not mention pagination
- File: src/cleveractors/agents/tool.py, line 620
- Problem: The docstring still reads “File reading tool with directory listing support and optional truncation.” It does not mention the new offset parameter or pagination behavior.
- Recommendation: Update the docstring to describe the offset parameter and its interaction with max_chars.

Nits

Scenario count mismatch in PR description
- The PR description lists “8 new Behave scenarios” but features/tool_coverage_gaps.feature adds 7 new scenarios (one of which exercises three cases: omitted, 0, and null). Cosmetic only; coverage is unchanged.

Summary

This is a well-scoped, clearly documented feature with a solid ADR and good test coverage of the new offset paths. The two major blockers are the coverage gate and the unintended change to legacy max_chars-only output. Once those are addressed, this PR should be ready to merge.

## PR Review: !85 (Ticket #83) ### Verdict: Request Changes The implementation correctly adds offset-based pagination and the new Behave scenarios cover the main pagination paths, validation errors, and EOF cases. However, two major blockers need resolution before this can merge: the reported coverage is below the project’s documented 97% gate, and the `MORE_CONTENT_AT_OFFSET` marker is currently appended to all truncated reads, which changes existing `max_chars`-only output and violates the issue’s regression guard. ### Critical Issues None. ### Major Issues 1. **Coverage is below the documented 97% merge gate** - **File:** project-wide / `noxfile.py` - **Problem:** The PR author reports `nox -s coverage_report` at **96.8%**. `CONTRIBUTING.md` §Project-Specific Guidelines states: “Unit test coverage must remain above **97%** at all times… for this project, **97% is the enforced merge gate**.” Issue #83’s acceptance criteria also require `nox -s coverage_report stays ≥ 97%`. The `noxfile.py` constant `COVERAGE_THRESHOLD = 96.5` predates this PR and conflicts with the documented gate. The author flagged this explicitly for a maintainer call. - **Recommendation:** Resolve before merging by either (a) adding tests to bring coverage to ≥ 97% and aligning `noxfile.py` to 97%, or (b) obtaining an explicit, documented maintainer waiver that updates the issue acceptance criteria / `CONTRIBUTING.md` threshold. Without that, the PR does not satisfy the issue’s own acceptance criteria. 2. **`MORE_CONTENT_AT_OFFSET` changes output for existing `max_chars`-only calls** - **File:** `src/cleveractors/agents/tool.py`, lines 736–747 - **Problem:** Issue #83 acceptance criterion #2 requires that omitting `offset` “reproduces byte-for-byte identical output to current behavior (regression guard).” The implementation appends `MORE_CONTENT_AT_OFFSET: <N>` to every truncated response, including calls that set only `max_chars` and omit `offset`. That changes the header for existing `max_chars`-only users and breaks the regression guard. - **Recommendation:** Only emit `MORE_CONTENT_AT_OFFSET` when the caller is actually paginating. The simplest fix consistent with the existing `offset > 0` guard is: ```python if truncated: header += f" | TRUNCATED to {max_chars} chars" if offset > 0: header += f" | MORE_CONTENT_AT_OFFSET: {window_end}" ``` This preserves the legacy `max_chars`-only header exactly while still signaling continuation for paginated reads. Update ADR-2033 D-3 and the CHANGELOG wording accordingly. ### Minor Issues 1. **`_file_read_tool` docstring does not mention pagination** - **File:** `src/cleveractors/agents/tool.py`, line 620 - **Problem:** The docstring still reads “File reading tool with directory listing support and optional truncation.” It does not mention the new `offset` parameter or pagination behavior. - **Recommendation:** Update the docstring to describe the `offset` parameter and its interaction with `max_chars`. ### Nits 1. **Scenario count mismatch in PR description** - The PR description lists “8 new Behave scenarios” but `features/tool_coverage_gaps.feature` adds 7 new scenarios (one of which exercises three cases: omitted, `0`, and `null`). Cosmetic only; coverage is unchanged. ### Summary This is a well-scoped, clearly documented feature with a solid ADR and good test coverage of the new offset paths. The two major blockers are the coverage gate and the unintended change to legacy `max_chars`-only output. Once those are addressed, this PR should be ready to merge.

CoreRasurae changed target branch from feature/m2-tool-timeout-awareness to master

2026-07-31 08:31:22 +00:00

CoreRasurae commented

2026-07-31 08:39:57 +00:00

Regarding the review comment 321097 for the MAJOR ISSUES:

Issue 1: The coverage can be accepted at 96.8% the 97% textual definition can be considered to be rounded, not precise, the 96.5% is the precise value. So not applying this change.
Issue 2: It is preferable to inform the LLM appropriately with proper hints that it can proceed from a simple max_char calls to start pagination. The byte-byte for byte correspondence is for the file content, not for the response header, or footer. So note applying this change.

Regarding the same review comments, MINOR ISSUE:

Issue 1: Is much more then a minor issues, the LLM needs to be properly informed of the offset argument. This is to be addressed.

Regarding the review comment 321097 for the MAJOR ISSUES: - Issue 1: The coverage can be accepted at 96.8% the 97% textual definition can be considered to be rounded, not precise, the 96.5% is the precise value. So not applying this change. - Issue 2: It is preferable to inform the LLM appropriately with proper hints that it can proceed from a simple max_char calls to start pagination. The byte-byte for byte correspondence is for the file content, not for the response header, or footer. So note applying this change. Regarding the same review comments, MINOR ISSUE: - Issue 1: Is much more then a minor issues, the LLM needs to be properly informed of the offset argument. This is to be addressed.

CoreRasurae added 1 commit 2026-07-31 08:55:24 +00:00

feat(agents): add offset-based pagination to file_read

CI / lint (pull_request) Successful in 1m40s

Details

CI / quality (pull_request) Successful in 2m7s

Details

CI / typecheck (pull_request) Successful in 3m23s

Details

CI / build (pull_request) Successful in 1m6s

Details

CI / security (pull_request) Successful in 4m51s

Details

CI / integration_tests (pull_request) Successful in 3m14s

Details

CI / unit_tests (pull_request) Successful in 5m24s

Details

CI / coverage (pull_request) Successful in 6m51s

Details

CI / status-check (pull_request) Successful in 7s

Details

CI / benchmark (pull_request) Failing after 17m20s

Details

CI / lint (push) Successful in 59s

Details

CI / typecheck (push) Successful in 2m21s

Details

CI / security (push) Successful in 1m16s

Details

CI / quality (push) Successful in 51s

Details

CI / build (push) Successful in 1m29s

Details

CI / integration_tests (push) Successful in 3m28s

Details

CI / unit_tests (push) Successful in 4m37s

Details

CI / coverage (push) Successful in 4m58s

Details

CI / status-check (push) Successful in 7s

Details

CI / benchmark (push) Failing after 18m9s

Details

4fe14c5b77

`file_read` always read from position 0; `max_chars` (ADR-2030 D-3) only
bounded where the returned content stopped, so once a large file was
truncated there was no way to retrieve the next chunk short of falling
back to the `shell` tool (`tail -c +N`, `sed -n`, `dd skip=...`) — the
same class of awkward, error-prone detour ADR-2030 D-4 already eliminated
for file paths mistaken for shell commands.

Adds an optional `offset` character-position argument (default 0,
byte-for-byte identical output when omitted) to both the tool schema
(`llm_tools._BUILTIN_TOOL_SCHEMAS["file_read"]`) and the implementation
(`ToolAgent._file_read_tool`). Combined with `max_chars` it returns the
window `[offset, offset + max_chars)`, and the `[FILE_READ_SUCCESS]`
header now signals continuation: `MORE_CONTENT_AT_OFFSET: N` when more
content remains (N is the exact next offset, so callers never compute
`offset + max_chars` themselves), or `NO_MORE_CONTENT_AT_OFFSET: N` when
the requested offset is at or beyond end-of-file — a success response
with empty content, not an error, since that is the expected terminal
state of a correctly-paginating caller. Negative or non-integer offsets
raise `ExecutionError`, mirroring the existing `max_chars` validation
pattern.

See docs/adr/ADR-2033-file-read-offset-pagination.md for the full set of
design decisions, including why directory-listing pagination and
byte-level seeking are deferred to a future issue.

ISSUES CLOSED: #83

CoreRasurae force-pushed feature/m2-file-read-offset from e9247458cc to 4fe14c5b77

2026-07-31 08:55:25 +00:00

Compare

CoreRasurae commented

2026-07-31 08:55:38 +00:00

Follow-up after re-checking review #9766 against docs/index.md, docs/adr/ADR-2033-file-read-offset-pagination.md, and issue #83:

Major Issue 1 (coverage 97% vs 96.5%): Not changing noxfile.py. Confirmed unrelated to file_read/offset — pre-existing repo-wide constant, and bumping it is a separate drive-by change. Re-ran nox -s coverage_report after the fix below: still 96.8% (≥ the code's actual 96.5% gate), no regression. Stands per comment 321108.

Major Issue 2 (MORE_CONTENT_AT_OFFSET gated on offset > 0): Not applying. This is exactly what ADR-2033 D-2/D-3 (accepted) specifies: the marker is tied to the pre-existing TRUNCATED condition, not to whether offset was passed — by design, so a plain max_chars-only caller also gets a hint that pagination is available. The ADR's own Consequences section already documents that the header (non-normative per §4.5.1) is intentionally extended here; the "byte-for-byte identical output" regression guard (issue #83 AC #2) is about file content at offset=0, not header text — confirmed unchanged by the implementation. Changing this would mean reopening and revising an already-accepted ADR for a case it explicitly decided.

Minor Issue 1 (docstring): Applied. ToolAgent._file_read_tool's docstring now mentions the offset parameter and pagination (ADR-2033), amended into the same commit (4fe14c5, force-pushed).

Nit (scenario count): Cosmetic PR-description-only mismatch (7 scenarios in features/tool_coverage_gaps.feature, one covering 3 sub-cases); no code impact, leaving as-is.

Coverage and full lint/typecheck/unit_tests re-verified green after the docstring change. Ready for re-review.

Follow-up after re-checking review #9766 against `docs/index.md`, `docs/adr/ADR-2033-file-read-offset-pagination.md`, and issue #83: **Major Issue 1 (coverage 97% vs 96.5%):** Not changing `noxfile.py`. Confirmed unrelated to `file_read`/`offset` — pre-existing repo-wide constant, and bumping it is a separate drive-by change. Re-ran `nox -s coverage_report` after the fix below: still **96.8%** (≥ the code's actual 96.5% gate), no regression. Stands per comment 321108. **Major Issue 2 (`MORE_CONTENT_AT_OFFSET` gated on `offset > 0`):** Not applying. This is exactly what `ADR-2033` D-2/D-3 (accepted) specifies: the marker is tied to the pre-existing `TRUNCATED` condition, not to whether `offset` was passed — by design, so a plain `max_chars`-only caller also gets a hint that pagination is available. The ADR's own Consequences section already documents that the header (non-normative per §4.5.1) is intentionally extended here; the "byte-for-byte identical output" regression guard (issue #83 AC #2) is about file *content* at `offset=0`, not header text — confirmed unchanged by the implementation. Changing this would mean reopening and revising an already-accepted ADR for a case it explicitly decided. **Minor Issue 1 (docstring):** Applied. `ToolAgent._file_read_tool`'s docstring now mentions the `offset` parameter and pagination (ADR-2033), amended into the same commit (`4fe14c5`, force-pushed). **Nit (scenario count):** Cosmetic PR-description-only mismatch (7 scenarios in `features/tool_coverage_gaps.feature`, one covering 3 sub-cases); no code impact, leaving as-is. Coverage and full lint/typecheck/unit_tests re-verified green after the docstring change. Ready for re-review.

hurui200320 approved these changes 2026-07-31 09:17:34 +00:00

hurui200320 left a comment

PR Review: !85 (Ticket #83)

Verdict: Approve

Reviewed the latest revision (4fe14c5) including the author's responses to the previous review. The offset-based pagination feature is implemented cleanly and matches the accepted ADR-2033. The docstring update has been applied. The two previously flagged items (coverage threshold wording and MORE_CONTENT_AT_OFFSET appearing on legacy max_chars-only truncated reads) are pre-existing design/documentation discrepancies that the PR author has explicitly decided to defer, so I am not re-raising them.

Critical Issues

None.

Major Issues

None.

Minor Issues

None.

Nits

None.

Summary

src/cleveractors/agents/tool.py: _file_read_tool correctly validates offset (default 0, None treated as 0, non-integer and negative values raise ExecutionError), computes the window [offset, offset + max_chars), and emits the continuation markers per ADR-2033 D-3/D-4. The offset > 0 guard preserves the empty-file/no-offset regression path.
src/cleveractors/agents/llm_tools.py: schema extended with the optional offset integer parameter and a helpful LLM-facing description.
docs/adr/ADR-2033-file-read-offset-pagination.md: complete ADR in the required format, resolving unit choice, window semantics, continuation signaling, EOF semantics, directory-listing deferral, and efficiency trade-offs.
features/tool_coverage_gaps.feature / features/steps/tool_coverage_gaps_steps.py: seven new Behave scenarios cover offset=0 regression, mid-file window, two-call pagination, negative offset, non-integer offset, offset at EOF, and offset beyond EOF. Assertions are meaningful and verify both markers and content boundaries.
CHANGELOG.md: accurate, user-facing entry.

The PR is ready to merge.

## PR Review: !85 (Ticket #83) ### Verdict: Approve Reviewed the latest revision (`4fe14c5`) including the author's responses to the previous review. The offset-based pagination feature is implemented cleanly and matches the accepted ADR-2033. The docstring update has been applied. The two previously flagged items (coverage threshold wording and `MORE_CONTENT_AT_OFFSET` appearing on legacy `max_chars`-only truncated reads) are pre-existing design/documentation discrepancies that the PR author has explicitly decided to defer, so I am not re-raising them. ### Critical Issues None. ### Major Issues None. ### Minor Issues None. ### Nits None. ### Summary - `src/cleveractors/agents/tool.py`: `_file_read_tool` correctly validates `offset` (default `0`, `None` treated as `0`, non-integer and negative values raise `ExecutionError`), computes the window `[offset, offset + max_chars)`, and emits the continuation markers per ADR-2033 D-3/D-4. The `offset > 0` guard preserves the empty-file/no-offset regression path. - `src/cleveractors/agents/llm_tools.py`: schema extended with the optional `offset` integer parameter and a helpful LLM-facing description. - `docs/adr/ADR-2033-file-read-offset-pagination.md`: complete ADR in the required format, resolving unit choice, window semantics, continuation signaling, EOF semantics, directory-listing deferral, and efficiency trade-offs. - `features/tool_coverage_gaps.feature` / `features/steps/tool_coverage_gaps_steps.py`: seven new Behave scenarios cover `offset=0` regression, mid-file window, two-call pagination, negative offset, non-integer offset, offset at EOF, and offset beyond EOF. Assertions are meaningful and verify both markers and content boundaries. - `CHANGELOG.md`: accurate, user-facing entry. The PR is ready to merge.

CoreRasurae merged commit 4fe14c5b77 into master

2026-07-31 10:14:13 +00:00

CoreRasurae deleted branch feature/m2-file-read-offset

2026-07-31 10:14:20 +00:00

CoreRasurae referenced this pull request

2026-07-31 11:54:37 +00:00

fix(ci): benchmark_regression job intermittently hangs/times out and never signals real regressions correctly #86

CoreRasurae referenced this issue from a commit

2026-07-31 12:02:18 +00:00

fix(ci): scope asv --quick to the benchmark_regression CI job only

CoreRasurae referenced this pull request

2026-07-31 12:02:46 +00:00