LEAP

Reorganizes LEAP documentation—canonical locations, INDEX updates, superseded banners, archive vs dev_notes. Use when cleaning up docs, consolidating guides, marking files obsolete, or resolving duplicate how-tos.

Runs a short LEAP pre-merge release gate—CHANGELOG, migrations, docs touchpoints, lint, typecheck, tests. Use when the version bump and README narrative are already handled (e.g. via leap-version-bump) or for a quick final checklist before merge.

Ships a product update: derives a short business summary from changed files, audits docs for stale version or mismatched behavior, bumps semver in pyproject/README/CHANGELOG and other stamped docs, then verifies with grep and make checks. Use when releasing, bumping version, updating README “what’s new”, or syncing docs after a feature merge.

Debugs stuck or failed LEAP recording pipelines—Celery queues, pipeline stages, and log correlation. Use when a recording fails mid-flight, a Celery task errors, workers seem idle, or the user asks to trace download through upload.