chore: release 0.8.0

[FBumann]

Prompt: Prepare the latest release of specsolve.

Prompt: Im wondering if we bumped the layout stuff multiple times in this release. We should only increment once since the last release!

Note

The following content was generated by AI.

Releases 0.8.0 on merge. The answer layout rose twice since 0.7.0, and the new inputs layout once after it was added. Each now rises once: ANSWER_LAYOUT 3 → 4, INPUTS_LAYOUT 1.

The layout numbers

v0.7.0..origin/main on archive_layout.py and relational/answer_layout.py:

PR	change
#1883	LAYOUT renamed ANSWER_LAYOUT (3); INPUTS_LAYOUT = 1 added
#1865	ANSWER_LAYOUT 3 → 4
#1904	ANSWER_LAYOUT 4 → 5
#1913	INPUTS_LAYOUT 1 → 2

No release wrote the intermediate numbers, so this PR sets ANSWER_LAYOUT = 4 and INPUTS_LAYOUT = 1. The format.json example in Result.save's docstring follows. A 0.7.0 answer stamps 3 and a 0.7.0 archive has no root stamp, so both stay refused.

The cost is on unreleased files only. An answer written from main between #1865 and #1904 stamps 4 and is no longer refused, though it still carries model_digest. An archive written from main between #1883 and #1913 stamps inputs 1 and is no longer refused, though it may hold sources.parquet.

No test asserts a layout number; the refusal tests use 0, 99 and no stamp.

Release notes and gates

• ## Upcoming version → ## 0.8.0 (2026-10-09), with a paragraph, a Breaks list and the lines grouped under Solving, Reading an answer, Archives, Data and Examples. An empty ## Upcoming version stays above it. All 21 lines are kept; feat(api): a solve or a sweep asked for outputs={'variable_basis', 'constraint_basis'} reads the basis it ended on, in the same words on every solver #1876's line says outputs={'basis'}, the spelling feat(api): a solve or a sweep can start from tables of values and basis statuses, and a sweep from an earlier sweep or from the slice before it #1882 gave it.
• Minor, not patch: refactor(api): keep= is gone, and a re-solve carries on from where the last solve ended unless start=None says otherwise #1884 removes keep= and Result.kept, feat(api): an answer carries the spec it answered rather than a digest of it, and an archive no longer digests its sources #1913 removes the digests, and the layout refuses 0.7.0 files.
• python -m tools.changelog check → releases 0.8.0 on merge.
• pixi run check: 5523 passed, 566 skipped, 4 xfailed.
• Not run: pixi run docs-test.
• Departure: the layout fix rides in this PR rather than its own, because the release must not ship the doubled numbers. It is its own commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SUzrD57WeiMZtKUnw7wsG8

[read-the-docs-community]

Documentation build overview

📚 specsolve | 🛠️ Build #35037363 | 📁 Comparing ad7d278 against latest (f3cba7d)

  🔍 Preview build  

2 files changed

± about/changelog/index.html
± reference/api/index.html

[codspeed]

Merging this PR will regress 1 benchmark

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 7 improved benchmarks
❌ 1 regressed benchmark
✅ 59 untouched benchmarks
⏩ 307 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	test_window[sector-s-specsolve-highs-one]	4.1 MB	4.3 MB	-5.32%
⚡	test_read[fleet-s-specsolve-parquet]	3,913 KB	957.9 KB	×4.1
⚡	test_read[storage-s-specsolve-parquet]	2.8 MB	2 MB	+45.04%
⚡	test_read[dispatch-s-specsolve-parquet]	4.2 MB	3.3 MB	+25.79%
⚡	test_read[nodal-s-specsolve-parquet]	1.9 MB	1.6 MB	+16.51%
⚡	test_read[profiled-s-specsolve-parquet]	7.6 MB	6.6 MB	+15.8%
⚡	test_read[commitment-s-specsolve-parquet]	770.6 KB	691.3 KB	+11.47%
⚡	test_read[sector-s-specsolve-parquet]	1,034.9 KB	934.1 KB	+10.8%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing claude/nifty-pasteur-de9v0l (ad7d278) with main (782d53f)²}

Footnotes

1. 307 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (f3cba7d) during the generation of this report, so 782d53f was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