Skip to content

chore: entry-point cleanup — delete run_search.py, prune one-off console scripts#10

Merged
wiyth00 merged 2 commits into
mainfrom
chore/entry-point-cleanup
Jul 25, 2026
Merged

chore: entry-point cleanup — delete run_search.py, prune one-off console scripts#10
wiyth00 merged 2 commits into
mainfrom
chore/entry-point-cleanup

Conversation

@wiyth00

@wiyth00 wiyth00 commented Jul 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • Delete run_search.py. It was a 9-line duplicate of the chained-eclipse console script already installed via [project.scripts].
  • Remove chained-eclipse-total-tracks-2027 and chained-eclipse-eclipse4-atlanta from [project.scripts]. They are one-off analyses that were being installed onto every user's PATH. The modules stay runnable via python -m chained_eclipse.total_tracks_2027 / python -m chained_eclipse.eclipse4_atlanta — which is already exactly how the README documents them — and the README now says explicitly that this is intentional.
  • README quick-start now uses uv run chained-eclipse --mode full, and the four "Reproducible modes" examples use .venv/bin/chained-eclipse --mode <mode> instead of the deleted script.

Work plan item P2 / 12.

Note: this touches [project.scripts] in pyproject.toml; #5 touches [project] dependencies. Different hunks, so whichever merges second should rebase cleanly.

Scientific impact

None. Entry-point metadata and documentation only; cli.main and all analysis modules are unchanged.

  • No change to computed results
  • Results change (described above)

Checklist

  • ruff check . passes
  • pytest passes locally
  • New or changed behaviour is covered by a test (n/a — no code behaviour change)
  • Docs / README updated if user-facing behaviour changed

Lint/test boxes left unchecked because this branch was pushed without a local run — CI on this PR is the first execution.

wiyth00 added 2 commits July 25, 2026 13:51
- Remove chained-eclipse-total-tracks-2027 and chained-eclipse-eclipse4-atlanta
  from [project.scripts]; they are one-off analyses and stay runnable via
  python -m chained_eclipse.<module>.
- Point the README quick-start and reproducible modes at the chained-eclipse
  console script instead of run_search.py (deleted in the next commit).
It duplicated the chained-eclipse console script installed by
[project.scripts]; the README now points at the console script.
@wiyth00
wiyth00 merged commit d9532c8 into main Jul 25, 2026
1 check passed
wiyth00 added a commit that referenced this pull request Jul 25, 2026
…--resume

Item 15:
- argparse --version prints package version, MODEL_VERSION, and kernel name.
- Stage progress messages use the logging module (INFO default, --quiet for
  warnings only, --verbose for debug). Data outputs (json dumps, headline)
  stay on stdout. terminal_summary.txt is byte-identical.

Deferred #12 follow-ups:
- --allow-unverified-ephemeris is wired through every mode's load_ephemeris.
- events.json records the kernel digest from the verified context (no
  re-hash) plus the new verified flag.
- run_manifest.json command string reflects the real entry point (the old
  string referenced run_search.py, deleted in #10) and records resume use.

Item 16:
- --resume reuses per-stage artifacts in --output when a resume_manifest
  records matching model_version, config sha256, and kernel sha256;
  refuses to resume across any mismatch. Stages 1 (enumeration/screening),
  2 (validation), 3 (optimized design), and 5 (stability) are
  checkpointable; stage 4 is always recomputed because fixed-system ground
  tracks are not serialized and downstream figures need them.
- New tests cover parser flags, the version string, a --version subprocess
  run, and the pure resume-guard helper.
wiyth00 added a commit that referenced this pull request Jul 25, 2026
#14)

Item 15:
- argparse --version prints package version, MODEL_VERSION, and kernel name.
- Stage progress messages use the logging module (INFO default, --quiet for
  warnings only, --verbose for debug). Data outputs (json dumps, headline)
  stay on stdout. terminal_summary.txt is byte-identical.

Deferred #12 follow-ups:
- --allow-unverified-ephemeris is wired through every mode's load_ephemeris.
- events.json records the kernel digest from the verified context (no
  re-hash) plus the new verified flag.
- run_manifest.json command string reflects the real entry point (the old
  string referenced run_search.py, deleted in #10) and records resume use.

Item 16:
- --resume reuses per-stage artifacts in --output when a resume_manifest
  records matching model_version, config sha256, and kernel sha256;
  refuses to resume across any mismatch. Stages 1 (enumeration/screening),
  2 (validation), 3 (optimized design), and 5 (stability) are
  checkpointable; stage 4 is always recomputed because fixed-system ground
  tracks are not serialized and downstream figures need them.
- New tests cover parser flags, the version string, a --version subprocess
  run, and the pure resume-guard helper.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant