fix: regenerate stale navigator catalogue (Navigator Check RED on main)

[Jammy2211]

Overview

The Navigator Check Catalogue staleness job is RED on autofit_workspace main (commit 831b08b, the feature/ep-statistics-completion #85 merge). The EP work added scripts/features/expectation_propagation.py and a cross-ref from scripts/features/graphical_models.py, but the generated navigator catalogue (llms-full.txt, workspace_index.json) was never regenerated and committed. Surfaced by the 2026-07-11 morning /health sweep. This regenerates the catalogue so CI goes green.

Plan

• Branch feature/autofit-navigator-catalogue-refresh off origin/main.
• Run regenerate_navigator.py autofit (Phase 2 — no notebook rebuild, matches CI).
• Commit only the two regenerated catalogue files; open a pending-release PR.
• Merge stays human (--auto ends at PR-open).

Detailed implementation plan

Affected Repositories

• autofit_workspace (primary)

Branch Survey

Repository	Current Branch	Dirty?
./autofit_workspace	feature/autofit-navigator-catalogue-refresh (off origin/main @ 831b08b)	clean (catalogue-only)

Suggested branch: feature/autofit-navigator-catalogue-refresh

Implementation Steps

1. From the workspace root: python ../PyAutoBuild/autobuild/regenerate_navigator.py autofit.
2. Stage only llms-full.txt and workspace_index.json (ignore regenerated dataset/ / output/ runtime noise).
3. Open pending-release PR to main.

Verification (all green locally)

• check_navigator.py --root . --banners=fail → OK (paths + banners).
• Second regenerate_navigator.py autofit is idempotent (no further drift) → the CI "Catalogue staleness" diff-check will pass.
• Diff is +28/-1: a new expectation_propagation.py catalogue entry (title, summary, cross_refs → graphical_models) and graphical_models.py's cross_refs gains features/expectation_propagation.py.

Key Files

• llms-full.txt — regenerated catalogue (generated artifact).
• workspace_index.json — regenerated catalogue (generated artifact).

Conflict note

autofit_workspace is co-claimed by the parked markdown-renderings-workspaces task, but that branch touches only README.md, config/build/markdown_examples.yaml, and markdown/** — not the catalogue. The two branches are file-disjoint; human-approved to proceed in parallel (2026-07-11).

Original Prompt

Click to expand starting prompt

Fix autofit_workspace Navigator Check RED on main: the navigator catalogue (llms-full.txt, workspace_index.json) is stale after the EP #85 merge — graphical_models.py cross-refs features/expectation_propagation.py but the catalogue was never regenerated. Regenerate with regenerate_navigator.py autofit and commit the result. --auto

🤖 Generated with Claude Code

[Jammy2211]

Shipped to PR-open (--auto, safe): #87 (pending-release, catalogue-only).

Regenerated llms-full.txt + workspace_index.json (+28/-1); the Navigator Check Catalogue staleness job — the one that was RED on main — now passes on the PR. Ship gate: tests n/a (generated-artifact-only) · smoke n/a (no script surface) · review CLEAN (deterministic regen, check_navigator green, idempotent) · Heart YELLOW acknowledged for the 5-reason standing set (the sole hard-RED driver, a stale local PyAutoFit checkout, was ff-synced pre-ship).

Merge stays human — validation checklist is on #87.