Update README, version, changelog, dependency bounds, and limitations for launch

[bordeauxred]

Why

The repo metadata and README should match the experience we want first-time users to have.

What

• Lead with pip install clawloop and the no-key demo command once the installed demo exists.
• Add clear source-available BSL 1.1 framing near the top of the README.
• Make the Additional Use Grant threshold consistent with the license text.
• Make limitations visible: harness/playbook learning is the stable path; router/weights/full-mode have more constraints.
• Bump package version for the public release if publishing to PyPI.
• Add a matching CHANGELOG.md entry.
• Tighten litellm dependency bounds to avoid accidental breakage from a future major release.
• Review PyPI classifiers for accuracy.

Acceptance

• README first screen contains install, demo, license, and limitations.
• pyproject.toml version and dependency bounds match the release plan.
• CHANGELOG.md has the public release entry.

[bordeauxred]

Codex review (2026-04-19) — additions:

1. Update all version sources, not only `pyproject.toml`. Verify and bump:

   • `pyproject.toml` `[project] version`
   • `clawloop/init.py` `version`
   • `CITATION.cff` (when added)
   • GitHub release tag
   • CHANGELOG heading
     A version mismatch on release day is very visible.

2. `tool.uv.constraint-dependencies` does NOT protect plain `pip install` users. The current `litellm!=1.82.7,!=1.82.8` exclusion only applies when uv resolves the env. To protect PyPI users, encode the exclusions in `[project] dependencies` itself, e.g.:
   ```toml
   "litellm>=1.0,<2.0,!=1.82.7,!=1.82.8"
   ```

3. Classifier review: `License :: Other/Proprietary License` is technically valid for BSL but reads coldly. PyPI doesn't have a "source-available" classifier; cleanest move is to keep Other/Proprietary and let the README do the explaining. Do not use any OSI classifier.