docs: correct defaults, lifecycle and install facts (#267)

- README: second bootstrapper on one app raises ConfigurationError from bootstrap(); list FastMCP
- configuration: Prometheus, swagger and health checks are on by default; OTel also enabled by
  opentelemetry_log_traces; document opentelemetry_insecure default and warning, and the
  ignored litestar_logging_middleware_config warning; drop removed-field history
- quickstart: say which instruments are on by default; skipped_instruments omits dep-missing skips
- free: use FreeConfig instead of the backward-compatible alias
- performance: include the logging table the text refers to; trim prose
- fastmcp: drop version-history paragraph
- quote extras in install commands so zsh does not glob them; Litestar spelling

Author: lesnik512

README.md

@@ -18,7 +18,7 @@
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 [![ty](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ty/main/assets/badge/v0.json)](https://github.com/astral-sh/ty)
 
-`lite-bootstrap` wires production observability — OpenTelemetry, Prometheus, Sentry, and structlog — into FastAPI, Litestar, and FastStream services in a few lines, with no boilerplate.
+`lite-bootstrap` wires production observability — OpenTelemetry, Prometheus, Sentry, and structlog — into FastAPI, Litestar, FastStream, and FastMCP services in a few lines, with no boilerplate.
 
 With `lite-bootstrap`, you receive an application with lightweight built-in support for:
 
@@ -33,7 +33,7 @@ With `lite-bootstrap`, you receive an application with lightweight built-in supp
 
 Those instruments can be bootstrapped for:
 
-- [LiteStar](https://lite-bootstrap.modern-python.org/integrations/litestar/)
+- [Litestar](https://lite-bootstrap.modern-python.org/integrations/litestar/)
 - [FastStream](https://lite-bootstrap.modern-python.org/integrations/faststream/)
 - [FastAPI](https://lite-bootstrap.modern-python.org/integrations/fastapi/)
 - [FastMCP](https://lite-bootstrap.modern-python.org/integrations/fastmcp/)
@@ -43,7 +43,7 @@ Those instruments can be bootstrapped for:
 
 A few constraints that aren't obvious from the API:
 
-- **One bootstrapper per application instance.** Constructing two `FastAPIBootstrapper`s around the same `fastapi.FastAPI` (or two `FastMcpBootstrapper`s around the same `FastMCP`) stacks teardown hooks and re-wraps the lifespan. The library warns and skips the second attachment, but the second bootstrapper's `teardown()` won't fire on ASGI shutdown.
+- **One bootstrapper per application instance.** Constructing two `FastAPIBootstrapper`s around the same `fastapi.FastAPI` (or two `FastMcpBootstrapper`s around the same `FastMCP`) is not supported. The second bootstrapper warns at construction, and its `bootstrap()` raises `ConfigurationError`.
 - **One `OpenTelemetryInstrument` per process.** `bootstrap()` calls `opentelemetry.trace.set_tracer_provider(...)`, which the OTel SDK enforces as set-once — subsequent calls log a warning and have no effect. `teardown()` flushes spans and closes exporters but can't reset the process-global pointer.
 - **`teardown()` is idempotent.** `BaseBootstrapper.teardown()` short-circuits if not bootstrapped; per-instrument teardown methods are safe to call multiple times.
 - **Partial teardown failures are aggregated.** If an instrument's teardown raises, the bootstrapper continues with the rest of the instruments and raises `TeardownError` at the end with all collected failures.
@@ -52,7 +52,7 @@ A few constraints that aren't obvious from the API:
 
 Usage examples:
 
-- with LiteStar - [litestar-sqlalchemy-template](https://github.com/modern-python/litestar-sqlalchemy-template)
+- with Litestar - [litestar-sqlalchemy-template](https://github.com/modern-python/litestar-sqlalchemy-template)
 - with FastAPI - [fastapi-sqlalchemy-template](https://github.com/modern-python/fastapi-sqlalchemy-template)
 
 ## Acknowledgements
@@ -68,7 +68,7 @@ The following ideas were borrowed:
 The following intentionally differ:
 
 - **Configuration**: `lite-bootstrap` uses frozen `dataclass` configs (no `pydantic` / `pydantic-settings` runtime dependency), which is what makes it "lite". `microbootstrap` configures everything through `pydantic-settings` models.
-- **Granular extras**: `lite-bootstrap` has exactly **one** mandatory runtime dependency, the pure-Python `typing-extensions`; every instrument (`sentry`, `otl`, `logging`, `pyroscope`) and every framework (`fastapi`, `litestar`, `faststream`) is its own extra, plus an opt-in `orjson` speedup for logging, per-pair combos (`fastapi-sentry`, `litestar-otl`, `faststream-metrics`, …) and `*-all` rollups. You install only what you actually use. It also runs on free-threaded CPython (3.13t/3.14t): every extra whose dependencies are pure Python installs there, and the ones that don't are blocked upstream — `orjson` and `pyroscope` have no free-threaded wheels, and `otl` needs `grpcio`, so use `otl-http` instead. `microbootstrap` bundles the full observability stack (opentelemetry, sentry-sdk, structlog, pyroscope-io, rich, pydantic-settings, …) as base dependencies and only splits framework packages into extras.
+- **Granular extras**: `lite-bootstrap` has exactly **one** mandatory runtime dependency, the pure-Python `typing-extensions`; every instrument (`sentry`, `otl`, `logging`, `pyroscope`) and every framework (`fastapi`, `litestar`, `faststream`, `fastmcp`) is its own extra, plus an opt-in `orjson` speedup for logging, per-pair combos (`fastapi-sentry`, `litestar-otl`, `faststream-metrics`, …) and `*-all` rollups. You install only what you actually use. It also runs on free-threaded CPython (3.13t/3.14t): every extra whose dependencies are pure Python installs there, and the ones that don't are blocked upstream — `orjson` and `pyroscope` have no free-threaded wheels, and `otl` needs `grpcio`, so use `otl-http` instead. `microbootstrap` bundles the full observability stack (opentelemetry, sentry-sdk, structlog, pyroscope-io, rich, pydantic-settings, …) as base dependencies and only splits framework packages into extras.
 - **Scope**: `lite-bootstrap` is deliberately narrow — only instrument wiring. It does not include a Granian server runner or a console writer.
 
 ## 📚 [Documentation](https://lite-bootstrap.modern-python.org)

benchmarks/README.md

@@ -158,13 +158,15 @@ bare FastAPI, so the two tables are not directly comparable.
 
 ### 4c. Logging: cost per record, not per request
 
+<!-- --8<-- [start:logging] -->
 Three records per request, in-process:
 
 | scenario | +µs/req | delta |
 |---|---:|---:|
 | sentry-sdk defaults | +101.1 | |
 | `sentry_logs_level=None` (lite-bootstrap's default since #186) | +93.8 | −2.4 µs/record |
 | also `sentry_logging_breadcrumb_level=None` | +72.4 | −9.6 µs/record total |
+<!-- --8<-- [end:logging] -->
 
 Two handlers run per log record. `SentryLogsHandler.emit` calls `self.format(record)` *before* it
 checks `has_logs_enabled(client.options)`, so with Sentry Logs disabled (the default, and

docs/index.md

@@ -22,7 +22,7 @@ With `lite-bootstrap`, you receive an application with lightweight built-in supp
 
 Those instruments can be bootstrapped for:
 
-- [LiteStar](integrations/litestar.md)
+- [Litestar](integrations/litestar.md)
 - [FastStream](integrations/faststream.md)
 - [FastAPI](integrations/fastapi.md)
 - [FastMCP](integrations/fastmcp.md)

docs/integrations/fastapi.md

@@ -7,19 +7,19 @@
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[fastapi-all]
+      uv add "lite-bootstrap[fastapi-all]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[fastapi-all]
+      pip install "lite-bootstrap[fastapi-all]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[fastapi-all]
+      poetry add "lite-bootstrap[fastapi-all]"
       ```
 
 Read more about available extras [here](../introduction/installation.md).

docs/integrations/fastmcp.md

@@ -5,19 +5,19 @@
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[fastmcp-all]
+      uv add "lite-bootstrap[fastmcp-all]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[fastmcp-all]
+      pip install "lite-bootstrap[fastmcp-all]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[fastmcp-all]
+      poetry add "lite-bootstrap[fastmcp-all]"
       ```
 
 Read more about available extras [here](../introduction/installation.md).
@@ -62,10 +62,6 @@ FastMcpConfig(
 Enabled, each message is logged with its `method`, `source` and `type`, plus `duration` in
 nanoseconds. A message that raises is logged at exception level and the exception is re-raised.
 
-This replaces `logging_turn_off_middleware`, which has been removed. Setting it now raises
-`TypeError`: the default flipped from on to off, so a service that configured the old field has to
-decide again rather than upgrade past the change unnoticed.
-
 Set `health_checks_enabled=False` to omit the health route.
 
 Teardown is wired through FastMCP's provider lifecycle — `bootstrapper.teardown()`

docs/integrations/faststream.md

@@ -5,19 +5,19 @@
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[faststream-all]
+      uv add "lite-bootstrap[faststream-all]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[faststream-all]
+      pip install "lite-bootstrap[faststream-all]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[faststream-all]
+      poetry add "lite-bootstrap[faststream-all]"
       ```
 
 Read more about available extras [here](../introduction/installation.md).

docs/integrations/free.md

@@ -5,30 +5,30 @@
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[free-all]
+      uv add "lite-bootstrap[free-all]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[free-all]
+      pip install "lite-bootstrap[free-all]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[free-all]
+      poetry add "lite-bootstrap[free-all]"
       ```
 
 Read more about available extras [here](../introduction/installation.md).
 
 ## 2. Define bootstrapper config and build your application:
 
 ```python
-from lite_bootstrap import FreeBootstrapperConfig, FreeBootstrapper
+from lite_bootstrap import FreeConfig, FreeBootstrapper
 
 
-bootstrapper_config = FreeBootstrapperConfig(
+bootstrapper_config = FreeConfig(
     opentelemetry_endpoint="otl",
     sentry_dsn="https://testdsn@localhost/1",
 )

docs/integrations/litestar.md

@@ -1,25 +1,25 @@
 # Usage with `Litestar`
 
-*Another example of usage with LiteStar - [litestar-sqlalchemy-template](https://github.com/modern-python/litestar-sqlalchemy-template)*
+*Another example of usage with Litestar - [litestar-sqlalchemy-template](https://github.com/modern-python/litestar-sqlalchemy-template)*
 
 ## 1. Install `lite-bootstrap[litestar-all]`:
 
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[litestar-all]
+      uv add "lite-bootstrap[litestar-all]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[litestar-all]
+      pip install "lite-bootstrap[litestar-all]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[litestar-all]
+      poetry add "lite-bootstrap[litestar-all]"
       ```
 
 Read more about available extras [here](../introduction/installation.md).
@@ -122,8 +122,8 @@ LitestarConfig(
 
 ## Request body size limit
 
-`LitestarBootstrapper` builds its app with `Litestar.from_config()`, which —
-unlike `Litestar(...)` — passes every `AppConfig` field explicitly and so
+`LitestarBootstrapper` builds its app with `Litestar.from_config()`, which,
+unlike `Litestar(...)`, passes every `AppConfig` field explicitly and so
 skips the 10 MB `request_max_body_size` default that `Litestar(...)` applies.
 Left as-is, that means every handler that reads a request body returns `500:
 'request_max_body_size' set to 'Empty' on all layers`

docs/introduction/configuration.md

@@ -25,8 +25,8 @@ Additional parameters can also be supplied through the settings object:
 
 Read more about sentry_sdk params [here](https://docs.sentry.io/platforms/python/configuration/options/).
 
-Sentry is the second most expensive instrument in the stack, and the settings that actually move
-the number are not the ones most people reach for. See [Performance](performance.md).
+Sentry is the second most expensive instrument in the stack. Its cost comes almost entirely from the ASGI
+integration; see [Performance](performance.md).
 
 ### Sentry logging integration
 
@@ -52,9 +52,8 @@ Under either, `sentry_logging_breadcrumb_level` is ignored and lite-bootstrap wa
 
 Prometheus is the cheapest of the three non-logging instruments; see [Performance](performance.md).
 
-To bootstrap Prometheus, you must provide at least:
-
-- `prometheus_metrics_path`.
+Prometheus is on by default when its extra is installed, serving metrics at `prometheus_metrics_path`
+(default: `/metrics`). Set `prometheus_metrics_path` to an empty string to disable it.
 
 Additional parameters:
 
@@ -103,6 +102,7 @@ To bootstrap Opentelemetry, you must provide at least one of:
 
 - `opentelemetry_endpoint`, for traces.
 - `opentelemetry_metrics_endpoint`, for metrics.
+- `opentelemetry_log_traces=True`, to log spans to stdout.
 
 Additional parameters:
 
@@ -111,7 +111,7 @@ Additional parameters:
 - `opentelemetry_endpoint` - will be passed to `OTLPSpanExporter` as endpoint. Under `opentelemetry_exporter_protocol="http"` this is a full URL (e.g. `http://collector:4318/v1/traces`).
 - `opentelemetry_namespace` - will be passed to the `Resource`.
 - `opentelemetry_exporter_protocol` - OTLP exporter transport: `"grpc"` (default, needs the `otl` extra) or `"http"` (needs the `otl-http` extra, no `grpcio` - installable on free-threaded Python).
-- `opentelemetry_insecure` - whether the gRPC OTLP connection is insecure (gRPC only; for `http` the endpoint URL scheme carries security).
+- `opentelemetry_insecure` - whether the gRPC OTLP connection is insecure (default: `True`; gRPC only; for `http` the endpoint URL scheme carries security). While it is `True`, an endpoint pointing at a non-local host triggers a warning that telemetry is sent unencrypted.
 - `opentelemetry_instrumentors` - a list of extra instrumentors.
 - `opentelemetry_log_traces` - traces will be logged to stdout.
 - `opentelemetry_sampler` - an `opentelemetry.sdk.trace.sampling.Sampler` deciding which traces are recorded. Unset, the SDK's own default applies: `parentbased_always_on`, which records every trace that is not the child of a non-recording remote parent, unless `OTEL_TRACES_SAMPLER` / `OTEL_TRACES_SAMPLER_ARG` say otherwise.
@@ -266,7 +266,7 @@ async def handler(request: Request) -> dict[str, str]:
 Additional parameters for Litestar's access-log middleware:
 
 - `litestar_logging_middleware_enabled` - turn on request/response access logging (default: `False`).
-- `litestar_logging_middleware_config` - a caller-supplied `LoggingMiddlewareConfig` that replaces the built-in defaults wholesale.
+- `litestar_logging_middleware_config` - a caller-supplied `LoggingMiddlewareConfig` that replaces the built-in defaults wholesale. It is ignored, with a warning, unless `litestar_logging_middleware_enabled` is `True`.
 
 See [the Litestar integration guide](../integrations/litestar.md#logging) for what gets logged and why access logging defaults to off.
 
@@ -283,8 +283,7 @@ it defaults to off.
 
 The per-MCP-message access log is **off by default**:
 
-- `fastmcp_logging_middleware_enabled` - turn on the access log (default: `False`). Replaces
-  `logging_turn_off_middleware`, which has been removed.
+- `fastmcp_logging_middleware_enabled` - turn on the access log (default: `False`).
 
 See [the FastMCP integration guide](../integrations/fastmcp.md#logging) for what gets logged.
 
@@ -329,11 +328,11 @@ To bootstrap swagger, you have the following parameters:
 - `swagger_path`
 - `swagger_offline_docs` - option to turn on offline docs.
 
-For Litestar `swagger_path` is required to bootstrap swagger instrument.
+Swagger is on by default at `swagger_path` (default: `/docs`). For Litestar, set `swagger_path` to an empty string to disable it.
 
 ## Health checks
 
-To bootstrap Health checks, you must provide set `health_checks_enabled` to True.
+Health checks are on by default; set `health_checks_enabled=False` to disable them.
 
 Additional params:
 

docs/introduction/installation.md

@@ -26,17 +26,17 @@ For example, if you want to bootstrap litestar with structlog and opentelemetry
 === "uv"
 
       ```bash
-      uv add lite-bootstrap[litestar-logging,litestar-otl]
+      uv add "lite-bootstrap[litestar-logging,litestar-otl]"
       ```
 
 === "pip"
 
       ```bash
-      pip install lite-bootstrap[litestar-logging,litestar-otl]
+      pip install "lite-bootstrap[litestar-logging,litestar-otl]"
       ```
 
 === "poetry"
 
       ```bash
-      poetry add lite-bootstrap[litestar-logging,litestar-otl]
+      poetry add "lite-bootstrap[litestar-logging,litestar-otl]"
       ```