prompt: record lacosmic CR dial + star-pass decoupling shipped (PyAutoReduce#66) - #227
Merged
Merged
Conversation
…yAutoReduce#66) Reconciliation: the cr_method dial (deepcr per-frame route, resetbits=0 trap pinned) and the psf_star_pass decoupling shipped as PyAutoReduce PR #66 on 2026-08-06 from a wake-up session branch, but the prompt was never advanced out of draft/. Fold it into the dated completion record; refresh index + dashboard. PyAutoReduce#61/#62 stay open deliberately — closure is the human-gated default-flip decision, now reshaped by the reporter's 2026-08-09 grid correction (erosion was a dither-erasing alignment artifact; the discriminating regime is poorly-dithered data). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DSnKLkkNeGriLFQNd8fKrc
Jammy2211
pushed a commit
that referenced
this pull request
Aug 23, 2026
) The follow-up filed at the end of the stale-jax-pin ship bundled two different jobs and sized too-large (score 11) against a declared medium. Split per hard rule #3: - active/run_smoke_per_script_timeout.md — bounded, now ISSUED as autogalaxy_workspace_test#108 and registered in active.md. - draft/research/workspaces/intermittent_smoke_hang_jax_mge.md — re-homed from bug/ to research/ and re-sized large; the open-ended half, left in draft. Investigating the timeout task changed it materially. It is not a new feature but DRIFT: autolens_workspace_test's run_smoke.py already implements the per-script timeout (PyAutoHands#226/#227) at 193 lines, while autogalaxy, autocti and autofit still carry the un-capped 113-line copy. Those three are identical in code — differing only in one docstring paragraph — so it is one diff applied three times. That also explains the hang's asymmetry: autolens would have capped mge.py and carried on; autogalaxy had nothing to stop it and ran 59 minutes silent. Sizing overridden to low/direct against the Feature Agent's large/phased verdict, which was formed on the pre-investigation draft. Recorded in the prompt with the reason rather than silently ignored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KMknTjH347FBZUE82nNEby
3 tasks
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
2 participants
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.
Summary
Ledger reconciliation for the dashboard task "LACosmic per-frame CR masking option + decouple PSF-star pass from the science CR pass". Both halves of the prompt shipped as PyAutoReduce#66 (merged 2026-08-06) from a
/wake_upsession branch, but the prompt never advanced out ofdraft/, so the dashboard kept listing it as not-started.complete/2026/08/lacosmic-cr-option-and-star-pass-decoupling.mdvialifecycle.py record(index refreshed in the same step);lifecycle.py checkgreen.dashboard.md— the task no longer appears in the draft listing.cr_method: "driz_cr" | "deepcr"dial with theresetbits=0trap pinned by test; thepsf_star_passdecoupling with always-recordedstar_source_passprovenance), the deliberate"deepcr"-not-"lacosmic"naming, and the reporter's 2026-08-09 grid correction on prompt: retire Codex skill wrapper rollout #61 (the ~37% erosion was a dither-erasing alignment artifact; the discriminating validation regime is poorly-dithered data).🤖 Generated with Claude Code
https://claude.ai/code/session_01DSnKLkkNeGriLFQNd8fKrc
Generated by Claude Code