feat: re-birth autolens_visualization as the lens project repo (PyAutoEyes 1a)

[Jammy2211]

Overview

Phase 1a of the pyautoeyes-birth epic, under the layered design the human chose on 2026-09-28: project repos <lib>_visualization make, store and track one library's figures; the organ PyAutoEyes is the cross-project dashboard that reads each project repo's tracked manifest and links to its PNGs (it renders nothing and copies no figures). This task puts the lens content back into its own project repo, PyAutoLabs/autolens_visualization, adds the tracked gallery/viz_manifest.yaml read contract, and registers the repo across Mind, Brain and Heart. Phase 1b (stripping the organ to its skeleton) must not start until this is merged.

Classification: feature, medium, direct; workflow library (start_library → ship_library). Autonomy: supervised.
Feature Agent risk note: "Public-API change may ripple to downstream repos". It does not: this task changes no library code (PyAutoFit/Array/Galaxy/Lens untouched), so nothing ripples downstream.
Heart at the door: YELLOW — "PyAutoMemory: open PR 7d old (updated 5h ago)".
Parallel claim: human-approved 2026-09-28 over PyAutoMind / PyAutoBrain / PyAutoHeart alongside eyes-organ-order (#439). The only overlap is Mind repos.yaml: #439 reorders the organ rows; 1a adds a project row after autolens_inference and rewrites the PyAutoEyes role string.

Already done this session:

• The human ran gh repo create PyAutoLabs/autolens_visualization --public.
• The current PyAutoEyes main history (8f3e712) was pushed to it. git ls-remote shows refs/heads/main 8f3e7124dc….
• Cloned at lens/autolens_visualization (origin = the new repo, 40 PNGs present).

Plan

1. Push the PyAutoEyes history to the new project repo and clone it at lens/autolens_visualization (done).
2. In autolens_visualization: retitle README/AGENTS/CLAUDE stub to the project-repo role, with the layering stated. The gallery builder writes a tracked gallery/viz_manifest.yaml (content hashes + rendered stack version), and --check fails on a stale manifest. render.yml commits it and fires an eyes-refresh repository_dispatch at PyAutoEyes.
3. PyAutoMind: project row after autolens_inference (using the autolens_profiling row as the template), PyAutoEyes role rewritten to the dashboard wording, ROUTING target, then repos_sync --write and propagation.
4. PyAutoBrain: Eyes conductor AGENTS.md + skills/eyes/eyes.md default instance → lens/autolens_visualization, with the layering paragraph; bin/clean_slate.sh exclusion comment/path.
5. PyAutoHeart: the config/repos.yaml excluded list gains autolens_visualization beside autolens_profiling.
6. Ship Mind → Brain → Heart → autolens_visualization as separate PRs, with the witness from the prompt.

Detailed implementation plan

Affected Repositories

• autolens_visualization (primary)
• PyAutoMind
• PyAutoBrain
• PyAutoHeart

Branch Survey

Repository	Current Branch	Dirty?
./lens/autolens_visualization	main (8f3e712)	clean
./organs/PyAutoMind	main (1f07d34)	clean
./organs/PyAutoBrain	main (2139521)	clean
./organs/PyAutoHeart	main (a95ebc9)	clean

PyAutoMind/PyAutoBrain/PyAutoHeart are also claimed by eyes-organ-order (#439) on feature/eyes-organ-order. A parallel worktree was human-approved on 2026-09-28 (overlap: Mind repos.yaml only).

Suggested branch: feature/autolens-visualization-rebirth (all four repos)
Worktree root: ~/Code/PyAutoLabs-wt/autolens-visualization-rebirth (created by start_library)

Implementation Steps

Human first, quoted verbatim for the session:

1. gh repo create PyAutoLabs/autolens_visualization --public

Agent, after the human confirms the empty repo exists:

1. History carries over. From the current organs/PyAutoEyes checkout
   (clean, in sync with origin/main), add the new repo as a remote and push
   the current main history to it — git remote add autolens_visualization https://github.com/PyAutoLabs/autolens_visualization.git && git push autolens_visualization main — so every PNG keeps its provenance (PR docs: update stale admin_jammy/prompt/ refs to PyAutoPrompt/ #1,
   the phase-0 commits). Then clone it to lens/autolens_visualization
   (origin = the new repo). PyAutoEyes main is left untouched here; phase 1b
   strips it.

2. In lens/autolens_visualization (task worktree, one PR):

   • README.md / AGENTS.md (+ CLAUDE.md stub) retitled to
     autolens_visualization, the layering stated: a project repo that owns
     the lens figures — producers, simulators, datasets, plots.yaml,
     instruments, tracked PNGs, GALLERY.md, the render harness — while the
     organ PyAutoEyes only aggregates it on its dashboard. Remove organ prose
     inherited from phase 0 (registry, board, "every library").
   • Tracked manifest. gallery/gallery_build.py writes
     viz_manifest.yaml to a tracked path (gallery/viz_manifest.yaml),
     carrying every figure it holds (producer, domain, relative PNG path,
     size, mtime-free content hash) plus the rendered stack version;
     output/gallery/gallery.html stays gitignored. render.yml commits the
     manifest alongside the PNGs and GALLERY.md. --check fails on a stale
     manifest. This is the organ's read contract (phase 1b reads it).
   • render.yml: keep the pyautolens-release repository_dispatch (plain
     git PNGs, no LFS); add a final step that fires a repository_dispatch
     (eyes-refresh) at PyAutoEyes so its dashboard refreshes (Cortex
     pattern; token as the other cross-repo dispatches use).
   • _viz_cli.py kept; activate.sh, lint.yml unchanged except names.
     Keep dataset/imaging/hst byte-identical to profiling (never
     re-simulate).

3. PyAutoMind — mirror the feat: birth autolens_visualization — permanent figure gallery repo #436 registration set
   (complete/2026/09/autolens-visualization-birth.md): repos.yaml row
   after autolens_inference, template the autolens_profiling row —

   autolens_visualization:
     path: lens/autolens_visualization
     github: PyAutoLabs/autolens_visualization
     category: project
     role: "Rendered PyAutoLens figures — every visualizer output on realistic HST-scale imaging and SMA interferometer data, the producers and harness that render them, re-rendered on each release; aggregated by the PyAutoEyes dashboard."

   and the PyAutoEyes role rewritten to the layered wording (the
   cross-project visualization dashboard over the <lib>_visualization
   project repos: registry, manifest contract, Pages board; renders nothing,
   never judges, never edits plot code). ROUTING.md target list gains
   autolens_visualization. Then python3 scripts/repos_sync.py --write
   and propagate the generated map blocks / organ tables to their repos
   (watch the --write-from-bundle spill into canonical checkouts).

4. PyAutoBrain — Eyes conductor prose
   (agents/conductors/eyes/AGENTS.md, skills/eyes/eyes.md): default
   instance → lens/autolens_visualization, with the layering in one
   paragraph (project repos hold the figures; the organ PyAutoEyes is the
   dashboard; the registry that lists instances arrives in phase 2);
   bin/clean_slate.sh dataset-wipe exclusion for the new path. _eyes.py
   stays repo-name-free.

5. PyAutoHeart — config/repos.yaml drift exclusion / organism list entry
   for autolens_visualization, as feat: birth autolens_visualization — permanent figure gallery repo #436 had it.

Ship policy: PR order Mind → Brain → Heart → autolens_visualization. While Heart is RED, the PRs ship only under a contemporaneous human RED override. Merging stays human (/prm).

Witness: bash gallery/gallery_run.sh --all in lens/autolens_visualization reproduces the 40 PNGs (a byte-diff is acceptable only in the version string) and writes the tracked gallery/viz_manifest.yaml. python3 organs/PyAutoMind/scripts/repos_sync.py --check is clean (except the pre-existing hub-blurb leg, if it is still red). pyauto-brain eyes survey lens/autolens_visualization reports no gaps and no orphans.

Key Files

• lens/autolens_visualization/README.md, AGENTS.md, CLAUDE.md — retitle to the project-repo role
• lens/autolens_visualization/gallery/gallery_build.py — tracked gallery/viz_manifest.yaml + --check staleness
• lens/autolens_visualization/.github/workflows/render.yml — commit the manifest; eyes-refresh dispatch to PyAutoEyes
• organs/PyAutoMind/repos.yaml, ROUTING.md — project row, PyAutoEyes role, routing target
• organs/PyAutoBrain/agents/conductors/eyes/AGENTS.md, skills/eyes/eyes.md, bin/clean_slate.sh — default instance + layering
• organs/PyAutoHeart/config/repos.yaml — excluded-list entry

Original Prompt

Click to expand starting prompt

PyAutoEyes phase 1a — re-birth autolens_visualization as the lens project repo

Type: feature
Target: autolens_visualization
Repos:

• autolens_visualization
• PyAutoMind
• PyAutoBrain
• PyAutoHeart
  Themes:
• visualization
• infrastructure
  Difficulty: medium
  Autonomy: supervised
  Priority: high
  Lane: local-dev
  Status: draft
  Consequence: judge
  Witness: bash gallery/gallery_run.sh --all in lens/autolens_visualization reproduces the 40 PNGs (byte-diff acceptable only in the version string) and writes the tracked gallery/viz_manifest.yaml; python3 organs/PyAutoMind/scripts/repos_sync.py --check clean (bar the pre-existing hub-blurb leg, if still red); pyauto-brain eyes survey lens/autolens_visualization reports no gaps and no orphans
  Review-minutes: 15
  Epic: pyautoeyes-birth
  Phase: 1a
  Filed: 2026-09-28

Blocked on: human repo creation (gh repo create PyAutoLabs/autolens_visualization --public — the agent is denied gh repo create).

Layering (human decision 2026-09-28)

Two layers, the same shape as autolens_profiling / autolens_inference
under the Brain board. Project repos <lib>_visualization make, store and
track the figures of one library. The organ PyAutoEyes is the cross-project
dashboard that reads every project repo's tracked manifest and links to its
PNGs; it renders nothing and copies no figures. This phase puts the lens
content back into its own project repo; phase 1b strips the organ to its
skeleton.

Task

Human first, quoted verbatim for the session:

1. gh repo create PyAutoLabs/autolens_visualization --public

Agent, after the human confirms the empty repo exists:

1. History carries over. From the current organs/PyAutoEyes checkout
   (clean, in sync with origin/main), add the new repo as a remote and push
   the current main history to it — git remote add autolens_visualization https://github.com/PyAutoLabs/autolens_visualization.git && git push autolens_visualization main — so every PNG keeps its provenance (PR docs: update stale admin_jammy/prompt/ refs to PyAutoPrompt/ #1,
   the phase-0 commits). Then clone it to lens/autolens_visualization
   (origin = the new repo). PyAutoEyes main is left untouched here; phase 1b
   strips it.

