mind: retire jax-likelihood-smoke-pins-stale — fixed before it was filed - #335
Merged
Merged
Conversation
/start_dev research on draft/bug/autolens/jax_likelihood_smoke_pins_stale.md found no reproducible bug left in it. Retired unstarted: no GitHub issue, no active.md entry, no development. Verified against autolens_workspace_test main 8be3d59, Smoke Tests run 32922456742 (2026-08-26 02:24 UTC), green on Python 3.12 and 3.13: 22/22 PASS, including all three of the named scripts still in the gate. The prompt's "20/24 until this lands" is now 22/22. Per claim: - imaging/jax_likelihood/lp.py - repinned -1.34797827e09 -> -6.74165366e08 in 197ce6e (autolens_workspace_test#257), the same day the prompt was filed. - fb1aefe0b "orphan worktree" - not orphaned. It is the head SHA of PyAutoLens#700, merged 2026-08-17, two days before the prompt called it unmerged; 197ce6e is the paired re-pin the prompt asked for. - interferometer/.../rectangular.py - pin -3164.286252 unchanged and green (re-verified in 99d63b3 incl. the TransformerNUFFT cross-check). The 08-19 miss was control-run environment drift, not a stale pin. - interferometer/.../mge.py - repinned by the same 197ce6e; a PositionsLH-doubling casualty, not independent drift. - multi_dataset/.../mge.py - never a pin problem. Out of the smoke gate since #262 (2026-08-22) for the XLA compile stall tracked in autolens_workspace_test#245; its pin is untouched since the multi -> multi_dataset rename. The completion record keeps the reusable findings: adjudicate an "orphan" worktree from the remote's merged PRs rather than from the worktree's own state, and do not group symptoms into a "family" by folder — three of the four scripts were one root cause. Follow-ups are local debris (a stale worktree on the laptop, /repo_cleanup) and one latent item owned by autolens_workspace_test#245's re-enable. Dashboard regenerated in the same commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Egf8PFc5UKJfVWY1jbBKGU
github-actions
Bot
deleted the
claude/jax-likelihood-smoke-pins-stale-im98b0
branch
August 26, 2026 20:07
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
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.
Overview
/start_dev draft/bug/autolens/jax_likelihood_smoke_pins_stale.mdfound no reproducible bug left in the prompt. Retired unstarted: no GitHub issue, noactive.mdentry, no development.Verified state
autolens_workspace_testmain8be3d59, Smoke Tests run 32922456742 (2026-08-26 02:24 UTC), green on Python 3.12 and 3.13:The prompt's headline — "every workspace_test smoke sweep reads 20/24 until this lands" — is now 22/22.
Disposition of each claim
imaging/jax_likelihood/lp.pypin-1.34797827e09is double-6.74165366e08in197ce6e(autolens_workspace_test#257), the same day the prompt was filedfb1aefe0bsits unmerged in an orphan worktree197ce6eis the paired re-pin the prompt asked forinterferometer/jax_likelihood/rectangular.pymisses pin by 0.0124%-3164.286252unchanged and green (re-verified in99d63b3incl. the TransformerNUFFT cross-check). The 08-19 miss was control-run environment drift, not a stale pininterferometer/jax_likelihood/mge.pystale pin197ce6e; a PositionsLH-doubling casualty, not independent driftmulti_dataset/jax_likelihood/mge.pystale pinmulti→multi_datasetrenameChanges
complete/2026/08/jax-likelihood-smoke-pins-stale.md— the completion record, with the original prompt folded indraft/bug/autolens/jax_likelihood_smoke_pins_stale.md— removedcomplete/index.md— regenerated (1143 records)dashboard.md/dashboard.html— regenerated; the prompt no longer renders as pickable backloglifecycle.py checkandlifecycle.py index --checkboth report OK.Findings kept in the record
PositionsLHpenalty). Acting on the "stale-pin family" framing would have widened tolerances on pins that were already correct.smoke_tests.txtfor timing reasons, so the sweep reads 22/22 without any pin having been touched for that.Follow-ups
~/Code/PyAutoLabs-wt/positions-lh-penalty-accumulationis a stale worktree over a merged branch — a/repo_cleanupitem, not code work.multi_dataset/jax_likelihood/mge.py's pin has never been verified against a post-PyAutoLens#700 library. Re-derive it as part of autolens_workspace_test#245's re-enable. Deliberately not filed as its own prompt — it has no standalone trigger.🤖 Generated with Claude Code
https://claude.ai/code/session_01Egf8PFc5UKJfVWY1jbBKGU
Generated by Claude Code