conformance.toml

# Conformance manifest for openarmature-python.
#
# Records which openarmature-spec proposals are implemented in this
# package, and starting at which release version. Intended to be read
# by external consumers (notably the openarmature-spec docs build,
# which surfaces a per-implementation status column on the proposals
# index page).
#
# Stable URL (read-only, fetched at docs-build time):
#   https://raw.githubusercontent.com/LunarCommand/openarmature-python/main/conformance.toml
#
# Maintenance: keep in sync with CHANGELOG.md. The CI guard at
# scripts/check_conformance_manifest.py validates this file against the
# pinned spec submodule's proposals/ directory on every PR and release
# build; any Accepted proposal lacking an entry (or any entry pointing
# at a non-existent / non-Accepted proposal) fails the build.
#
# Scope: this file lists ONLY proposals visible in the pinned spec
# submodule (openarmature-spec at the SHA pinned by this repo's
# submodule). Proposals accepted on the spec's main branch after this
# repo's last spec bump are intentionally absent — surfacing the gap
# between pinned-spec and spec-head is the consumer's job (e.g., the
# spec docs site computes the difference and renders accordingly).
#
# Convention: this file is updated as part of release PRs AND as part
# of feature PRs that bump the spec submodule pin (the manifest guard
# requires entries for every Accepted proposal in the pinned spec, so
# a submodule bump forces this file to update too). Such bump PRs set
# `since` to the upcoming release version; between the bump PR and the
# matching tag, external readers will see a `since` referring to the
# upcoming, unreleased version.

[manifest]
implementation = "openarmature-python"
spec_pin = "v0.56.0"

# Status values:
#   implemented   — shipped behavior matches the proposal's contract
#   partial       — partial impl; consult `note` for what's missing
#   textual-only  — accepted proposal is purely textual (reframe,
#                   clarification, template) with no module-level
#                   change required; CHANGELOG note explains why
#   not-yet       — accepted in spec, not yet shipped in this package
#
# Drafts and Superseded proposals are deliberately absent from this
# file. The CI guard requires entries only for proposals whose spec
# header reads `Status: Accepted`.

[proposals."0001"]
status = "implemented"
since = "0.5.0"

[proposals."0002"]
status = "implemented"
since = "0.5.0"

[proposals."0003"]
status = "implemented"
since = "0.5.0"

[proposals."0004"]
status = "implemented"
since = "0.5.0"

[proposals."0005"]
status = "implemented"
since = "0.5.0"

[proposals."0006"]
status = "implemented"
since = "0.5.0"

[proposals."0007"]
status = "implemented"
since = "0.5.0"

[proposals."0008"]
status = "implemented"
since = "0.5.0"

[proposals."0009"]
status = "implemented"
since = "0.9.0"

[proposals."0010"]
status = "implemented"
since = "0.9.0"

[proposals."0011"]
status = "implemented"
since = "0.6.0"

[proposals."0012"]
status = "implemented"
since = "0.5.0"

[proposals."0013"]
status = "implemented"
since = "0.5.0"

[proposals."0014"]
status = "implemented"
since = "0.6.0"

[proposals."0015"]
status = "implemented"
since = "0.6.0"

[proposals."0016"]
status = "implemented"
since = "0.6.0"

[proposals."0017"]
status = "implemented"
since = "0.6.0"

[proposals."0018"]
status = "implemented"
since = "0.6.0"

[proposals."0019"]
status = "textual-only"
since = "0.9.0"
note = "Purely textual reframe of llm-provider §8 as a catalog of wire-format mappings (OpenAI-compatible body nested under §8.1). No module-level change required."

[proposals."0024"]
status = "implemented"
since = "0.8.0"

[proposals."0025"]
status = "implemented"
since = "0.9.0"

[proposals."0026"]
status = "textual-only"
since = "0.9.0"
note = "Purely textual §8 framing paragraph; the existing OpenAI §8.1 mapping is the template's reference shape, so no module-level work was needed."

[proposals."0027"]
status = "implemented"
since = "0.9.0"

[proposals."0028"]
status = "implemented"
since = "0.9.0"

