v0.11.0 — deprecate attune_help.{manifest,staleness,freshness}; add rag adapter

Highlights

Phase B2 of the architecture-realignment spec. Closes finding #1 (ADR-002 violation: authoring code in attune-help) of the 2026-05-07 deep code review.

Changed (deprecation)

• attune_help.manifest, attune_help.staleness, attune_help.freshness (and attune_help.freshness.symbols) are now thin re-export shims around their new homes in attune_author.*. Each shim emits DeprecationWarning on import. Update your imports:

  # before
  from attune_help.manifest import Feature, FeatureManifest
  
  # after
  from attune_author.manifest import Feature, FeatureManifest

  The shims are scheduled for removal in the next minor release of attune-help (target: 2026-07-07).

• The package no longer eagerly re-exports manifest/staleness symbols from its top-level. A plain import attune_help is warning-free during the deprecation window.

Added

• attune_help.adapters.rag.AttuneHelpAdapter — frozen dataclass implementing attune_rag.corpus.help_adapter.HelpCorpusAdapter. Lets attune-rag build the help corpus with no dynamic import of attune-help.

Dependencies

• New required: attune-author>=0.7.0. Transitional — required only while the deprecation shims live; removed together with the shims on 2026-07-07. (Tech.md's "zero required deps" constraint is paused for the deprecation window.)

Architecture-realignment progress

Phases A (attune-rag #10), B1 (attune-author #14, packaged in v0.7.0), and B2 (this release) done. Phase C next: orchestration scaffold in attune-author.

Diff stat

+300 / −1090 — three internal modules (~1063 lines) collapse to four ~30-line shims plus the rag adapter.