Pin spec v0.64.0 for proposal 0073 (textual-only) (#173)

* Pin spec v0.64.0 for proposal 0073 (textual-only)

0073 (GenAI semconv adoption reconciliation) is a spec governance +
observability §5.5 rationale change with no emitted-attribute and no
conformance-expectation change: OA retains gen_ai.system despite the
upstream rename to gen_ai.provider.name, and the existing gen_ai.*
fixtures stand as the retention regression.

Textual-only pin bump v0.63.1 -> v0.64.0: __spec_version__, pyproject,
smoke, regenerated AGENTS.md, conformance.toml 0073 textual-only, and
the 0.15.0 changelog pin bullet. No code, no new fixtures.

* Fix stale conformance.toml spec_pin; guard it

PR #173 review: conformance.toml [manifest].spec_pin was stale at
v0.60.0 -- a fourth pin-sync point the smoke test did not cover, so it
drifted across the v0.15.0 pin bumps. Update it to v0.64.0 and add a
smoke-test assertion that spec_pin tracks __spec_version__ so it cannot
drift again.

Author: chris-colinsky

CHANGELOG.md

@@ -15,7 +15,7 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). The
 
 ### Changed
 
-- **Pinned spec advances v0.60.0 → v0.63.1** across the v0.15.0 cycle: v0.61.0 (proposal 0061, the detached-trace invocation span above), v0.62.0 (proposal 0064, the Langfuse session/user population above), v0.63.0 (proposal 0072, the prompt cache control above), and the v0.63.1 patch (pipeline-utilities coverage fixtures 070/071 for the already-implemented 0069 / 0070 behavior, no new proposal). `conformance.toml` records 0061 / 0072 `implemented` and 0064 `partial` (its `sessionId` half is dormant pending the sessions capability). Proposal 0050 needed no pin bump of its own (it was already within the pin from its v0.42.0 acceptance); its v0.14.0 `partial` entry flips to `implemented` with the per-attempt span surface above.
+- **Pinned spec advances v0.60.0 → v0.64.0** across the v0.15.0 cycle: v0.61.0 (proposal 0061, the detached-trace invocation span above), v0.62.0 (proposal 0064, the Langfuse session/user population above), v0.63.0 (proposal 0072, the prompt cache control above), the v0.63.1 patch (pipeline-utilities coverage fixtures 070/071 for the already-implemented 0069 / 0070 behavior, no new proposal), and v0.64.0 (proposal 0073, GenAI semconv adoption reconciliation: OA retains `gen_ai.system` despite the upstream rename to `gen_ai.provider.name`; textual-only, with no emitted-attribute or fixture change, so the existing `gen_ai.*` fixtures stand as the retention regression). `conformance.toml` records 0061 / 0072 `implemented`, 0064 `partial` (its `sessionId` half is dormant pending the sessions capability), and 0073 `textual-only`. Proposal 0050 needed no pin bump of its own (it was already within the pin from its v0.42.0 acceptance); its v0.14.0 `partial` entry flips to `implemented` with the per-attempt span surface above.
 
 ## [0.14.0] — 2026-06-17
 

conformance.toml

@@ -32,7 +32,7 @@
 
 [manifest]
 implementation = "openarmature-python"
-spec_pin = "v0.60.0"
+spec_pin = "v0.64.0"
 
 # Status values:
 #   implemented   — shipped behavior matches the proposal's contract
@@ -712,3 +712,10 @@ note = "The Langfuse observer promotes a recognized userId caller-metadata key t
 status = "implemented"
 since = "0.15.0"
 note = "PromptBackend.fetch / PromptManager.fetch / get gain an optional cache_ttl_seconds read-side control (absent / None = current behavior; 0 = force a fresh read past any cache; N > 0 = bound a served entry's staleness to N seconds; negative is rejected). It governs only which cached entry MAY be served for this fetch, not whether / how the result is cached. python's bundled backends (filesystem, in-memory) are cacheless and treat it as a no-op; the manager threads it through the §9 fallback chain and rejects negatives. render is unchanged. The TTL semantics are exercised by a caching prompt-backend conformance-harness primitive (§6.8: caches by (name, label), source_read_count, advance_clock controllable clock); fixtures 033/034 pass. No production caching backend ships (per §5, cacheless backends no-op). The v0.63.1 pin also wires pipeline-utilities coverage fixtures 070/071 (already-implemented 0069/0070 behavior; no new proposal)."