[proposals."0029"]
status = "implemented"
since = "0.9.0"

[proposals."0030"]
status = "textual-only"
since = "0.9.0"
note = "Drain snapshot semantic and timeout-input validation already implemented as part of the proposal 0010 impl PR (v0.9.0); no additional module-level work needed."

# Spec v0.23.0-v0.27.1 batch (proposals 0031, 0032, 0033, 0034, 0035,
# 0036), all shipped in the v0.10.0 release.
[proposals."0031"]
status = "implemented"
since = "0.10.0"

[proposals."0032"]
status = "implemented"
since = "0.10.0"

[proposals."0033"]
status = "implemented"
since = "0.10.0"

[proposals."0034"]
status = "implemented"
since = "0.10.0"

[proposals."0035"]
status = "implemented"
since = "0.10.0"

[proposals."0036"]
status = "implemented"
since = "0.10.0"

# Spec v0.28.0-v0.31.0 (proposals 0037, 0039, 0040, 0041).
[proposals."0037"]
status = "not-yet"

[proposals."0039"]
status = "implemented"
since = "0.11.0"

[proposals."0040"]
status = "implemented"
since = "0.11.0"

[proposals."0041"]
status = "implemented"
since = "0.11.0"

# Spec v0.32.0-v0.34.0 (proposals 0038, 0020, 0042).
[proposals."0038"]
status = "not-yet"

[proposals."0020"]
status = "not-yet"

# Spec (proposal 0021).  Suspension capability — async-pause +
# resume primitive (``suspend()`` + ``resume()``) layering on the
# graph engine.  Python has not yet shipped suspension; v0.13.0
# leaves the capability not-yet-implemented.
[proposals."0021"]
status = "not-yet"

# Spec v0.49.0 (proposal 0022).  Harness capability — abstract
# contract for wrapping the engine in deployment runtimes
# (HTTP / event-bus / queue / CLI / streaming).  Python has not
# yet shipped a harness binding; v0.13.0 leaves the capability
# not-yet-implemented.  Composes with 0056 (chat sub-spec).
[proposals."0022"]
status = "not-yet"

# Spec v0.52.0 (proposal 0023).  Canonical state reducers — three
# new factory-style reducers (``bounded_append``, ``dedupe_append``,
# ``merge_by_key``) extending the graph-engine §2 baseline set.
# Python has not yet shipped the new reducers; v0.13.0 leaves the
# capability not-yet-implemented. Conformance fixtures 035-038
# stay parser-deferred until the implementation lands.
[proposals."0023"]
status = "not-yet"

[proposals."0042"]
status = "implemented"
since = "0.11.0"

# Spec v0.35.0 (proposal 0043).
[proposals."0043"]
status = "implemented"
since = "0.11.0"

# Spec v0.36.0 (proposal 0044).
[proposals."0044"]
status = "implemented"
since = "0.11.0"

# Spec v0.37.0 (proposal 0045).  Engine-side per-depth lineage chains
# + observer-side three-step boundary decision tree implemented.
# Single-level fixtures 029 / 030 / 034 stay unchanged per 0045's
# backward-compat note.  Nested-case fixture 039 stays deferred in the
# Langfuse harness — needs runtime-state item-list lookup for nested
# fan-outs plus an ``augment_metadata_from_outer_item`` directive.
# Behavioral contract verified at unit level via
# ``test_nested_fan_out_augmentation_reaches_outer_instance_dispatch_span``.
[proposals."0045"]
status = "implemented"
since = "0.11.0"

# Spec v0.38.0 (proposal 0046).  Multi-message chat-prompt rendering.
# Adds ``ChatPrompt`` alongside the existing ``TextPrompt`` (renamed
# from ``Prompt``); ``Prompt`` is now the discriminated-union alias.
# Chat-prompt segments (content + placeholder) and content-block
# templates (text + image-URL + image-inline) ship in
# ``openarmature.prompts``.  ``PromptManager.render`` accepts a new
# ``placeholders`` kwarg for variable-length message-list injection.
# Conformance fixtures 017-031 activate against the existing
# prompt-management harness with a chat-template parser extension.
[proposals."0046"]
status = "implemented"
since = "0.11.0"

