Bound repair feedback construction

This commit is contained in:
2026-11-05 14:07:34 +00:00
parent e834e7d806
commit 7c435032b6
3 changed files with 46 additions and 11 deletions

View File

@@ -516,6 +516,13 @@ many entries, heavily escaped and invalid strings, valid JSON, and omission
semantics. Repeat the roadmap's three formatter workloads and record real
allocation results; aggregate allocation is not a peak-heap guarantee.
Completion: repair feedback uses bounded prefixes for both complete and
omission forms. Focused tests pass on Go 1.27.3. The documented 20-iteration,
three-run workloads measured 398 B/op for 64 ASCII bytes (68 output bytes),
767,634 B/op for 1 MiB ASCII (65,536 output bytes), and about 12,125,700 B/op
for 1 MiB escaped content (65,531 output bytes). These aggregate allocations
do not establish a peak-heap guarantee.
## Stage 20: Select Namespace Ranges Before Copying Inventories
**Catalog:** 20. **Files:** configuration/engine inventory interfaces and listing tests.