2. In lens/autolens_visualization (task worktree, one PR):

   • README.md / AGENTS.md (+ CLAUDE.md stub) retitled to
     autolens_visualization, the layering stated: a project repo that owns
     the lens figures — producers, simulators, datasets, plots.yaml,
     instruments, tracked PNGs, GALLERY.md, the render harness — while the
     organ PyAutoEyes only aggregates it on its dashboard. Remove organ prose
     inherited from phase 0 (registry, board, "every library").
   • Tracked manifest. gallery/gallery_build.py writes
     viz_manifest.yaml to a tracked path (gallery/viz_manifest.yaml),
     carrying every figure it holds (producer, domain, relative PNG path,
     size, mtime-free content hash) plus the rendered stack version;
     output/gallery/gallery.html stays gitignored. render.yml commits the
     manifest alongside the PNGs and GALLERY.md. --check fails on a stale
     manifest. This is the organ's read contract (phase 1b reads it).
   • render.yml: keep the pyautolens-release repository_dispatch (plain
     git PNGs, no LFS); add a final step that fires a repository_dispatch
     (eyes-refresh) at PyAutoEyes so its dashboard refreshes (Cortex
     pattern; token as the other cross-repo dispatches use).
   • _viz_cli.py kept; activate.sh, lint.yml unchanged except names.
     Keep dataset/imaging/hst byte-identical to profiling (never
     re-simulate).