# Spec v0.39.0 (proposal 0047).  Implicit prefix-cache wire-byte
# stability.  Cross-capability proposal landed end-to-end in the
# v0.13.0 cycle across three pieces, all post-v0.12.0:
# (1) ``Response.usage`` cache-stat fields (``cached_tokens`` /
# ``cache_creation_tokens``) sourced from the OpenAI
# ``prompt_tokens_details`` payload, with conditional emission
# preserved (absent-vs-zero distinction stays observable) — landed
# in PR #136 as the proposal's payload-side prerequisite;
# (2) OTel observer emits ``openarmature.llm.cache_read.input_tokens``
# (and optional ``openarmature.llm.cache_creation.input_tokens``)
# when the corresponding usage field is populated — landed in
# PR #140; (3) §8.1 intra-impl wire-byte canonicalization in the
# OpenAI adapter — landed in PR #145. The canonicalizer recursively
# sorts dict keys at every nesting level while preserving caller-
# supplied array order, applied at the four user-input boundaries
# (``tool.parameters`` / ``tool.function`` record top-level per
# spec Q5, ``response_format.json_schema.schema``, ``RuntimeConfig``
# extras, ``tool_call.arguments`` JSON encoding) plus a top-level
# belt-and-suspenders pass over the assembled request body.
# Downstream-observable wire-byte shift on
# ``tool_call.arguments``: the encoded string now uses
# ``sort_keys=True`` (functionally equivalent — parses to the same
# dict — but byte-different for golden-file / audit-snapshot
# consumers).  Scope is the Chat Completions endpoint only; the
# OpenAI Responses API endpoint is deferred to a future cycle (no
# python consumer today).  Prompt-management §13 cross-variable
# substring stability is satisfied by the existing Jinja2
# ``StrictUndefined`` render path; pinned by
# ``tests/unit/test_prompts.py::
# test_cross_variable_substring_stability_text_prompt`` and
# ``test_cross_variable_substring_stability_chat_prompt``.
# Anthropic / Gemini wire-byte conformance fixtures stay deferred
# — neither provider is implemented in python today.
[proposals."0047"]
status = "implemented"
since = "0.13.0"

# Spec v0.40.0 (proposal 0048).  Read-symmetric invocation metadata.
# Adds ``get_invocation_metadata()`` symmetric to the existing
# ``set_invocation_metadata()`` write API.  The python implementation
# satisfies the §3.4 read contract via the pre-existing
# ``current_invocation_metadata`` machinery: returns ``MappingProxyType``
# snapshot of the current async context's view, silent no-op outside
# an invocation, no observer emission, per-async-context scoping under
# fan-out and parallel-branches (inherited from 0034/0040/0045),
# per-attempt scoping under retry (engine-side reset of
# ``_invocation_metadata_var`` around each ``RetryMiddleware`` iteration,
# landed in the same release cycle as 0048).
# ``get_invocation_metadata`` lands as the canonical spec-idiomatic
# public name; ``current_invocation_metadata`` stays as a stable
# alias (Option A per the proposal-0048-implementation coord thread).
# Plus a new §9 *Queryable observer pattern* section in
# ``docs/concepts/observability.md`` covering the §9.1 read-method
# contract, §9.2 async-safety, §9.3 three-channel guidance, §9.4
# lifecycle.  §9 is convention-only per spec — no new abstract
# surface on ``Observer``.
#
# Conformance fixtures 043-049 introduce new directive shapes
# (augment_metadata / capture_invocation_metadata_into /
# capture_queryable_observer_read_into / per_attempt_behavior +
# queryable_observers / inner_subgraphs / caller_metadata /
# direct_call / sequential_invocations top-level keys) that the
# cross-capability parser doesn't model; fixture-shape activation is
# queued for a future PR slotted after the upcoming spec
# conformance-adapter capability ratifies the directive vocabulary.
# The shipped contract is pinned by explicit unit tests:
#   - alias identity + roundtrip + immutable-mapping return:
#     ``tests/unit/test_observability_metadata.py::
#     test_get_invocation_metadata_is_same_callable_as_current``,
#     ``::test_get_invocation_metadata_roundtrip_baseline_plus_augment``,
#     ``::test_get_invocation_metadata_returns_immutable_mapping_outside_invocation``;
#   - mid-invocation augmentation visible to subsequent reads:
#     ``::test_mid_invocation_augmentation_persists_to_next_node``;
#   - outside-invocation empty:
#     ``::test_current_invocation_metadata_empty_outside_invocation``;
#   - per-attempt scoping under retry (mirrors spec fixture 045):
#     ``::test_per_attempt_scoping_under_retry_discards_failed_attempt_writes``,
#     ``::test_terminal_failure_discards_final_failed_attempt_writes``,
#     ``::test_cancellation_discards_in_flight_attempt_writes``.
[proposals."0048"]
status = "implemented"
since = "0.12.0"

