Skip to content

mind: record the shipped min-version draft, add issues --drafts, dedupe - #164

Merged
Jammy2211 merged 1 commit into
mainfrom
claude/automind-task-planning-57sqpo
Aug 8, 2026
Merged

mind: record the shipped min-version draft, add issues --drafts, dedupe#164
Jammy2211 merged 1 commit into
mainfrom
claude/automind-task-planning-57sqpo

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Follows the draft/ rot noticed while closing out #163. draft/ is graded by no check at all, and it carries shipped work too.

minimum_library_version_adoption was shipped three weeks ago

It sat in draft/feature/workspaces/ with Priority: high while all three legs of its scope had been delivered. Verified across every repo it names, not inferred from one:

  • The key is adopted in all sevenversion.minimum_library_version: 2026.7.9.1 in config/general.yaml for autofit / autogalaxy / autolens workspaces, HowToFit, HowToGalaxy, HowToLens, euclid_strong_lens_modeling_pipeline.
  • The dead workspace_version key is gone. The only surviving matches are the explanatory comment and workspace_version_check — a different, still-live key (the documented bypass for main-branch clones, where mismatches are expected because main moves faster than releases).
  • version.txt is gone — HTTP 404 on main for the three sampled repos.

Recorded to complete/2026/07/, dated from autolens_workspace 21702119.

A duplicate draft

restore_multiple_sources_lensing_of_lens.md existed twice — under feature/autolens/ and feature/workspaces/. Same task: the autolens copy is the raw original (typos "acitually", "epxlpicit", no header), the workspaces copy is that text formalised by the Intake Agent on 2026-07-08. Dropped the raw one.

A scan across all 152 drafts for other duplicate basenames and identical bodies found no others.

issues --drafts

Extends the online cross-check to draft prompts citing a GitHub issue.

Advisory, and never affects the exit code — because the signal genuinely differs. A registry entry's issue: is its own tracking issue, so closed means done. A draft usually cites an issue as context ("Once #480 is fixed…", "Follow-up to #57"), so closed can mean the draft is newly unblocked rather than finished. Both readings deserve a human look; neither is a gate.

This is a partial net by construction: only 9 of 152 drafts cite an issue at all. minimum_library_version_adoption cited none, so this check would not have caught it — that one needed reading the seven configs.


lifecycle check → OK. pytest tests/ → 112 passed (3 new).


Generated by Claude Code

…dupe

Follows the draft/ rot noticed while closing out the orphan triage. draft/
is graded by NO check at all, and it carries shipped work too.

minimum_library_version_adoption was sitting in draft/feature/workspaces/
with Priority: high while all three legs of its scope had been delivered
three weeks earlier. Verified across every repo it names, not inferred from
one:

  * version.minimum_library_version: 2026.7.9.1 present in config/general.yaml
    in all SEVEN -- autofit/autogalaxy/autolens workspaces, HowToFit,
    HowToGalaxy, HowToLens, euclid_strong_lens_modeling_pipeline
  * the dead `workspace_version` key is gone. The only surviving matches are
    the explanatory comment and `workspace_version_check`, a different and
    still-live key (the documented bypass for main-branch clones)
  * version.txt is gone -- HTTP 404 on main for the three sampled repos

Recorded to complete/2026/07/, dated from autolens_workspace 21702119
"config: adopt version.minimum_library_version floor (2026.7.9.1)".

Also removes a duplicate draft: restore_multiple_sources_lensing_of_lens.md
existed twice, under feature/autolens/ and feature/workspaces/. They are the
same task -- the autolens copy is the raw original (typos "acitually",
"epxlpicit", no header), the workspaces copy is the same text formalised by
the Intake Agent on 2026-07-08. Dropped the raw one. A scan for other
duplicate basenames and identical bodies across all 152 drafts found no
others.

`issues --drafts` extends the online cross-check to draft prompts citing a
GitHub issue. It is ADVISORY and never affects the exit code, because the
signal genuinely differs: a registry entry's `issue:` is its own tracking
issue, so closed means done, but a draft usually cites an issue as CONTEXT
("Once #480 is fixed...") -- closed can mean newly UNBLOCKED rather than
shipped. Both readings deserve a look; neither is a gate. Only 9 of 152
drafts cite an issue at all, so this is a partial net by construction.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GW2wFpSkZtXr8VzM5w8MpX
@Jammy2211
Jammy2211 merged commit e2f9327 into main Aug 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants