Optional packaging for a real `loopprint` CLI (pipx / uvx / console_scripts)

[Rennlabs]

The tools run as python3 scripts/loopprint-<x>.py by design (skill, not a package). For users who want a PATH binary, add OPTIONAL packaging (a pyproject.toml with console_scripts, installable via pipx/uvx) WITHOUT changing the folder-skill identity. Must stay zero-runtime-dep for the core; PyYAML only where already required.

Acceptance: pipx install (or uvx loopprint ls) works; the folder-skill install path is unchanged.

[Rennlabs]

Partially shipped in 3ef5b6f: pyproject.toml + a thin looptimal_cli/ wrapper package expose [project.scripts] console entries for every scripts/*.py tool, verified end-to-end with real uv/uvx runs (both entry-point conventions), and confirmed the folder-skill install path is unchanged.

Left open on purpose: this issue's acceptance criterion implies a working pipx install / uvx loopprint ls — i.e. an actual PyPI-published package. Publishing to PyPI is identity-bound (Renn Labs' account) and semi-irreversible (package-name registration), so I didn't do it unilaterally. Today, uvx --from git+https://github.com/Renn-Labs/Looptimal@v2.0.0 <tool> works without one. Happy to walk through the actual PyPI publish (package name check, trusted-publishing setup) whenever you want to take that step — it needs your account, not just a code change.