# Spec v0.41.0 (proposal 0049).  Typed LLM Completion Event — first
# typed event variant on the observer event union.  Shipped fully in
# v0.13.0 across PRs #141 (typed-event definition + provider
# emission + 0057 field-set extension), #142 (OTel observer migration
# to type discrimination), #143 (Langfuse observer migration +
# success-side sentinel emission dropped), and #144 (0058 typed
# LlmFailedEvent + sentinel-namespace NodeEvent emission for LLM
# events retired entirely from the bundled OpenAIProvider).
# LlmCompletionEvent carries identity/scoping/outcome fields per
# the spec field table.  Both bundled observers (OTel + Langfuse)
# consume the typed events via isinstance discrimination on both
# outcome paths.  Conformance fixtures 050-056 activated by the
# typed_event_collector harness directive.  Fixtures 057-068
# (proposal 0057 request-side fields) and 069-073 (proposal 0058
# typed failure event) stay parser-deferred pending the harness's
# typed_event_collector directive schema catch-up + the event_counts
# list directive introduced by fixture 071; behavior pinned by
# unit tests in tests/unit/test_llm_provider.py +
# test_observability_otel.py + test_observability_langfuse.py.
[proposals."0049"]
status = "implemented"
since = "0.13.0"

# Spec v0.42.0 (proposal 0050).  Retry & degradation primitives —
# failure-isolation middleware (§6.3) + call-level retry (§7).  Both
# primitives implemented across the v0.14.0 cycle:
# FailureIsolationMiddleware (distinct FailureIsolatedEvent +
# CaughtException) and the call-level ``retry`` parameter on
# ``Provider.complete()`` — an in-call loop over transient §7 errors
# reusing the §6.1 RetryConfig record.  ``partial`` because §7.1's
# per-attempt span surface — N ``openarmature.llm.complete`` spans +
# the ``openarmature.llm.attempt_index`` attribute — is DEFERRED: the
# python LLM span is rendered from the typed event, which is
# terminal-only per the graph-engine §6 mutual-exclusion contract, so
# per-attempt spans require a dedicated within-call sub-event
# (LlmRetryAttemptEvent) scoped to a future cycle.  Call-level retry
# ships terminal-only: exactly one LlmCompletionEvent / LlmFailedEvent
# per ``complete()`` call.  Failure-isolation conformance fixtures
# (058-063) are all wired + passing: the FailureIsolatedEvent's
# attempt_index reports the final / exhausting attempt per §6.3's
# lineage-correlation rule (spec ruled this in the attempt-index coord
# thread; RetryMiddleware now records the final attempt in a
# terminal-attempt scope the outer isolation reads, rather than the
# post-reset baseline).  ``partial`` is now solely about the
# call-level-retry per-attempt span surface above.
[proposals."0050"]
status = "partial"
since = "0.14.0"

# Spec v0.43.0 (proposal 0051).  Langfuse trace.input/trace.output
# implementation-surface caveat.  Purely textual: documents that the
# Langfuse SDK's ``LangfuseClient`` API requires a trace object
# round-trip to project caller-side ``trace.input`` / ``trace.output``
# updates onto the wire.  No module-level change required; the python
# implementation's existing v0.11.0 (proposal 0043) shape already
# matches the documented behavior.
[proposals."0051"]
status = "textual-only"
since = "0.12.0"

