chore: widen attune-rag pin to <0.3 and release v0.14.1 (#43)

attune-rag 0.2.0 shipped 2026-05-25 as the first SemVer-binding
cut — purely additive (new measure_corpus module + aliases
helpers; no breaking API changes). The current [rag] extra
pin caps at <0.2, silently locking installs to attune-rag
0.1.23 even when 0.2.x is available.

Widen the cap to <0.3 so `pip install attune-author[rag]`
resolves attune-rag 0.2.x while still requiring explicit
re-validation for the next breaking minor.

Local smoke (python 3.10, fresh venv):
  pip install -e .[rag]
  → attune-author 0.14.1, attune-rag 0.2.0
  53/53 rag- and faithfulness-marked tests pass.

No code changes — RagPipeline / DirectoryCorpus /
FaithfulnessConfig surfaces consumed by rag_hook.py and
faithfulness/ are unchanged across the 0.1.x → 0.2.0 bump.

Author: silversurfer562

CHANGELOG.md

@@ -13,6 +13,24 @@ and this project adheres to
 Work in progress for the next release. Add entries here as
 changes land, not at tag time.
 
+## [0.14.1] - 2026-05-25
+
+### Changed
+
+- **Widen `attune-rag` pin in the `[rag]` extra: `>=0.1.0,<0.2`
+  → `>=0.1.0,<0.3`.** Unblocks installs of `attune-author[rag]`
+  alongside the freshly-released
+  [attune-rag 0.2.0](https://pypi.org/project/attune-rag/0.2.0/),
+  which is the first SemVer-binding cut. The 0.2.0 release is
+  purely additive (new `attune_rag.measure_corpus` public module,
+  new `load_aliases_from_file` helper, new
+  `DirectoryCorpus(extra_aliases_file=...)` kwarg); the
+  `RagPipeline` / `DirectoryCorpus` / `FaithfulnessJudge` APIs
+  consumed by `attune_author.rag_hook` and `attune_author.faithfulness`
+  are unchanged, so no code adaptation needed. Cap raised one
+  minor (`<0.3`) rather than open-ended so the next breaking
+  attune-rag bump still requires explicit re-validation.
+
 ## [0.14.0] - 2026-05-22
 
 ### Added

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "attune-author"
-version = "0.14.0"
+version = "0.14.1"
 description = "Documentation authoring and maintenance for the attune ecosystem — generate, maintain, and validate help content with AI assistance."
 readme = {file = "README.md", content-type = "text/markdown"}
 requires-python = ">=3.10"
@@ -51,7 +51,7 @@ ai = ["anthropic>=0.40.0"]
 # opt-out via --no-rag or ATTUNE_AUTHOR_RAG=0). Optional
 # so authors who don't want the dep avoid it. Lazy-imported
 # inside attune_author.rag_hook; core import is unaffected.
-rag = ["attune-rag>=0.1.0,<0.2"]
+rag = ["attune-rag>=0.1.0,<0.3"]
 plugin = [
     "mcp>=0.9.0",
     "anthropic>=0.40.0",

src/attune_author/__init__.py

@@ -5,7 +5,7 @@
 attune-help (reader) and attune-ai (full dev workflows).
 """
 
-__version__ = "0.14.0"
+__version__ = "0.14.1"
 
 from attune_author.manifest import Feature, Manifest, load_manifest
 from attune_author.staleness import (