Clarify user and integration documentation contracts

docs/integrations/audita.md

@@ -3,16 +3,12 @@
 ## Purpose
 Define the Audita adapter contract used by the `polish` stage.
 
-## Adapter Boundary
-Interface:
-- `audita.Runner`
-- method: `Run(ctx, PolishRequest) (PolishResult, error)`
+## External Boundary
 
-Primary implementation:
-- `internal/adapters/audita/SubprocessRunner`
-
-Execution mode:
-- subprocess invocation of `audita process`
+Narratio invokes `audita process` as a subprocess for each polish operation.
+The configured timeout and parent cancellation bound the invocation. Internal
+runner composition is documented in
+[the adapter implementation guide](../internal/adapters.md).
 
 ## Request Contract
 `PolishRequest` carries:
@@ -52,8 +48,10 @@ Failure results still include output/log/config/exit metadata for diagnostics.
 - Generated invocation YAML (`audita.generated.v1`) is emitted when requested.
 - Manifest writes are stage-owned; adapter itself is stateless.
 
-## Config Mapping
-Config fields consumed through runner/stage wiring are under `pipeline.audita.*`.
+## Configuration
+
+Operator-selected values are defined under `pipeline.audita.*` in the
+[configuration reference](../config.md#pipeline).
 
 Maintained example with Audita config:
 - `examples/pipeline.full.annotated.yml`