# Spec v0.44.0 (proposal 0052).  Implementation attribution attributes
# on every invocation span (§5.1) + every Langfuse Trace (§8.4.1).
# The OTel observer emits ``openarmature.implementation.name`` +
# ``openarmature.implementation.version`` on the invocation span
# alongside the existing ``openarmature.graph.spec_version``; inner
# spans do NOT carry them (per §5.1 they are invocation-span-only,
# not cross-cutting §5.6).  The Langfuse observer mirrors with
# ``trace.metadata.implementation_name`` +
# ``trace.metadata.implementation_version`` rows on both trace-open
# paths (the proposal 0043 boundary-event lazy-open path and the
# legacy NodeEvent path).  Always-emit invariant: neither
# ``disable_state_payload`` nor any other privacy knob gates these
# attributes — they describe runtime identity, not runtime data.
#
# Source: ``__implementation_name__`` ("openarmature-python") added
# to ``openarmature/__init__.py`` alongside the existing version
# constants; ``__version__`` is the package version source.
# Configurable via dataclass fields on both observers for test
# parameterization.
#
# §3.4 reserved-key set grows 24 -> 26 names: ``implementation_name``
# and ``implementation_version`` reject caller-supplied collision at
# the ``invoke()`` API boundary.
#
# Conformance fixtures: 058 (OTel) parses cleanly via the existing
# ``span_tree`` + ``attributes_absent`` directive shapes — its
# cross-capability parser test passes; runtime exec is gated by
# ``_SUPPORTED_FIXTURES`` in ``test_observability.py`` until the
# harness wires up the canonical-value parameterization. 059
# (Langfuse) stays deferred from the cross-capability parser
# pending the upcoming conformance-adapter capability — same Path A
# reasoning as the 0048 / 0054 fixtures. Behavior is pinned by unit
# tests:
#   - reserved-key rejection (validate / set_invocation_metadata /
#     invoke() boundary for both names):
#     ``tests/unit/test_observability_metadata.py::
#     test_validate_rejects_reserved_implementation_name``,
#     ``::test_validate_rejects_reserved_implementation_version``,
#     ``::test_set_invocation_metadata_rejects_reserved_implementation_name``,
#     ``::test_set_invocation_metadata_rejects_reserved_implementation_version``,
#     ``::test_invoke_rejects_reserved_implementation_name_at_boundary``,
#     ``::test_invoke_rejects_reserved_implementation_version_at_boundary``;
#   - OTel invocation span carries the attributes; inner spans do
#     not:
#     ``tests/unit/test_observability_otel.py::
#     test_invocation_span_carries_implementation_attribution_attributes``;
#   - OTel always-emit invariant under ``disable_provider_payload``,
#     ``disable_genai_semconv``, ``disable_llm_spans``:
#     ``::test_invocation_span_attribution_emits_under_disable_provider_payload``;
#   - OTel attributes emit on every invocation span across a
#     reused observer (3 sequential invocations):
#     ``::test_invocation_span_attribution_emits_on_every_invocation``;
#   - Langfuse Trace metadata carries the rows + always-emit
#     invariant under ``disable_state_payload=True``:
#     ``tests/unit/test_observability_langfuse.py::
#     test_trace_metadata_carries_implementation_attribution_rows``,
#     ``::test_implementation_attribution_rows_emit_with_disable_state_payload_enabled``;
#   - Langfuse rows emit on every Trace across a reused observer (3
#     sequential invocations):
#     ``::test_implementation_attribution_rows_emit_on_every_trace``.
#
# Fixture 058 case 2 ("detached_subgraph_attribution_propagates_
# _to_child_trace_invocation_span") expects two ``openarmature.invocation``
# spans (parent + detached child trace), but fixture 008 establishes
# that detached subgraphs root in their subgraph-dispatch span — NOT
# in a separate invocation span. The two fixtures appear inconsistent.
# Not deferring 058's parsing (it parses cleanly), but the runtime
# exec contract for the detached-child-invocation-span case needs
# coord-thread resolution before activation. The python implementation
# emits the attribution attributes on every invocation span it opens
# (pinned by the multi-invocation test above), so the 0052 contract
# itself is honored.
[proposals."0052"]
status = "implemented"
since = "0.12.0"

