`websockets` is used by `ria_toolkit_oss.agent.ws_client`, which is
imported as part of `ria-agent stream`. It was only declared in the
optional `[tool.poetry.group.agent]` poetry group, so a vanilla
`pip install ria-toolkit-oss` left `ria-agent stream` failing with
`ModuleNotFoundError: No module named 'websockets'`.
Moved into PEP 621 `[project].dependencies` with the same constraint
(`>=12.0,<14.0`). The duplicate in the optional poetry group is left
in place so `poetry install --with agent` remains self-sufficient.
poetry.lock: `websockets` now joins the `main` dependency group; the
generator-header bump (2.1.4 → 2.3.4) and the `jsonschema-specifications`
version-string normalization are auto-regenerated noise from the
locally-installed poetry version.
Note: `requests` has the same packaging gap (used by the legacy agent
path, declared only in the optional `agent` group); leaving that for a
follow-up since the immediate complaint is websockets.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Most users register against the production hub, so requiring --hub on
every invocation was friction. Default the flag to https://riahub.ai
via a module-level DEFAULT_HUB_URL constant; explicit --hub still wins,
so dev and self-hosted setups (e.g. http://whitehorse:3005) keep working.
The legacy `ria-agent run` path keeps its own --hub handling unchanged
— it has a config-file fallback and existing operators rely on it.
Bumps version to 0.1.8.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Covers the User-Agent / Cloudflare fix, request timeout, structured
error reasons, human-readable default agent names, and updated CLI
help text for the per-user `ria_reg_*` registration key flow.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