3. PyAutoMind — mirror the feat: birth autolens_visualization — permanent figure gallery repo #436 registration set
   (complete/2026/09/autolens-visualization-birth.md): repos.yaml row
   after autolens_inference, template the autolens_profiling row —

   autolens_visualization:
     path: lens/autolens_visualization
     github: PyAutoLabs/autolens_visualization
     category: project
     role: "Rendered PyAutoLens figures — every visualizer output on realistic HST-scale imaging and SMA interferometer data, the producers and harness that render them, re-rendered on each release; aggregated by the PyAutoEyes dashboard."

   and the PyAutoEyes role rewritten to the layered wording (the
   cross-project visualization dashboard over the <lib>_visualization
   project repos: registry, manifest contract, Pages board; renders nothing,
   never judges, never edits plot code). ROUTING.md target list gains
   autolens_visualization. Then python3 scripts/repos_sync.py --write
   and propagate the generated map blocks / organ tables to their repos
   (watch the --write-from-bundle spill into canonical checkouts).

4. PyAutoBrain — Eyes conductor prose
   (agents/conductors/eyes/AGENTS.md, skills/eyes/eyes.md): default
   instance → lens/autolens_visualization, with the layering in one
   paragraph (project repos hold the figures; the organ PyAutoEyes is the
   dashboard; the registry that lists instances arrives in phase 2);
   bin/clean_slate.sh dataset-wipe exclusion for the new path. _eyes.py
   stays repo-name-free.