# Spec v0.45.0 (proposal 0053).  §3.4 shared-parent boundary
# clarification.  Purely textual: tightens the structural-shared-parent
# classification to predicate the invocation span on whether at least
# one fan-out or parallel-branches dispatch is on the augmenter's
# call-stack path.  Implementation-side: behavior already matches the
# clarified contract via fixtures 034 (outermost-serial augmentation
# reaches the invocation span) and 039 (nested cases do not).  No
# module-level change required.
[proposals."0053"]
status = "textual-only"
since = "0.12.0"

# Spec v0.46.0 (proposal 0054).  Per-invocation observer event drain
# (``CompiledGraph.drain_events_for(invocation_id, *, timeout) ->
# DrainSummary``).  Shipped in v0.12.0 — the architectural pair to
# 0048's §9.4 queryable observer accumulator lifecycle.  Engine
# implementation: per-invocation waker Futures on the existing
# ``_DrainCounters``; ``deliver_loop`` fulfils waiters whose target
# delivered-count has been reached.  Reuses the existing
# ``DrainSummary`` shape verbatim per the
# discuss-per-invocation-event-drain coord thread's Q4 direction.
# Default timeout is 5.0 seconds (recommended-value nudge per the
# coord-thread Q3 direction; spec leaves the default to the
# implementation).
#
# Key divergence from process-wide ``drain()``: per-invocation drain
# MUST NOT cancel the deliver worker on timeout (the graph remains
# active and other invocations may still be in flight); ``drain()``
# cancels because it's a shutdown primitive.
#
# Conformance fixtures (graph-engine/028-033) stay deferred from the
# cross-capability parser pending the upcoming spec conformance-
# adapter capability — same Path A reasoning as the 0048 fixtures.
# Behavior is pinned by unit tests:
#   - basic synchronization (mirrors fixture 028):
#     ``tests/unit/test_drain.py::
#     test_drain_events_for_basic_synchronization``;
#   - snapshot semantic / no-deadlock-on-own-completed-event
#     (mirrors fixture 029):
#     ``::test_drain_events_for_snapshot_semantic_does_not_wait_for_own_completed_event``;
#   - worker-NOT-cancelled-on-timeout (mirrors fixture 030, the
#     load-bearing divergence-from-drain contract):
#     ``::test_drain_events_for_timeout_does_not_cancel_worker``;
#   - invocation-scope isolation (mirrors fixture 031):
#     ``::test_drain_events_for_invocation_scope_isolation``;
#   - fan-out coverage (mirrors fixture 032; subgraph descents share
#     parent counters):
#     ``::test_drain_events_for_covers_fan_out_instance_events``;
#   - parallel-branches coverage (mirrors fixture 033):
#     ``::test_drain_events_for_covers_parallel_branches_events``;
#   - zero-timeout non-blocking check:
#     ``::test_drain_events_for_zero_timeout_is_non_blocking_check``;
#   - unknown invocation_id returns clean summary:
#     ``::test_drain_events_for_unknown_invocation_returns_clean_summary``;
#   - negative + NaN timeout rejected at boundary:
#     ``::test_drain_events_for_rejects_negative_timeout``,
#     ``::test_drain_events_for_rejects_nan_timeout``.
[proposals."0054"]
status = "implemented"
since = "0.12.0"

# Spec v0.47.0 (proposal 0055).  Conformance-adapter capability —
# descriptive ratification of the existing fixture / directive
# system. No code change; python's adapter is already structured
# per the spec text by virtue of having grown alongside the
# fixtures since proposal 0001.  Matches the Textual impl-tracking
# precedent (0019 / 0026 / 0030 / 0051 / 0053).
[proposals."0055"]
status = "textual-only"
since = "0.13.0"

