Skip to content

test(docscout): preserve multi-field requests within reply estimate - #81

Merged
wolfy-j merged 1 commit into
mainfrom
test/docscout-under-budget-request
Nov 11, 2026
Merged

wolfy-j merged 1 commit into
mainfrom
test/docscout-under-budget-request

Conversation

@wolfy-j

@wolfy-j wolfy-j commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Completes the compatibility regression for #77, which supersedes #63. A two-field extractor whose reply estimate fits the output allowance must make exactly one extraction call with the pre-batching request fingerprint, ordered fields, values, evidence and saved results. The existing single-field identity test remains unchanged.

The expected fingerprint is recorded against the extraction code before #77, then the same test passes against the current implementation on SQLite and PostgreSQL. A one-line source comment links the estimate weights to the completion-size samples reported in #63; the existing comments continue to describe them as heuristics.

Validation uses the official v0.3.59a runtime and freshly resolved dependencies: the affected successful-caller file passes all 10 tests on both engines against both implementations. Full Docscout suites pass 304 tests per engine, and lint passes. This changes tests and a comment only; extractor behavior, configuration, data and static assets remain unchanged.

@wolfy-j
wolfy-j merged commit 956ad04 into main Nov 11, 2026
16 checks passed
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