Update README install & status for the live PyPI release

[abhiksark]

Part of the 0.3.0 adoption roadmap — Discovery.

Why (adoption impact)

python-learnings is live on PyPI (0.2.0), but the README still tells people PyPI "will become the primary install path after publishing is enabled" and points them at a GitHub @v0.1.0 install. New users following the README get the wrong, harder path — an active adoption blocker.

Current state

• Readme.md "Install" section (~lines 51–73): recommends pipx install "git+https://github.com/abhiksark/pylings.git@v0.1.0" and says PyPI is "after publishing is enabled".
• Readme.md intro status line (~line 21): Status: v0.1.0 alpha. GitHub installs are available now; the PyPI package name is python-learnings and will become the primary install path after publishing is enabled.

Scope / acceptance criteria

• Install section leads with PyPI: pip install python-learnings and pipx install python-learnings.
• Documents the zero-install run (uvx --from python-learnings pylings) and uv tool install python-learnings.
• Keeps the existing note that the command is pylings and the PyPI name is python-learnings (do NOT pip install pylings).
• Adds a one-line "needs Python 3.9+" with links to python.org per-OS.
• Updates the status line to v0.2.0 and removes all "after publishing" wording.
• Keeps the GitHub/dev-build install as a secondary "latest from main" note.

Where to look

• Readme.md — "Install", "Quick Start", and the intro status paragraph.

Out of scope

• Badge fixes (separate issue) and the no-arg launch change (separate issue).

Verify

• Copy each documented command into a clean shell / fresh venv on Python 3.9+ and confirm pylings --version prints 0.2.0.

Difficulty

good first issue · documentation — docs only, ~30 min.

[stevesagronegocios673-ux]

Quick README pass after checking the issue, current Readme.md, pyproject.toml, and the 0.3.0 roadmap: the issue is right that this should be a very small above-the-fold + install-section correction, not a broader README rewrite.

The three source-of-truth facts I would make the diff orbit around are:

pyproject.toml name: python-learnings
pyproject.toml version: 0.2.0
pyproject.toml requires-python: >=3.9

So I would update the top badges/status first:

[![Python 3.9+](...)](...)
[![PyPI](https://img.shields.io/pypi/v/python-learnings.svg)](https://pypi.org/project/python-learnings/)

Status: `v0.2.0` alpha. Install from PyPI as `python-learnings`; run it with the `pylings` command.

Then make the Install section order match first-time user intent:

## Install

Requires Python 3.9 or newer.

Recommended isolated install:

```bash
pipx install python-learnings
pylings --version

Regular pip install:

python -m pip install python-learnings
pylings --version

Zero-install run with uv:

uvx --from python-learnings pylings --version

Persistent uv tool install:

uv tool install python-learnings

I would keep the “do not `pip install pylings`” note immediately after those commands, because the package-name/command-name split is the one thing people will get wrong if it is buried.

For the GitHub install, I would make it explicitly secondary and unversioned:

```bash
pipx install --force "git+https://github.com/abhiksark/pylings.git"

One small acceptance-test tweak: verify python -m pip install python-learnings as well as pipx, because many beginners will not have pipx installed yet. The PR can still recommend pipx first, but the fallback command should be proven too.

If useful, I can turn this into a compact paste-ready README patch with the updated status line, install block, command-name warning, and verification checklist.