# Spec v0.48.0 (proposal 0056).  Harness-chat capability — new
# harness sub-spec ratifying the chat-loop deployment shape
# (ChatMessage, conversation-history convention, send() callable,
# send_streaming() forward-looking surface, error-bucket → user-
# facing-reply mapping).  Python does not yet ship a chat-harness
# binding; v0.13.0 leaves the capability not-yet-implemented.
[proposals."0056"]
status = "not-yet"

# Spec v0.51.0 (proposal 0057).  LlmCompletionEvent field-set
# extension — eight additive request-side fields on the typed
# event variant + ``request_id`` → ``response_id`` rename + new
# ``response_model`` field.  Python lands the field-set extension
# + rename + provider population in v0.13.0 PR 3a; OTel + Langfuse
# observers continue driving their §5.5 surface off the sentinel
# NodeEvent pair through this PR (observer migration to type
# discrimination is queued for follow-up PRs 3b / 3c against the
# same v0.13.0 release).
[proposals."0057"]
status = "implemented"
since = "0.13.0"

# Spec v0.53.0 (proposal 0058).  Typed LLM failure event — second
# spec-normatively-typed event variant on the observer event union
# alongside LlmCompletionEvent. Field set mirrors LlmCompletionEvent's
# identity / scoping / request-side surface (17 fields) plus three
# failure-specific fields (error_category from the §7 normative
# category enumeration, optional vendor-specific error_type, always-
# present error_message). Dispatched alongside the §7 exception on
# the observer queue — caller-side exception flow unchanged.
# Mutually exclusive with LlmCompletionEvent on the same call. Python
# lands the typed variant + provider emission + OTel/Langfuse
# consumer migration in v0.13.0; same PR also drops sentinel-namespace
# NodeEvent emission for LLM events entirely from the bundled
# OpenAIProvider.
[proposals."0058"]
status = "implemented"
since = "0.13.0"

# Spec v0.54.0 (proposal 0059).  Retrieval-provider capability —
# the ``EmbeddingProvider`` protocol + ``EmbeddingEvent`` /
# ``EmbeddingFailedEvent`` typed variants + OTel/Langfuse embedding
# mapping.  Python has not yet shipped the embedding surface, so the
# capability is not-yet.  The one piece adopted at this pin is the
# proposal's cross-spec consequence: the observer-level privacy flag
# ``disable_llm_payload`` is renamed ``disable_provider_payload`` (the
# §5.5.4 rename touches existing LLM-payload gating, so it lands with
# the pin even though the embedding capability does not).
[proposals."0059"]
status = "not-yet"

# Spec v0.55.0 (proposal 0065; repo pins v0.55.1).  Failure-isolation
# cause fidelity at non-node placements (pipeline-utilities §6.3 /
# §11.7).  At instance (§9.7), branch (§11.7), and parent-node
# middleware sites the engine wraps the originating error as a §4
# ``node_exception`` carrier before isolation catches it;
# ``FailureIsolatedEvent.caught_exception.category`` now resolves
# THROUGH that carrier to the originating cause instead of reporting the
# masking ``node_exception``.  Fixture 064 (three cases) passes;
# node-level placement (fixture 061) was already faithful.  The pin is
# v0.55.1 rather than v0.55.0 because v0.55.1 adds an observability §11
# span-links text reconciliation (no proposal, no python-observable
# change).
[proposals."0065"]
status = "implemented"
since = "0.14.0"

# Spec v0.56.0 (proposal 0066).  Fan-out failure-isolation degrade
# contribution (pipeline-utilities §9.3 / §9.8 / §11.7).  A degraded
# fan-out instance is a success whose contribution IS its degraded_update
# (subgraph-space, read by subgraph field name; ``extra_outputs`` keyed by
# subgraph field too, fixing a latent drop).  A static degraded_update
# omitting collect_field is a compile error
# (``fan_out_degraded_update_missing_collect_field``); a callable that omits
# it yields a graceful null slot (no raise).  The §11.7 parallel-branches
# counterpart skips an uncovered projected field.  Fixture 065 (four
# cases) passes.
[proposals."0066"]
status = "implemented"
since = "0.14.0"