5. PyAutoHeart — config/repos.yaml drift exclusion / organism list entry
   for autolens_visualization, as feat: birth autolens_visualization — permanent figure gallery repo #436 had it.

Ship policy

PR order Mind → Brain → Heart → autolens_visualization. While Heart is RED the
PRs ship only under a contemporaneous human RED override. Merge stays human
(/prm). Phase 1b must not start deleting organ content until this phase is
merged and the history is confirmed on the new repo (git ls-remote).

[Jammy2211]

Library PRs Created (phase 1a)

• PyAutoMind#447 — register autolens_visualization; PyAutoEyes role → cross-project dashboard
• PyAutoBrain#426 — Eyes conductor / /eyes default instance → lens/autolens_visualization
• PyAutoHeart#240 — exclude autolens_visualization from polling
• autolens_visualization#1 — tracked gallery/viz_manifest.yaml (PyAutoEyes read contract)

API changes: none — internal only; no workspace-script impact (no /start_workspace needed).
Heart: YELLOW, human-acknowledged 2026-09-28 (recorded as heart-ack: in active.md).
Note: Mind#447's firewall leg is red until Brain#426 merges (CI reads Brain main's organism-map block). Merge Brain first, or re-run it after.
Merge stays human → /prm. After that, the map-block follow-up PRs go out from tmp/handover/map-block-*.patch.

🤖 Generated with Claude Code

[Jammy2211]

