Skip to content

mind: record two completed tasks the online check surfaced #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jammy2211 merged 1 commit into from
Aug 8, 2026
Merged

mind: record two completed tasks the online check surfaced #162

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 0 additions & 44 deletions active.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,49 +1,5 @@
# Active Tasks

## ep-optimise-updater
- issue: https://github.com/PyAutoLabs/PyAutoFit/issues/1456
- status: COMPLETE 2026-08-08 — PyAutoFit #1457 merged first as 3b960609; autofit_workspace #136 then merged as cf8b4077. Required CI was green on both tested heads.
- library-pr: https://github.com/PyAutoLabs/PyAutoFit/pull/1457
- workspace-pr: https://github.com/PyAutoLabs/autofit_workspace/pull/136
- workspace-gate: cleared under explicit human acknowledgement — sandbox-only notebook IPC, broad AutoLens runtime, and branch-sensitive Heart limitations were documented before shipping. Library-first order was preserved.
- repos:
- PyAutoFit: feature/ep-optimise-updater
- autofit_workspace: feature/ep-optimise-updater
- summary: |
Expose the existing EP updater hierarchy through the declarative
FactorGraphModel.optimise() API. The public default remains updater=None,
so damping is opt-in and existing fits retain their current behaviour.
Library changes and seam tests land first; the workspace follows with an
undamped-by-default tutorial example showing the optional keyword.

