No functional change. This release exists because PyPI metadata is immutable per version: the packaging fields added in 6b9dec5 could not reach anyone without a version carrying them.
What was missing
The PyPI page declared no classifiers at all, so the package appeared in none of PyPI's faceted searches — License, Topic and Intended Audience are driven by classifiers, not by the license field. There was also no route from the package page to the issue tracker: project.urls carried only Homepage and Repository.
Changes
- classifiers — 10 entries. Python versions list what CI exercises (3.10, 3.12) plus 3.11 between them;
requires-pythonstill admits any 3.10+ interpreter. - project.urls — added
Issues,Changelog(→ Releases; this repository keeps no CHANGELOG.md) andDocumentation. - Issue templates — bug report and feature request as issue forms. The bug form asks for
EMBEDDING_PROVIDERand the affected surface, the two facts that decide where to look first. Vulnerabilities are routed to GitHub Security Advisories, whose private reporting was enabled in the same pass. - README — links both templates, and the two
LICENSElinks are now absolute. The README renders on the PyPI page, where relative links resolve against pypi.org and 404.
Compatibility
Metadata and documentation only. No code, no dependency, no schema change. cloto-connector.json deliberately stays at 0.6.2 — nothing here affects the hub-mediated path, and bumping it would require regenerating the magic seal for no user-visible gain.
Verification
Test suite green (54 passed) before the bump, per the verify-then-bump discipline. Metadata confirmed live on PyPI after publish: 10 classifiers and all five project URLs present, description_content_type: text/markdown.
Full changelog: v0.6.2...v0.6.3