[devin-ai-integration]

What and why

The release-gate performance record for 0.11.0: docs/project/performance-release-0.11.0-vs-0.10.1.md measures the release candidate against the v0.10.1 tag (1c45b6e1749fc8adc9b82d4af22fbe180b56a0e2) by the method of the 0.10.1 and 0.10.0 records — every benchmark on both revisions under benchstat over six interleaved rounds, the rows in doubt re-run interleaved on a quiet machine (Parse/* alone for eight rounds), tests/stressmodel with the 32-satellite rows re-taken quiet, and whole-binary validation, start-up and size.

The candidate is develop d8b60ed62 with #1350 merged locally (df3341e659ccfe88f37791e652d78ef948a1c3e5), named that way in the record because #1350 restores what #1319 cost; a third column measures that candidate with the six focused fixes the record led to. Of those, #1347, #1348, #1351, #1352 and #1353 have since merged (develop a662c2bce), so the third column is the shipping head modulo #1349, which stays open. Each movement beyond noise is attributed by first-parent bisection with exact allocation counts and either fixed in its own perf/* pull request or named and carried as the inherent cost of a correctness change; no fix lands here.

Fix pull requests the record links: #1347 (loop footprints), #1348 (import enumeration), #1349 (conformance by symbol), #1351 (effective types), #1352 (REPL UTF-16 column), #1353 (redefinition closure), and, written after the tables and not in the third column, #1355 (statement order and stamped footprint once per model) and #1356 (transition taken without allocating). The language server's remaining per-query re-enumeration is named as a design cost of #1062 with its fix branch to follow.

Wiring: mkdocs.yml not-in-nav list after the 0.10.1 entry, the Performance entry in docs/project/README.md, the "the latest is" link in docs/internals/performance.md, and the fragment changes/unreleased/perf-0.11.0-record.added.md.

How it was verified

gofmt -l . (empty), go vet ./..., python3 scripts/check-doc-links.py (0 broken), python3 scripts/check-doc-ids.py, python -m mkdocs build --strict, python3 scripts/changelog.py check, go test ./tests/hygiene. The measurements are reproducible from the commands the record states; raw benchstat inputs are not committed, as in the previous records.

Checklist

• make test and make lint pass locally (docs-only change; the doc gates above)
• Tests added or updated for the change (not applicable: documentation)
• Documentation extended where it already covers the surface (see CONTRIBUTING.md)
• Changelog entry added as changes/unreleased/<slug>.<section>.md, not as an edit to CHANGELOG.md
• baselines regenerated and make docs-counts run if a gate count moved (no gate count moved)
• No internal work-item labels (waves, slices, F4, K5) in the body, docs, or changelog

Link to Devin session: https://nasa-jpl-demo.devinenterprise.com/sessions/cf22d7a746814d20b2f0eaf11682fef9
Open in Devin Desktop: https://nasa-jpl-demo.devinenterprise.com/desktop/session/cf22d7a746814d20b2f0eaf11682fef9?variant=devin
Requested by: @HuiJun

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

🔍 Devin Review: 2 flags

Not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)