Clean up docs nav titles and default uv toolchain (#91)

* De-hyphenate pattern titles in docs nav

The Patterns section showed kebab-case titles inherited from the
filenames (Tool-dispatch-as-node, Session-as-checkpoint-resume,
Bypass-if-output-exists), inconsistent with "Parameterized entry
point". Convert the nav labels, page H1s, and index catalog links
to spaced titles.

Filenames stay kebab-case: they are the canonical pattern slugs
behind patterns.get() / patterns.list(), so the link targets and
the public API surface are unchanged.

* Default full local toolchain in uv sync

A plain `uv run mkdocs serve` failed because mkdocs lives in the docs
dependency group, which uv does not sync by default. The docs and
examples groups and the otel/langfuse extras were absent from the
default environment.

Add a [tool.uv] default-groups covering dev, docs, examples, and a
new observability group. uv can default groups but not extras, so the
observability group self-references the public otel/langfuse extras to
pull them into the default-synced env. Regenerate uv.lock to record
the new group.

* Regenerate bundled agent docs for pattern titles

The de-hyphenate commit changed docs/patterns/ H1s but not the
artifacts generated from them: src/openarmature/AGENTS.md and the
src/openarmature/_patterns/ copies the patterns API serves. The
drift test caught the mismatch in CI.

Regenerate both via scripts/build_agents_md.py so the bundled recipe
titles match the docs. Pattern slugs (filenames / API keys) are
unchanged.

Author: chris-colinsky

docs/patterns/bypass-if-output-exists.md

@@ -1,4 +1,4 @@
-# Bypass-if-output-exists
+# Bypass if output exists
 
 **Problem.** How do I skip a node whose external output already
 exists?

docs/patterns/index.md

@@ -25,11 +25,11 @@ docs composing existing primitives.
 
 - [Parameterized entry point](parameterized-entry-point.md) —
   start the graph at an arbitrary node via state-driven routing.
-- [Tool-dispatch-as-node](tool-dispatch-as-node.md) — model an
+- [Tool dispatch as node](tool-dispatch-as-node.md) — model an
   agent tool-call loop as a graph cycle.
-- [Session-as-checkpoint-resume](session-as-checkpoint-resume.md) —
+- [Session as checkpoint resume](session-as-checkpoint-resume.md) —
   carry multi-turn agent state across turns using the existing
   checkpointer.
-- [Bypass-if-output-exists](bypass-if-output-exists.md) —
+- [Bypass if output exists](bypass-if-output-exists.md) —
   short-circuit a node whose external output already exists, via
   middleware.

docs/patterns/session-as-checkpoint-resume.md

@@ -1,4 +1,4 @@
-# Session-as-checkpoint-resume
+# Session as checkpoint resume
 
 **Problem.** How do I keep multi-turn agent state across turns?
 

docs/patterns/tool-dispatch-as-node.md

@@ -1,4 +1,4 @@
-# Tool-dispatch-as-node
+# Tool dispatch as node
 
 **Problem.** How do I run an agent tool-call loop?
 

mkdocs.yml

@@ -118,9 +118,9 @@ nav:
   - Patterns:
     - patterns/index.md
     - Parameterized entry point: patterns/parameterized-entry-point.md
-    - Tool-dispatch-as-node: patterns/tool-dispatch-as-node.md
-    - Session-as-checkpoint-resume: patterns/session-as-checkpoint-resume.md
-    - Bypass-if-output-exists: patterns/bypass-if-output-exists.md
+    - Tool dispatch as node: patterns/tool-dispatch-as-node.md
+    - Session as checkpoint resume: patterns/session-as-checkpoint-resume.md
+    - Bypass if output exists: patterns/bypass-if-output-exists.md
   - Examples:
     - examples/index.md
     - Hello, world: examples/00-hello-world.md

pyproject.toml

@@ -85,6 +85,18 @@ docs = [
 examples = [
     "openai>=1.40",
 ]
+# Self-references the project's public otel + langfuse extras so the
+# observability backends can be defaulted into the local env: uv can
+# default dependency groups but not extras.
+observability = ["openarmature[otel,langfuse]"]
+
+[tool.uv]
+# Default-synced env for local work so a plain `uv run` (mkdocs
+# serve, the examples, pytest) needs no per-command flags. Naming
+# default-groups overrides uv's built-in ["dev"] default, hence "dev"
+# is re-listed. The "observability" group carries the otel/langfuse
+# extras, which uv otherwise can't default.
+default-groups = ["dev", "docs", "examples", "observability"]
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/openarmature"]

src/openarmature/AGENTS.md

@@ -402,7 +402,7 @@ treats fetch and render as separable.
 
 _Recipes that compose the primitives. Not framework contracts — these are how to do common things idiomatically._
 
-### Bypass-if-output-exists
+### Bypass if output exists
 
 **Problem.** How do I skip a node whose external output already
 exists?
@@ -614,7 +614,7 @@ fields the chosen branch needs) and the graph routes accordingly.
 - [Checkpointing](https://openarmature.ai/concepts/checkpointing/)
 - Spec: [graph-engine](https://openarmature.org/capabilities/graph-engine/)
 
-### Session-as-checkpoint-resume
+### Session as checkpoint resume
 
 **Problem.** How do I keep multi-turn agent state across turns?
 
@@ -729,7 +729,7 @@ state and the session table holds the join keys.
   single-resume baseline.
 - Spec: [pipeline-utilities](https://openarmature.org/capabilities/pipeline-utilities/)
 
-### Tool-dispatch-as-node
+### Tool dispatch as node
 
 **Problem.** How do I run an agent tool-call loop?
 

src/openarmature/_patterns/bypass-if-output-exists.md

@@ -1,4 +1,4 @@
-# Bypass-if-output-exists
+# Bypass if output exists
 
 **Problem.** How do I skip a node whose external output already
 exists?

src/openarmature/_patterns/session-as-checkpoint-resume.md

@@ -1,4 +1,4 @@
-# Session-as-checkpoint-resume
+# Session as checkpoint resume
 
 **Problem.** How do I keep multi-turn agent state across turns?
 

src/openarmature/_patterns/tool-dispatch-as-node.md

@@ -1,4 +1,4 @@
-# Tool-dispatch-as-node
+# Tool dispatch as node
 
 **Problem.** How do I run an agent tool-call loop?