Add detached-trace invocation span (0061) (#168)

* Add detached-trace invocation span (0061)

The OTel observer now synthesizes an openarmature.invocation span at
the root of each detached trace (a detached subgraph and each detached
fan-out instance), carrying the parent's shared invocation_id and the
detached unit's own entry_node, with the detached subgraph/instance
span nested beneath it. A raising detached subgraph surfaces ERROR plus
the error category and an exception event on both the parent dispatch
span and the detached invocation span.

Observer-side only: no graph-engine change, and the Langfuse observer
is unchanged. Pins the spec submodule to v0.61.0 and brings conformance
fixtures 008 (rewritten) and 058 (newly covered) live.

* Clear stale detached-error marker on span open

errored_detached_keys gates the synthetic close paths' default
set_status(OK) so a detached-trace ERROR survives export. The set is
invocation-scoped but never cleared mid-invocation, so a detached
prefix that errors and then re-runs successfully within the same
invocation (cyclic or fire-and-forget re-entry) could leave the later
success span UNSET instead of OK.

Discard the key when a fresh detached invocation span opens at it (the
only point keys are introduced), so each generation's close reflects
only its own status. Reading the live span status was rejected as it
depends on _Span.status, which is not part of the public OTel Span
interface.

Author: chris-colinsky

conformance.toml

@@ -687,3 +687,10 @@ since = "0.14.0"
 status = "textual-only"
 since = "0.14.0"
 note = "Descriptive catalog of the failure-mock family (flaky + failure_sequence, flaky_by_index, flaky_per_index, flaky_instance_only, flaky_resume_aware) that the adapter already implements and the existing retry / failure-isolation / checkpoint-resume fixtures exercise; no new behavior, no new fixtures, no code change. Mirrors 0055's textual-only treatment of the conformance-adapter capability. The success-state naming drift (success_update / on_success / success_compute) is documented as-is by the proposal and left unchanged."
+
+# Spec v0.61.0 (proposal 0061).  Detached-trace invocation span
+# (observability §4.4 / §4.3 / §4.1 / §4.2 / §5.1).
+[proposals."0061"]
+status = "implemented"
+since = "0.15.0"
+note = "The OTel observer synthesizes an openarmature.invocation span at the root of each detached trace (a detached subgraph + each detached fan-out instance), carrying the parent's SHARED invocation_id (detached mode is observer-side trace rendering, not a new run) and the detached unit's own entry_node; the detached subgraph / instance span nests under it. A raising detached subgraph surfaces ERROR + the category + an OTel exception event on BOTH the parent dispatch span and the detached invocation span. Observer-side only -- no graph-engine change; the Langfuse observer is unchanged (its Trace entity already plays the invocation-level-container role). Fixtures 008 (rewritten) and 058 (newly wired) run in test_observability."

docs/concepts/observability.md

@@ -644,8 +644,11 @@ obs = OTelObserver(
 )
 ```
 
-A detached subgraph or fan-out gets a fresh trace root (new
-`trace_id`); the `correlation_id` still propagates through, so
+A detached subgraph or fan-out renders into a fresh trace, rooted in
+its own `openarmature.invocation` span that carries the same
+`invocation_id` as the parent (detached mode is an observer-side
+rendering choice, not a separate run). The new trace has a fresh
+`trace_id`, and the `correlation_id` still propagates through, so
 join semantics survive even when trace boundaries don't.
 
 The non-detached default is what you want most of the time: one

openarmature-spec

@@ -63,7 +63,7 @@ Specification = "https://github.com/LunarCommand/openarmature-spec"
 openarmature = "openarmature.cli:main"
 
 [tool.openarmature]
-spec_version = "0.60.0"
+spec_version = "0.61.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.60.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.14.0 (spec v0.61.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.60.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.61.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.60.0"
+__spec_version__ = "0.61.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