Bump spec conformance pin to v0.107.0 (#259)

* Bump spec conformance pin to v0.107.0

Advance the openarmature-spec submodule pin from v0.88.0 to v0.107.0,
absorbing proposals 0094-0113 into the v0.17.0 release. This is a
mechanical bump: the four sync points (pyproject spec_version, package
__spec_version__, conformance.toml spec_pin, the submodule CHANGELOG)
plus the test_smoke assertion move together, and AGENTS.md regenerates.
No src behavior changes.

Moving the pin surfaces the band's conformance fixtures, whose behavior
shipped and is unit-tested ahead of the pin but whose harness wiring is
not yet in place. All 67 are deferred with categorized reasons, keeping
the suite green; the fixture wiring lands in a follow-up PR before the
release tag.

Manifest notes: 0096, 0097, and 0100 are since 0.16.0 (shipped with the
v0.16.0 retrieval work); 0098, 0102, and 0107 are textual-only
(conformance-adapter directives with no shipped-module component); 0113
is partial (the general merge-arm malformed handling is not yet built).

* Clarify retrieval fixture-deferral comments

Two review-driven comment refinements in test_retrieval_provider.py, no
behavior change:

- Reconcile the header comment above _DEFERRED_FIXTURES: it claimed no
  retrieval fixtures remain deferred, which the v0.107.0 bump contradicts
  by re-deferring 042 / 043 / 052.
- Refine 042's deferral reason to name the actual gap. The chunk-stitch
  behavior shipped in v0.16.0 (first-chunk-only response_id nulling, all-
  or-nothing usage); 042 fails only on the contains_event matcher, which
  compares a record-valued field (usage) against a dict expectation.

From review of PR #259.

Author: chris-colinsky

conformance.toml

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

openarmature-spec

@@ -1,6 +1,6 @@
 # OpenArmature — Agent documentation
 
-*This is the agent guide bundled with the openarmature Python package, version 0.16.0 (spec v0.88.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`.*
+*This is the agent guide bundled with the openarmature Python package, version 0.16.0 (spec v0.107.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.88.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._
+_Sourced from openarmature-spec v0.107.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`
 
@@ -168,13 +168,72 @@ the defaults themselves: projection-in is off by default (so `inputs` turns it o
 projection-out is on by default via field-name matching (so `outputs` replaces it to avoid ambiguous mixed
 rules).
 
+**Declared same-name projection boundary.** As a checked alternative between the implicit
+field-name-matching default and the explicit rename maps, a subgraph-as-node MAY declare its boundary as two
+field-name *sets* — an **in-set** and an **out-set** — naming the fields that cross by the *same name* on
+both sides. The *per-entry* semantics of each set match the explicit maps restricted to same-name pairs: an in-set entry
+behaves as an `inputs` entry whose subgraph and parent field names coincide (the parent field's value is
+copied into the same-named subgraph field at entry); an out-set entry behaves as an `outputs` entry whose
+parent and subgraph field names coincide (the subgraph field's final value is merged into the same-named
+parent field via the parent's reducer at exit).
+
+Unlike the maps, the declared form is a **complete boundary declaration with no field-name-matching
+fallback** — using it states exactly what crosses:
+
+- The in-set fully determines projection-in: subgraph fields not named receive their schema-declared
+  defaults; an empty in-set projects nothing in (identical to the no-projection-in default).
+- The out-set fully determines projection-out, replacing field-name matching: subgraph fields not named are
+  discarded; an empty out-set projects nothing out. There is no "absent out-set falls back to field-name
+  matching" state — a subgraph-as-node that wants field-name matching uses the default (declares no
+  boundary). An empty set means "nothing," symmetrically for both directions.
+
+Using the declared form governs **both** directions: declaring either set opts the node into the declared
+form, and a set that is *omitted entirely* is treated as empty — nothing crosses in that direction, with no
+fall-back to field-name matching or to the maps' defaults. Declaring `projects_in` alone, for example,
+projects the named fields in and projects **nothing** out (to keep field-name matching on the way out, use
+the default form). This is what distinguishes the declared form from the explicit maps, whose `inputs`-only
+case *does* leave projection-out at the field-name-matching default (below).
+
+The declared same-name sets and the explicit `inputs`/`outputs` maps are **mutually exclusive** on a single
+subgraph-as-node: a node declares its projection with at most one of the default (nothing declared), the
+declared same-name sets, or the explicit maps.
+
 Compilation MUST fail with category `mapping_references_undeclared_field` if an `inputs` mapping names a
 parent field that is not declared in the parent's state schema, or a subgraph field that is not declared in
 the subgraph's state schema. The same rule applies symmetrically to `outputs`. Implementations SHOULD
 validate at compile time that the types of mapped parent/subgraph field pairs are compatible (per the
 language's type system's notion of compatibility); this is SHOULD rather than MUST because type-system
 expressiveness varies across languages.
 
+The same `mapping_references_undeclared_field` rule applies to the declared same-name sets: compilation MUST
+fail if an in-set or out-set names a field not declared on the relevant schema (a same-name field is checked
+on both the parent and the subgraph schema). Declaring both the same-name sets and an explicit
+`inputs`/`outputs` mapping on one subgraph-as-node MUST fail compilation with category
+`conflicting_projection_forms`.
+
+**Reducer round-trip warning.** Because projection-out merges through the parent's reducer, a field projected
+*in* and then *back out* into the same parent field re-merges: for a reducer that is not
+*round-trip-idempotent* — one for which re-applying an already-merged value changes the field — the unchanged
+value is merged a second time (e.g. an `append` reducer doubles the list). Of the canonical reducers above,
+`last_write_wins`, `merge`, `merge_by_key`, and `dedupe_append` are round-trip-idempotent (a replace, or a
+keyed / deduplicated / shallow merge re-applied with the same value, is a no-op); `append`, `concat_flatten`,
+`bounded_append`, and `merge_all` are not — `append` / `concat_flatten` / `bounded_append` grow the field on
+re-application, and `merge_all` requires a *list-of-mappings* update (see its definition above), so re-merging
+a single mapping value is ill-typed and raises `reducer_error` rather than a no-op. A projection
+**round-trips** a field when the same parent field is copied into the subgraph and a subgraph field carrying
+it is merged back into that same parent field. This occurs when: (a) in the declared same-name form, a field
+is named in **both** the in-set and the out-set; (b) in the explicit maps, a parent field is both an `inputs`
+value and an `outputs` key mapped to the **same** subgraph field; or (c) with `outputs` absent (projection-out
+left at the field-name-matching default), an `inputs` entry copies a parent field into a **same-named**
+subgraph field, so field-name matching merges it straight back out. Implementations **MUST** emit a compile-time warning
+`projection_reducer_round_trip` (a warning, distinct from the MUST-fail compile-error categories below) when a
+projection round-trips a field into a non-round-trip-idempotent **canonical** reducer, and **SHOULD** emit it
+when the target is a custom reducer the implementation classifies as non-idempotent. The warning is a
+structural heuristic — an implementation cannot statically prove the subgraph left the value unchanged, so it
+MAY fire on a round-trip that legitimately replaces the value — and it changes no runtime behavior
+(projection-out still merges through the parent's reducer). Authors SHOULD route a round-tripped field through
+a replace/idempotent reducer or avoid round-tripping it.
+
 **Compiled graph.** The result of compiling a graph definition. A compiled graph is immutable and executable.
 The entry node MUST be declared explicitly by the graph author — there is no implicit "first node added"
 default. Compilation MUST fail with a diagnostic error if the graph has: no declared entry node, unreachable
@@ -189,8 +248,10 @@ identifiers (as an error class, error code, or tagged discriminant, per the lang
 - `dangling_edge` — an edge references a node name that is not declared.
 - `multiple_outgoing_edges` — a node has more than one outgoing edge.
 - `conflicting_reducers` — a state field has more than one declared reducer.
-- `mapping_references_undeclared_field` — a subgraph-as-node `inputs` or `outputs` mapping names a field
-  not declared in the relevant state schema.
+- `mapping_references_undeclared_field` — a subgraph-as-node `inputs` or `outputs` mapping, or a declared
+  same-name in-set / out-set, names a field not declared in the relevant state schema.
+- `conflicting_projection_forms` — a subgraph-as-node declares both the same-name projection sets and an
+  explicit `inputs`/`outputs` mapping (the two are mutually exclusive).
 - `reducer_configuration_invalid` — a reducer factory was supplied invalid construction parameters
   (e.g., `bounded_append(max_len=0)`, `merge_by_key(key=None)`). Raised at field registration / graph
   compilation time, before any node body runs. Distinct from `conflicting_reducers`, which is about
@@ -496,8 +557,8 @@ The substrate is intentionally narrow, matching llm-provider's posture:
 
 **Transparency.** Per charter §3.1 principle 8 ("Transparency over abstraction"), the embedding
 abstraction surfaces a normalized shape — `EmbeddingResponse`, `EmbeddingUsage` — without hiding
-what the underlying provider returned. The `EmbeddingResponse.raw` field carries the parsed provider
-response verbatim alongside the normalized fields, and the error categories preserve the underlying
+what the underlying provider returned. The `EmbeddingResponse.raw` field carries the provider
+response verbatim — an object or an array (§4) — alongside the normalized fields, and the error categories preserve the underlying
 provider exception as cause.
 
 #### 2. Concepts
@@ -511,7 +572,7 @@ vectors wrapped in an `EmbeddingResponse`. Bound to a specific embedding model i
 instance.
 
 **EmbeddingResponse.** The result of an `embed()` call: the vectors, the model identifier, the
-parsed raw response, and — when present — usage information and the provider-returned request
+verbatim provider response (`raw`), and — when present — usage information and the provider-returned request
 identifier.
 
 **EmbeddingUsage.** A usage record carrying `input_tokens` only — embedding has no output tokens
@@ -534,7 +595,7 @@ the documents sorted by query-relevance with provider-specific scores. Bound to
 model identifier per instance.
 
 **RerankResponse.** The result of a `rerank()` call: the sorted scored documents, the model
-identifier, the parsed raw response, and — when present — usage information and the
+identifier, the verbatim provider response (`raw`), and — when present — usage information and the
 provider-returned response identifier.
 
 **RerankUsage.** A usage record with optional `search_units` and optional `input_tokens`, reflecting

pyproject.toml

@@ -25,7 +25,7 @@
 """
 
 __version__ = "0.16.0"
-__spec_version__ = "0.88.0"
+__spec_version__ = "0.107.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/AGENTS.md

@@ -85,6 +85,21 @@ def _fixture_id(path: Path) -> str:
         "Proposal 0023 canonical state reducers; impl not yet shipped"
     ),
     "038-reducer-error-non-list-update": ("Proposal 0023 canonical state reducers; impl not yet shipped"),
+    # Proposal 0094 (spec v0.89.0) declared same-name subgraph projection
+    # boundary + reducer round-trip compile warning. Behavior shipped +
+    # unit-tested ahead of the pin (test_projection_declared_boundary.py);
+    # the runtime adapter (declared-boundary subgraph construction) + the
+    # GraphFixture directive model ride the v0.17.0 fixture-wiring PR.
+    "040-subgraph-declared-same-name-boundary": (
+        "Proposal 0094 declared-boundary adapter; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "041-declared-boundary-compile-errors": (
+        "Proposal 0094 declared-boundary compile-error adapter; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "042-reducer-round-trip-warning": (
+        "Proposal 0094 round-trip warning adapter (expected_compile_warning); "
+        "rides the v0.17.0 fixture-wiring PR"
+    ),
 }
 
 

src/openarmature/__init__.py

@@ -626,6 +626,82 @@ def _id(case: tuple[str, Path]) -> str:
         "directive shapes the cross-cap parser does not model, "
         "runtime-driven in test_observability"
     ),
+    # ----- v0.17.0 spec-pin bump (v0.88.0 -> v0.107.0) ------------------
+    # These fixtures use directive shapes the cross-capability parser does
+    # not yet model. Behavior for each proposal shipped + is unit-tested
+    # ahead of the pin; the fixture-model wiring rides the v0.17.0
+    # fixture-wiring PR (041 parses cleanly -- only its runtime adapter is
+    # deferred, in test_conformance).
+    # Proposal 0094 (v0.89.0) declared-boundary + round-trip warning.
+    "graph-engine/040-subgraph-declared-same-name-boundary": (
+        "Proposal 0094 declared-boundary GraphFixture model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "graph-engine/042-reducer-round-trip-warning": (
+        "Proposal 0094 round-trip warning fixture model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    # Proposal 0095 (v0.91.0) adaptive call-level retry + reask.
+    "llm-provider/061-call-level-retry-per-attempt-override": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/062-call-level-reask-success": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/063-call-level-reask-budget-exhausted": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/064-call-level-reask-off-by-default": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/065-call-level-reask-compose-override": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/066-call-level-reask-transient-interleave": (
+        "Proposal 0095 call.retry / wire_requests directive model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    # Proposal 0101 (v0.96.0) malformed usage counter.
+    "llm-provider/070-usage-counter-derived-total-unreported-addend": (
+        "Proposal 0101 usage-counter fixture model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/071-usage-counter-malformed-streaming-terminal-chunk": (
+        "Proposal 0101 usage-counter fixture model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    # Proposals 0105 (v0.100.0) / 0108 (v0.103.0) managed-field collision;
+    # the fixtures carry per-case `invariants` flags the parser does not model.
+    "llm-provider/072-managed-response-format-collision": (
+        "Proposal 0105 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/073-managed-stream-options-collision": (
+        "Proposal 0105 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/074-managed-structural-model-collision": (
+        "Proposal 0105 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/075-managed-declared-scalar-collision": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/076-managed-declared-stop-merge": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/077-managed-declared-stream-collision": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/078-managed-anthropic-stream-reject": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/079-managed-anthropic-stop-merge": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    "llm-provider/080-managed-gemini-stop-merge": (
+        "Proposal 0108 managed-collision invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    # Proposal 0113 (v0.107.0) malformed extras on a merge-managed field.
+    "llm-provider/081-managed-declared-stop-malformed": (
+        "Proposal 0113 malformed merge-managed extras invariants model; rides the v0.17.0 fixture-wiring PR"
+    ),
+    # Proposal 0109 (v0.104.0) token-budget config extra-key handling.
+    "prompt-management/037-token-budget-unrecognized-key-ignored": (
+        "Proposal 0109 token_budget extra-key fixture model; rides the v0.17.0 fixture-wiring PR"
+    ),
 }