fix: regenerate the chat bundle against the 2026.8.4.1 baseline - #109
Merged
Conversation
Closes #108. `chat_bundle.py --check` failed the wiki-currency leg of release 2026.8.4.1 (PyAutoHands run 30905602064) on all 12 committed artifacts. ## Cause `pinned_stack()` reads the stack version from `wiki/core/api_audit_baseline.json`, and the release regenerates that baseline as its own commit (2995839, "Release 2026.8.4.1: regenerate API audit baseline"). The release does NOT regenerate the chat bundle, so every version-headed artifact goes stale the instant the baseline lands. This is stale-by-construction at every release, not a one-off. Control test: on the pre-release baseline the check reported 2 stale files; after pulling 2995839 it reported the same 12 as CI. Regenerating and re-running the check on the regenerated output gives `OK - artifacts current` (exit 0). ## Not just version stamps The refresh also picks up real API surface added in this release: - total public symbols 655 -> 658 - `autolens.plot` 61 -> 64 - new: `subplot_fit_interferometer_combined`, `subplot_fit_interferometer_dirty_images`, `subplot_interferometer_dataset` ## Follow-up The recurrence itself is not fixed here — the release workflow should regenerate the bundle alongside the baseline, otherwise the next release files the next drift issue. Tracked separately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H3XMXCxF72JgNcLeVwCPhZ
The first pass regenerated on a machine whose PyAuto* install is the source checkouts, whose version stamp is deliberately frozen at 2026.7.23.1. But `api_surface()` builds its page by introspecting the LIVE installed stack (`render_symbol_dump()`), and that page carries a `Stack versions:` line reporting those installed versions — so the artifacts were stamped 2026.7.23.1 and `--check` still failed on the two files carrying that line (llms-chat.txt, chat_pack/01_api_surface.md). Regenerated in a clean venv holding the released `autolens==2026.8.4.1` wheels (PYTHONPATH unset, verified `autolens.__file__` resolves to site-packages), which is what `wiki-currency.yml` installs. `--check` under that same env now reports `OK - artifacts current`. Worth recording: the symbol dumps from the full local dev stack and the bare released install were byte-identical. Only the version line differs, so the optional-extras difference between release.yml and wiki-currency.yml does not affect this artifact, and the 655 -> 658 symbol growth is real API change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H3XMXCxF72JgNcLeVwCPhZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #108.
chat_bundle.py --checkfailed the wiki-currency leg of release 2026.8.4.1(PyAutoHands run 30905602064) on all 12 committed artifacts.
Cause
pinned_stack()reads the stack version fromwiki/core/api_audit_baseline.json,and the release regenerates that baseline as its own commit (2995839, "Release
2026.8.4.1: regenerate API audit baseline"). The release does NOT regenerate the
chat bundle, so every version-headed artifact goes stale the instant the baseline
lands. This is stale-by-construction at every release, not a one-off.
Control test: on the pre-release baseline the check reported 2 stale files; after
pulling 2995839 it reported the same 12 as CI. Regenerating and re-running the
check on the regenerated output gives
OK - artifacts current(exit 0).Not just version stamps
The refresh also picks up real API surface added in this release:
autolens.plot61 -> 64subplot_fit_interferometer_combined,subplot_fit_interferometer_dirty_images,subplot_interferometer_datasetFollow-up
The recurrence itself is not fixed here — the release workflow should regenerate
the bundle alongside the baseline, otherwise the next release files the next
drift issue. Tracked separately.
🤖 Generated with Claude Code
https://claude.ai/code/session_01H3XMXCxF72JgNcLeVwCPhZ