Parallel claim on PyAutoBrain (human-approved 2026-09-28): task eyes-organ-skeleton (#448, PyAutoEyes phase 1b) branches feature/eyes-organ-skeleton in PyAutoBrain. There is no file overlap: it touches only tests/test_policy_seams.py and config/policy.yaml (moving PyAutoEyes from WITNESS_EXEMPT to a test_witness row).

[Jammy2211]

Body-map propagation after #447/#449 — map-block PR status (from repos_sync --write on Mind main 76ef959a)

PR	File	State
PyAutoLabs/PyAutoNerves#178	AGENTS.md	Verified byte-identical to --write output — clear to merge
PyAutoLabs/PyAutoGut#14	AGENTS.md	Verified byte-identical to --write output — clear to merge
PyAutoLabs/PyAutoScientist#36	README.md	Verified byte-identical to --write output — clear to merge
PyAutoLabs/PyAutoCortex#47 (new)	AGENTS.md	Opened from the --write diff (byte-identical), label pending-release
PyAutoBrain	AGENTS.md	No PR needed — map block already current on main (--write reported unchanged)
.github profile/README.md	—	Human-only (checkout on feature/pyautoeyes-birth-organ-row); --write diff saved to tmp/handover/map-block-dotgithub-post449.patch (moves the Eyes row after Memory, and updates its text)

Remaining --check red legs: organism-map (Cortex/Nerves/Gut) and front-door tables (Scientist, .github) clear when the PRs above merge and the .github patch is applied. The generated-hooks leg (38 copies) is still red: session_hook_propagate.yml did not run on the #449 merge — no push-event workflow ran on 76ef959a at all (only the Pages Dashboard dispatch), so the organ-order hook change was never propagated. It needs a manual gh workflow run session_hook_propagate.yml -R PyAutoLabs/PyAutoMind (human decision; not dispatched by this session).

🤖 Generated with Claude Code

https://claude.ai/code/session_01CpGs8DxC5qA1MtHcmHeaBQ

[Jammy2211]

Shipped (phase 1a of pyautoeyes-birth)

All four task PRs merged by the human via /prm (2026-09-28):

• repos: register autolens_visualization project repo; PyAutoEyes role → cross-project dashboard (#446) #447 (9fe391ad): registers autolens_visualization in repos.yaml (project row after autolens_inference); PyAutoEyes role is now the cross-project dashboard
• eyes: default instance → lens/autolens_visualization; layered project-repo/organ prose (PyAutoMind#446) PyAutoBrain#426 (d8710e42): Eyes conductor and /eyes default instance point at lens/autolens_visualization; layering paragraph; clean_slate.sh exclusion
• config: exclude autolens_visualization project repo from polling (PyAutoMind#446) PyAutoHeart#240 (cfbe3d41): autolens_visualization excluded from polling / on the organism list
• gallery: tracked viz_manifest.yaml (PyAutoEyes read contract); project-repo role (PyAutoMind#446) autolens_visualization#1 (0e96a285): tracked gallery/viz_manifest.yaml, which the PyAutoEyes organ reads; render.yml commits it and fires eyes-refresh

Each branch tip is proven an ancestor of origin/main (git merge-base --is-ancestor) in every repo.

Map-block follow-ups (from repos_sync --write after #447/#449):

• Merged: chore: organism map — autolens_visualization row + PyAutoEyes dashboard role (PyAutoMind#447) PyAutoNerves#178, chore: organism map — autolens_visualization row + PyAutoEyes dashboard role (PyAutoMind#447) PyAutoGut#14, chore: organism map — autolens_visualization row + PyAutoEyes dashboard role (PyAutoMind#447) PyAutoScientist#36
• Open: chore: organism map — regenerate after PyAutoMind#447/#449 PyAutoCortex#47 (organism map regen), merge pending
• Human-only: .github profile/README.md. Apply tmp/handover/map-block-dotgithub-post449.patch (agents are denied any .github org-profile touch)
• Still red: the generated-hooks leg, until someone runs gh workflow run session_hook_propagate.yml -R PyAutoLabs/PyAutoMind by hand (a human decision)

Human notes

• PAT: the eyes-refresh dispatch in render.yml warns and skips until PAT_PYAUTOLABS covers PyAutoEyes and the secret is available to autolens_visualization. Add both repos to the PAT's repo list.
• Pages: enabling GitHub Pages for the PyAutoEyes dashboard is a human step (agents are denied POST /pages). It lands with phase 1b / 2.

Layering (human decision 2026-09-28): project repos <lib>_visualization make, store and track the figures. The organ PyAutoEyes is the cross-project dashboard that reads each repo's tracked manifest and renders nothing.

Next: phase 1b, PyAutoMind#448 (eyes-organ-skeleton), is in flight (shipped, awaiting merge). Then phase 2.

Pending release (carried into the record): PyAutoMind#447, PyAutoBrain#426, PyAutoHeart#240, autolens_visualization#1.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CpGs8DxC5qA1MtHcmHeaBQ