chore: route resolved Sersic gradient reconciliation

Author: Jammy2211

active.md

@@ -60,3 +60,14 @@
 - artifacts-are-laptop-only: Actions artifact downloads are blocked from cloud/mobile sessions (egress policy 403s `productionresultssa2.blob.core.windows.net` on CONNECT) — this is what stopped the cloud session finishing the ingest. Both wiki drift reports were captured to `~/.pyauto-heart/release_20260807_wiki_drift/` while on the laptop.
 - do-not: do NOT use the nightly driver for a manual release — AUTONOMY.md forbids converting a manual release into the scheduled-nightly exception.
 - repos-none-claimed: this entry claims NO repos — deliberately on one line, NOT as 2-space `  - Repo` bullets, because `worktree_check_conflict` treats any such bullet as a live claim.
+
+## resolve-sersic-ell-comps-gradient
+- issue: https://github.com/PyAutoLabs/autolens_profiling/issues/123
+- prompt: active/resolve_sersic_ell_comps_gradient.md
+- session: chatgpt-work
+- status: workspace-dev
+- validation: pending
+- source-fix: https://github.com/PyAutoLabs/PyAutoGalaxy/pull/571
+- repos:
+  - autolens_profiling: maintenance/resolve-sersic-ell-comps-gradient
+

active/resolve_sersic_ell_comps_gradient.md

@@ -0,0 +1,17 @@
+# Reconcile the resolved Sersic ell_comps gradient finding
+
+Type: maintenance
+Target: autolens_profiling
+Repos:
+- autolens_profiling
+Difficulty: small
+Autonomy: supervised
+Priority: high
+Status: issued
+Source: PyAutoGalaxy#571 · autolens_profiling finding `likelihood.imaging-sersic.ell-comps-origin-nonfinite-gradient`
+
+PyAutoGalaxy#571 replaced the Sersic image path's singular Cartesian-to-polar ellipticity conversion with an algebraically equivalent Cartesian eccentric-radius calculation. The complete off-centre likelihood remains `-15.477240141252718` at `ell_comps=(0, 0)`, while the JAX gradient is now finite at `[1.1569945714414, -0.5449763942867472]`.
+
+Make the stable detector conditional on the origin gradient still being non-finite while its bounded neighbourhood is finite. Retain the finding ID for regression detection, regenerate the complete NumPy/JAX evidence against the merged source fix, remove the resolved record and plot, and refresh the semantic index and generated README table.
+
+Cover both persistence branches with pure synthetic unit tests. Do not change PyAutoGalaxy, priors, configuration, or numerical behavior. Label the profiling PR `pending-release` and merge it only after exact-head CI is green.