+
+# Spec v0.64.0 (proposal 0073).  GenAI semconv adoption reconciliation
+# (GOVERNANCE External-dependency adoption + observability §5.5 rationale).
+[proposals."0073"]
+status = "textual-only"
+since = "0.15.0"
+note = "Governance + observability §5.5 rationale change: reconciles the gen_ai.* adoption with upstream reality (the whole GenAI semconv surface is at Development status, and gen_ai.system was removed upstream in favor of gen_ai.provider.name). Adds a GenAI-scoped de-facto-interoperability carve-out (OA adopts the recognized core gen_ai.* names directly even at Development; peripheral attributes are mirrored to openarmature.*) and a post-adoption RETENTION rule (an adopted name is kept through an upstream rename / removal). No emitted-attribute change and no conformance-expectation change: python already emits the recognized core gen_ai.* set (including gen_ai.system, now RETAINED despite the upstream rename), so the existing gen_ai.* observability fixtures (e.g. 019-021) stand as the retention regression coverage. No python code and no new fixtures. The gen_ai.system -> gen_ai.provider.name migration is a deferred follow-on."

openarmature-spec

@@ -63,7 +63,7 @@ Specification = "https://github.com/LunarCommand/openarmature-spec"
 openarmature = "openarmature.cli:main"
 
 [tool.openarmature]
-spec_version = "0.63.1"
+spec_version = "0.64.0"
 
 [dependency-groups]
 dev = [

pyproject.toml

@@ -1,6 +1,6 @@
 # OpenArmature — Agent documentation
 
-*This is the agent guide bundled with the openarmature Python package, version 0.14.0 (spec v0.63.1). For the full docs site see [openarmature.ai](https://openarmature.ai). For the canonical spec text see [openarmature.org/capabilities](https://openarmature.org/capabilities/). For project-specific conventions for the code you're editing, see the host project's `AGENTS.md` or `CLAUDE.md`.*
+*This is the agent guide bundled with the openarmature Python package, version 0.14.0 (spec v0.64.0). For the full docs site see [openarmature.ai](https://openarmature.ai). For the canonical spec text see [openarmature.org/capabilities](https://openarmature.org/capabilities/). For project-specific conventions for the code you're editing, see the host project's `AGENTS.md` or `CLAUDE.md`.*
 
 ## TL;DR
 
@@ -10,7 +10,7 @@ OpenArmature is a workflow framework for LLM pipelines and tool-calling agents:
 
 ## Capability contracts
 
-_Sourced from openarmature-spec v0.63.1. Each entry below reproduces §1 (Purpose) and §2 (Concepts) of the capability's `spec.md` verbatim — including additions from accepted proposals that this Python implementation may not yet ship. For per-proposal implementation status (implemented / partial / textual-only / not-yet), see the `conformance.toml` manifest at the repo root. For the full spec text (execution model, error semantics, determinism, observer hooks, etc.) see the linked docs site._
+_Sourced from openarmature-spec v0.64.0. Each entry below reproduces §1 (Purpose) and §2 (Concepts) of the capability's `spec.md` verbatim — including additions from accepted proposals that this Python implementation may not yet ship. For per-proposal implementation status (implemented / partial / textual-only / not-yet), see the `conformance.toml` manifest at the repo root. For the full spec text (execution model, error semantics, determinism, observer hooks, etc.) see the linked docs site._
 
 ### Capability: `graph-engine`
 

src/openarmature/AGENTS.md

@@ -25,7 +25,7 @@
 """
 
 __version__ = "0.14.0"
-__spec_version__ = "0.63.1"
+__spec_version__ = "0.64.0"
 # Proposal 0052 (spec observability §5.1 / §8.4.1): canonical
 # package-registry name for this implementation. Surfaces on every
 # OTel invocation span as ``openarmature.implementation.name`` and on

src/openarmature/__init__.py

@@ -9,7 +9,7 @@
 
 def test_package_versions() -> None:
     assert openarmature.__version__ == "0.14.0"
-    assert openarmature.__spec_version__ == "0.63.1"
+    assert openarmature.__spec_version__ == "0.64.0"
 
 
 def test_spec_version_matches_pyproject() -> None:
@@ -24,6 +24,20 @@ def test_spec_version_matches_pyproject() -> None:
     assert openarmature.__spec_version__ == pyproject_spec_version
 
 
+def test_conformance_spec_pin_matches_spec_version() -> None:
+    # conformance.toml's [manifest].spec_pin is a fourth pin-sync point
+    # (alongside __spec_version__, pyproject, and the submodule changelog)
+    # that no other check covered, so it silently drifted across the
+    # v0.15.0 pin bumps. Assert it tracks __spec_version__ (the manifest
+    # value carries a ``v`` prefix) so it can't drift again.
+    conformance_path = Path(__file__).resolve().parent.parent / "conformance.toml"
+    manifest = tomllib.loads(conformance_path.read_text())
+    spec_pin = manifest["manifest"]["spec_pin"]
+    assert spec_pin == f"v{openarmature.__spec_version__}", (
+        f"conformance.toml [manifest].spec_pin is {spec_pin!r}, expected v{openarmature.__spec_version__}"
+    )
+
+
 # Keep a Changelog heading: ``## [0.15.0]`` (with optional trailing
 # date). The ``[Unreleased]`` entry uses a non-numeric tag and is
 # skipped by this pattern.