prompt: untrack-fits-test-artifacts lifecycle (issued → shipped → complete) + PyAutoLens follow-up - #355
Merged
Conversation
Files the PyAutoArray FITS-test-artifact prompt as PyAutoArray#494, advances it draft/ → active/, registers it in active.md and regenerates the dashboard. The code audit narrowed the scope: of the 13 tracked output_test files, only structures/arrays/files/array/output_test/array.fits is a live output (the file #483 flipped). The other 12 are orphans no test in the repo references. The prompt's open question about test_uniform_1d.py:12 resolves the same way — that path is written, not read, so no file in the set is a real input. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoAeGsJyiaLG4oqXb9n3dM
Moves the task to library-shipped, awaiting-merge and records the PR.
Also files the sibling-sweep finding the task's scope note asked for. Neither
PyAutoGalaxy nor PyAutoLens carries this defect — both track zero test-output
artifacts and neither uses the output_test/ name — but PyAutoLens ignores only
the integration/ copies of data_temp/, while its tests write to
test_autolens/{imaging,interferometer}/data_temp/. The teardown rmtree hides
that on the happy path; a failed run leaks untracked files. Filed as its own
prompt rather than widening #495.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QoAeGsJyiaLG4oqXb9n3dM
PyAutoArray#495 merged as a5d718e; issue #494 closed. Records the task, releases the active.md claim, and regenerates the dashboard. Repoints the sibling follow-up prompt's back-reference at the record now that the task it was filed from has shipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoAeGsJyiaLG4oqXb9n3dM
Re-homes the sibling-sweep follow-up from draft/maintenance/libraries/ to draft/maintenance/autolens/ — the work touches exactly one repo, and autolens is an established target folder. Sets Target: accordingly and states the scope boundary up front, since the body's comparison table names PyAutoArray and PyAutoGalaxy as the contrast that isolates the defect, not as repos in scope. Applied by hand rather than via `intake --apply`: the classifier derives Target from repo names anywhere in the body, so the provenance citation of PyAutoArray#494 makes it resolve autoarray/autogalaxy/autolens and propose draft/maintenance/autoarray/. That would have widened Repos: to three and truncated the filename. The declared header stands. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoAeGsJyiaLG4oqXb9n3dM
…est-artifacts-r1eard # Conflicts: # dashboard.html # dashboard.md
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
Mind state for the
untrack-fits-test-artifactstask, which shipped asPyAutoArray#495 (merged as
a5d718e, issue#494 closed). Four commits carrying the full
lifecycle plus the follow-up the task's scope note asked for.
This branch exists because the session was pinned to it; the state it carries is ordinary
mainworkflow state, so it wants merging rather than reviewing as a change of intent.What's here
28099538draft/maintenance/libraries/→active/, registered inactive.md, dashboard regeneratedc40e92b0library-shipped, awaiting-merge,library-pr:recorded; files the sibling-sweep follow-up2b8bb712complete/2026/08/untrack-fits-test-artifacts.md, prompt folded and removed fromactive/,complete/index.mdrefreshed (1163 records),active.mdclaim released7c2ca365draft/maintenance/autolens/data_temp_write_paths_not_ignored.mdWhy the dashboard is committed rather than left to the refresh
dashboard_refresh.ymlheals a stale render on pushes tomain, but it lands a later bot commitand has to re-dispatch
pages_dashboard.ymlitself, so the Pages page lags until it does. Eachcommit above regenerates
dashboard.md+dashboard.htmlin the same commit as the change itrenders, per the intake and
/prmcontracts.intake dashboard --checkreports both current attip, and
lifecycle.py checkis OK.One note on the follow-up prompt
It was placed by hand rather than through
intake --apply. The classifier derivesTarget:fromrepo names anywhere in the body, so this prompt's provenance citation of PyAutoArray#494 — and its
comparison table naming PyAutoGalaxy — made it resolve
autoarray, autogalaxy, autolensand proposedraft/maintenance/autoarray/pyautolens_test_data_temp_write_paths_are.md. Applying that would havewidened
Repos:from one repo to three and truncated the filename. The work touches PyAutoLensonly, so the declared header stands and the file sits in
draft/maintenance/autolens/.That is a real gap in target classification — a prompt cannot cite a sibling repo's issue in its
provenance without being mis-targeted — but it is the classifier's to fix, not this prompt's, and it
is not filed here.
Generated by Claude Code