release: v7.1.2 — widen attune-rag pin to <0.3 (#465)

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

Widen the core pin AND the [dev] extra's test-coverage pin to
<0.3 so `pip install attune-ai` resolves attune-rag 0.2.x.

Local smoke (uv sync --extra dev in the .venv):
  - attune-ai 7.1.2, attune-rag 0.2.0 resolved cleanly
  - All four import paths used by attune-ai work:
      from attune_rag import RagPipeline
      from attune_rag.corpus.directory import DirectoryCorpus
      from attune_rag.pipeline import RagPipeline
      from attune_rag.provenance import format_citations_markdown
  - 137/137 attune_rag-importing tests pass (3 xfails are
    pre-existing structural ceilings, not regressions)

No code changes — RagPipeline / DirectoryCorpus /
format_citations_markdown surfaces consumed by
attune.workflows.rag_code_gen, attune.memory.personal, and
attune.mcp.workflow_handlers are unchanged across 0.1.x -> 0.2.0.

Companion comment block at the bottom of pyproject.toml updated
to match for accuracy.

uv.lock regenerated for the bump (lockfile drift was minimal:
attune-ai 7.1.1 -> 7.1.2, attune-rag 0.1.5 -> 0.2.0, plus two
existing transitive deps newly attributed to attune-rag).

Author: silversurfer562

CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [7.1.2] — 2026-05-25
+
+### Changed
+
+- **Widen `attune-rag` core pin: `>=0.1.5,<0.2` → `>=0.1.5,<0.3`
+  (and matching widen in the `[dev]` extra's test-coverage pin).**
+  Unblocks fresh `pip install attune-ai` alongside
+  [attune-rag 0.2.0](https://pypi.org/project/attune-rag/0.2.0/),
+  released 2026-05-25 as the first SemVer-binding cut. The 0.2.0
+  bump 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` / `format_citations_markdown`
+  surfaces consumed by `attune.workflows.rag_code_gen`,
+  `attune.memory.personal`, and `attune.mcp.workflow_handlers`
+  are unchanged across 0.1.x → 0.2.0, so this is a pin widen only
+  with no code changes. Cap raised one minor rather than
+  open-ended so the next breaking attune-rag bump still requires
+  explicit re-validation. Companion comment block at the bottom
+  of `pyproject.toml` updated to match.
+
 ## [7.1.1] — 2026-05-25
 
 ### Added

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "attune-ai"
-version = "7.1.1"
+version = "7.1.2"
 description = "AI-powered developer workflows for Claude with cost optimization, multi-agent orchestration, and workflow automation."
 readme = {file = "README.md", content-type = "text/markdown"}
 requires-python = ">=3.10"
@@ -73,7 +73,7 @@ dependencies = [
     "langsmith>=0.7.31,<2.0.0",  # GHSA-rr7j-v2q5-chgv (transitive via langchain-core)
     "jinja2>=3.1.0,<4.0.0",  # Meta template rendering for help system
     "python-frontmatter>=1.0.0,<2.0.0",  # YAML frontmatter parsing for help templates — required by attune.help.engine which backs the help_lookup MCP tool (progressive/workflow_help/precursor/search_tag modes all parse template files). Vanilla pip install attune-ai without this breaks every help_lookup mode except `preamble`.
-    "attune-rag>=0.1.5,<0.2",  # RAG grounding for rag-code-gen workflow + rag_knowledge_query MCP tool. Core dep (not optional) — required for acceptable retrieval accuracy.
+    "attune-rag>=0.1.5,<0.3",  # RAG grounding for rag-code-gen workflow + rag_knowledge_query MCP tool. Core dep (not optional) — required for acceptable retrieval accuracy. Cap raised to <0.3 in 7.1.2 to admit attune-rag 0.2.0 (purely additive SemVer-binding cut, no breaking API changes); next breaking minor still requires explicit re-validation.
     "tomli>=2.0.0; python_version < '3.11'",  # tomllib fallback for Python 3.10. Used by attune.utils.coverage (loaded transitively from release-prep + orchestrated-health-check workflows). Without this, those workflows fail to load on 3.10.
     # NOTE: attune-author is a workspace-only dev dep for authoring/
     # refactoring help content — NOT a runtime requirement.
@@ -233,7 +233,7 @@ dev = [
     # branches (rag tests use pytest.importorskip). Floor
     # matches the [rag] extra so dev + runtime deps stay in
     # lock-step.
-    "attune-rag>=0.1.5,<0.2",
+    "attune-rag>=0.1.5,<0.3",
     # Test deps for paths that import optional runtime libs
     # unconditionally. Without these, the unit suite fails at
     # collection on a fresh `pip install -e .[dev]`. See
@@ -758,9 +758,9 @@ exclude_lines = [
 ]
 
 # Sibling repos — all published to PyPI:
-#   attune-rag     — core dep (>=0.1.5,<0.2) — promoted from optional; required for accuracy
+#   attune-rag     — core dep (>=0.1.5,<0.3) — promoted from optional; required for accuracy
 #   attune-author  — [author] optional extra (>=0.4.1,<0.5)
-#   attune-rag     — [rag] optional extra (>=0.1.5,<0.2)
+#   attune-rag     — [rag] optional extra (>=0.1.5,<0.3) — no-op alias since rag is core
 #
 # No [tool.uv.sources] overrides needed: CI resolves all three
 # from PyPI (https://pypi.org/simple). For local iteration against