## mge-sigma-min-workspace-sweep
- issue: https://github.com/PyAutoLabs/autolens_workspace/issues/466
- status: BOTH PHASES MERGED 2026-08-04. Phase 1 autolens_workspace#467 -> 92019316 (issue #466 auto-closed). Phase 2 autogalaxy_workspace#203 -> 8a7df7a6, HowToLens#67 -> 4ff3135c, HowToGalaxy#61 -> 51eed3d6, autogalaxy_assistant#10 -> f6966a64. Upstream PyAutoGalaxy#549 -> 13d3023c. All worktrees removed, all branches deleted local+origin, all five canonical checkouts back on main. Code work COMPLETE; two debts remain (below).
- phase-2-prs: autogalaxy_workspace#203 (28 files, `pending-release`) / HowToLens#67 (2 files, `pending-release`) / HowToGalaxy#61 (2 files, `pending-release`) / autogalaxy_assistant#10 (2 files, NO pending-release label — that repo does not define one, gate stated in the PR body instead). All four on branch feature/mge-sigma-min-workspace-sweep.
- phase-2-ci: THREE GREEN — agw#203, htl#67, htg#61 passed every check incl. both smoke matrix legs. aga#10 was MERGED WITH A RED wiki-currency check on explicit human instruction ("merge all"), failing `Version drift (--check-version)` ONLY — pre-existing, see DEBT 1. That red is now on autogalaxy_assistant main and persists for every future PR to that repo until the baseline is re-pinned.
- DEBT 1 of 2 CLEARED 2026-08-04 — assistant baseline re-pinned to the released 2026.8.4.1 stack via autogalaxy_assistant#11 (MERGED 9343e664). Regenerated in a CLEAN VENV with autogalaxy==2026.8.4.1, PYTHONPATH cleared and every module verified to resolve to venv site-packages — NOT from this workspace's source checkouts, which would have stamped the wrong version. Control-tested: old baseline exits 1 in that same venv (reproducing the CI failure), new one exits 0. All five wiki-currency checks pass on main. The re-pin surfaced a real API addition, `subplot_fit_imaging_list` in autogalaxy.plot (27 -> 28 symbols), which was undocumented — now documented in the same PR, and it corrected three stale claims incl. a pre-existing one about subplot_imaging_dataset_list's leaner signature. Original description follows: autogalaxy_assistant `wiki/core/api_audit_baseline.json` was generated 2026-08-01 pinning autogalaxy 2026.7.29.2; PyPI latest is now 2026.8.4.1 (released 2026-08-04). EVERY PR to that repo fails --check-version until the baseline is re-pinned. Proof it is not ours: the PR touches only 2 .md files, and symbol audit (--scope all) reports 0 missing/broken, provenance shows warnings only (no content_sha256 error), idioms clean.
- baseline-repin-TRAP: do NOT run `--write-baseline` from this workspace. It derives api_surface from the INSTALLED library, and local installs are the SOURCE checkouts (autogalaxy 2026.7.23.1), not the released 2026.8.4.1 that CI grades against — a local re-pin stamps the wrong version and turns the check green on a false premise. The re-pin must run against the released stack, as its own separate change.
- phase-2-result: autogalaxy_workspace 10 helper calls + 8 ladders; HowToLens 3 ladders (2 lens floored, 1 SOURCE -> -4, traced to source_bulge); HowToGalaxy 3 ladders all image-plane; autogalaxy_assistant 2 prose pages. Every autogalaxy_workspace MGE verified to attach to `galaxy = af.Model(ag.Galaxy, ...)` — PyAutoGalaxy has no lensing so no source plane exists to exclude. Validation: pyflakes zero introduced undefined names, 16/16 affected scripts pass smoke, notebooks regenerated 1:1 in all three repos with no orphan churn.
- assistant-provenance: wiki/core/concepts/linear_light_profiles_and_mge.md is provenance-stamped and a content_sha256 mismatch is a CI ERROR. Handled: added autogalaxy/analysis/model_util.py to the cited PyAutoGalaxy paths (where sigma_min lives), re-pinned PyAutoGalaxy 13d3023c + autogalaxy_workspace 1f821ba, bumped last_updated, re-stamped via `python3 autoassistant/audit_skill_apis.py --write-provenance`. Audit exits 0, 0 missing/broken. NOTE wiki-currency CI has paired-PR support — it checks out any cited source repo having a branch matching the PR head, so the paired autogalaxy_workspace branch is the grading ground truth.
- gh-trap: autogalaxy_assistant has an SSH remote, so `gh pr create` fails with "none of the git remotes ... point to a known GitHub host". Create its PRs via `gh api repos/<owner>/<repo>/pulls --method POST --input <json>` instead.
- assistant-false-positive: skills/ag_multi_dataset.md matches a `1e-4` grep but it is an intensity LogUniformPrior bound, NOT a sigma floor — deliberately untouched.
- RELEASE DEBT — DISCHARGED 2026-08-07 by publishing 2026.8.7.1 (all five libraries, PyPI). PROVEN, not inferred: downloaded the released `autogalaxy-2026.8.7.1-py3-none-any.whl` from PyPI and confirmed `sigma_min: float = 1e-4` in `autogalaxy/analysis/model_util.py` `mge_model_from` (+ the >0.0 / <=mask_radius guards). A user on a released install no longer hits TypeError. Original description follows: `sigma_min` existed only on PyAutoGalaxy main, NOT in any released PyAutoGalaxy; autolens_workspace main calls it, so released installs raised TypeError until a release carrying #549 shipped. The `pending-release` gate was overridden on explicit human instruction 2026-08-04 with that consequence stated — same pattern as the 2026-08-03 override recorded under release-drive-2026-08-03. Publishing was the remedy, not a preference.
- phase-1-result: 130 lens call sites take `sigma_min=dataset.pixel_scales[0] / 10.0`; 102 source sites untouched. 27 hand-rolled ladders: 10 image-plane floored, 17 source moved -2 -> -4. Classifier control-tested against the 88 explicitly-named sites first (88/88 agree, 0 disagree) before being trusted on the 143 bare `bulge` sites. Validation: 93 scripts byte-compile, pyflakes zero introduced undefined names across all 93, all 22 affected smoke scripts pass, notebooks regenerated 93-for-93 with no unrelated churn.
- heart-ack (2026-08-04): shipped under human-acknowledged YELLOW (score 70, `red_reasons: []`). Acknowledged reasons: (1) "workspace validation not passing (3 failed, 3 timeout, cloud#30858578587: autofit_test scripts/jax_assertions/multi_start_gradient_auto_convergence.py, autolens_test scripts/imaging/pixelization.py, autolens_test scripts/imaging/regularization.py, +3 more)"; (2) "manifest drift: tenant firewall (organ code) — 2 mismatch(es) vs PyAutoMind/repos.yaml"; (3) "release validation stale: source moved since rehearsal (PyAutoFit, PyAutoGalaxy, PyAutoLens)". None caused by this task; (3) is partly this day's own PyAutoGalaxy#549 merge. The ack covers THIS reason set only.
- OUTSTANDING DEBT 2 of 2 — markdown-DEFERRED (human decision 2026-08-04): markdown/ NOT regenerated. 7 of the 30 curated markdown_examples.yaml entries are among the changed scripts (start_here.py, imaging/start_here.py, imaging/modeling.py, multi_dataset/start_here.py, multi_dataset/modeling.py, group/start_here.py, group/modeling.py). generate_markdown.py refuses to run under PYAUTO_TEST_MODE (it executes scripts for real to render images) and a fresh worktree has no output/ resume cache, so a pass means real fits. Those 7 pages show snippets WITHOUT sigma_min until regenerated — outstanding debt, do not assume it is done.
- smoke-trap: the 3 scripts declaring `ENV: full_datasets` (group/, imaging/, multi_dataset/ start_here.py) FAIL with an unrelated IndexError (dataset capped to 16px vs a 209px mask) if run with PYAUTO_SMALL_DATASETS=1. Reproduced on pristine main, so it is a runner-env artefact, NOT a code bug — honour the in-file ENV declaration when smoke-running these.
- prompt: active/mge_sigma_min_workspace_sweep.md
- worktree: ~/Code/PyAutoLabs-wt/mge-sigma-min-workspace-sweep
- upstream: PyAutoGalaxy#549 MERGED 2026-08-04 (13d3023c) added `sigma_min` to `mge_model_from` (default 1e-4) and `mge_point_model_from` (default 0.01). Library defaults deliberately unchanged so archived runs keep their PyAutoFit identifiers — verified bit-identical across 1440 configs, and locked by a regression test in that PR. Nothing improves for users until the examples pass the argument; this task is that sweep.
- phases: 1 autolens_workspace (234 helper call lines + 23 hand-rolled ladder files — all the judgement) → 2 the mirror (autogalaxy_workspace, HowToLens, HowToGalaxy, autogalaxy_assistant prose). Phase 2 starts only once phase 1 merges.
- source-rule (human decision 2026-08-04): source-plane MGEs are EXCLUDED and keep the -4 default — the source is lensed, so magnification samples the source plane far finer than the image pixel scale and a pixel-scale floor would truncate real source structure. Only image-plane (deflector / galaxy light) MGEs take `sigma_min=dataset.pixel_scales[0] / 10.0`.
- classification-trap: this is NOT a regex sweep. Of 234 call lines: 59 explicitly source-named, 29 `lens_bulge`, 143 bare `bulge` needing per-call-site tracing to `lens=`/`source=af.Model(al.Galaxy...)`. scripts/multi_galaxy/modeling.py reuses the SAME name `bulge` for a lens galaxy (line 451) and the source (line 478) — a blind sweep wrongly ties ~100 source MGEs to the pixel scale.
- RESOLVED 2026-08-04 (was the one open question): hand-rolled SOURCE ladders move from -2 to -4, matching the helper they exist to teach. Human chose option 2. This DOES change behaviour in those ~10-14 tutorial sites — deliberately, since the files are pedagogical mirrors of `mge_model_from` and silently disagreeing with it is the inconsistency the sweep removes. Hand-rolled IMAGE-PLANE ladders still move to `np.log10(dataset.pixel_scales[0] / 10.0)`.
- out-of-scope this pass: autolens_workspace_test, autogalaxy_workspace_test, autolens_workspace_developer, autolens_profiling, euclid_strong_lens_modeling_pipeline — changed ladders change fit results there, needs separate re-baselining decision.
- sizing-note: Brain said too-large (16) and proposed design/core-API/examples/docs phases; NOT taken — score is prose-driven, the API shipped in #549, no design remains. Human-scoped 2-phase split by repo kept (point-source-defaults-campaign precedent).
- claim-released (2026-08-04): autolens_workspace dropped from `repos:` — phase 1 PR #467 MERGED, branch deleted on origin, canonical checkout back on main at 92019316. Phase 2 claims a different repo set and will register its own.
- repos-none-claimed: phase 2 has not started, so this entry claims NO repos — listed on this one line deliberately, NOT as 2-space ` - Repo` bullets, because worktree_check_conflict reads any such bullet as a live claim.

## release-drive-2026-08-03
- issue: (no issue — a human-authorized manual release drive, not a dev task)
- session: claude --resume e0105850-b98b-47ff-9ada-cba04a455a65
Expand Down
Loading
Loading