chore: bump to 0.3.6, migrate docs to openlegalstandard.org

CHANGES.md

@@ -1,3 +1,12 @@
+Version 0.3.6 (2026-04-08)
+---------------------------
+* Docs: Migrated user-facing documentation to https://openlegalstandard.org/resources/folio-python-library — comprehensive 9-page reference covering install, search, query, taxonomy, properties, serialization, LLM integration, and a complete API surface (alea-institute/folio-python#14)
+* Removed: `docs/` directory (Sphinx site that targeted the broken folio-python.readthedocs.io)
+* Removed: `.readthedocs.yaml` (RTD config no longer needed)
+* Removed: `.github/workflows/publish.yml` (Trusted Publisher workflow that was never configured on PyPI; releases are published locally via `uv build && uvx twine upload`)
+* Updated: README documentation link now points at openlegalstandard.org; logo path moved from `docs/_static/folio-logo.png` to `assets/folio-logo.png`
+* Updated: CONTRIBUTING.md notes that user-facing docs live in the openlegalstandard.org repo and should be updated alongside any public-API changes
+
 Version 0.3.5 (2026-04-08)
 ---------------------------
 * Added: `case_sensitive` parameter (default `False`) on `search_by_prefix()` — lowercase and mixed-case queries now match labels via a parallel lowercase MARISA trie using `str.casefold()` for Unicode-safe folding

CONTRIBUTING.md

@@ -54,6 +54,12 @@ To set up the project for development:
   - Test full build via docker (Ubuntu 24.04): `bash docker/build.sh`
   - Test clean install via docker (Ubuntu 22.04, Ubuntu 24.04): `bash docker/install.sh`
 
+## Documentation
+
+User-facing documentation lives in the [openlegalstandard.org](https://github.com/alea-institute/openlegalstandard.org) repository under [`src/pages/resources/folio-python-library/`](https://github.com/alea-institute/openlegalstandard.org/tree/main/src/pages/resources/folio-python-library), and is published at **[openlegalstandard.org/resources/folio-python-library](https://openlegalstandard.org/resources/folio-python-library)**.
+
+PRs that change public API (signatures, defaults, behavior) should also update the matching sub-page in that repo so the docs stay in sync. Every code snippet in the docs is validated against the published wheel via `uv run python`, so please run any new examples before submitting.
+
 ## Coding Style
 
 We generally follow the [PEP 8](https://pep8.org/) style guide for Python code, but the good news is that most style

README.md

@@ -1,6 +1,6 @@
 # FOLIO Python Library
 
-![FOLIO Logo](docs/_static/folio-logo.png)
+![FOLIO Logo](assets/folio-logo.png)
 
 [![PyPI version](https://badge.fury.io/py/folio-python.svg)](https://badge.fury.io/py/folio-python)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
@@ -181,7 +181,11 @@ Avoid `effort: "high"` — benchmarks show 5x latency with no quality improvemen
 
 ## Documentation
 
-For more detailed information about using the FOLIO Python library, please refer to our [full documentation](https://folio-python.readthedocs.io/).
+The full library reference lives on the FOLIO standards site:
+
+**[openlegalstandard.org/resources/folio-python-library](https://openlegalstandard.org/resources/folio-python-library)**
+
+It covers installation, initialization, fuzzy and prefix search, structured queries, taxonomy traversal, object properties and triples, serialization, LLM integration, and a complete API reference for `FOLIO`, `OWLClass`, `OWLObjectProperty`, and `FOLIOConfiguration`. Every code example is validated against the published wheel.
 
 ## Contributing