chronos-ruby 0.2.0.pre.1 → 0.4.0.pre.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8d204c1595d7029ae32a43aacacdcc561bdc0b264e52a77e8eceb9acd4fa397d
-  data.tar.gz: 99696fa1feee48e384c3563473d1c77786fb2e0c54e261a41cf6778c0ce2468c
+  metadata.gz: 1ab10ffdc0cff4274241465904b18e4bceb4fa230ea9fddb4b8be419c08e3463
+  data.tar.gz: 2d6d778012088192efed14e0ab64958716c8a6b4c3e697127c52573dc4dcd47b
 SHA512:
-  metadata.gz: 50ba51c92e8436616b1fe56b012d3c9ede3f8e1ec0d50df9a778f9790b876e3bd781c97cf42bac50b08d320e3ab07d8f675dbcdd746f6884d268fc222fc15d52
-  data.tar.gz: 480f16b60ba6162552ffca1f120c6a36d31b5debf639d99060ffda4a052b68d86d68f58849033b227582cf4cd6feac0ade70fe5e0d4e5fcac18148ca463b84bc
+  metadata.gz: a8bb789313b2b7d360b6a8c08e5b5cf731aa1325912be7b560a1869b3d8717e4e779610e92591c1a2c436f5d14cd39e28f1e5db837d954def1db232788284d2d
+  data.tar.gz: 93a311d6905d83dee031a88cb5887854a32e60d26eceb0dc0446a8244c77a2c9fa763089bc5ec5fa25d265cb5881c3775dafe6361b1e84a1c6044aa89df220ee

data/CHANGELOG.md

@@ -11,6 +11,54 @@ All notable changes are documented here. The project follows Semantic Versioning
 - legacy CI now resolves Bundler 1.17.3 through `Gem.bin_path` on RubyGems versions that do not support the `_version_` executable selector.
 - documentation verification now reads source and Markdown files explicitly as UTF-8 on legacy container locales.
 
+## [0.4.0.pre.1] - 2026-07-20
+
+### Added
+
+- Rack-protocol middleware for automatic exception capture with propagation of the original failure;
+- request context for method, normalized route, status, duration, request ID, optional user agent, host, path, controller/action, approximate response size, user, and sanitized parameters;
+- selectable context-store port with a thread-local legacy adapter and guaranteed scope cleanup;
+- bounded circular breadcrumbs for custom, log, request, query, external HTTP, cache, and job categories;
+- public `Chronos.with_context` and `Chronos.add_breadcrumb` APIs;
+- Rack context contract, concurrency tests, module documentation, ADR, executable example, and request-overhead benchmark.
+
+### Changed
+
+- manual notifications now inherit the current execution context and breadcrumbs;
+- version advanced to `0.4.0.pre.1`.
+
+### Known limitations
+
+- generic route normalization cannot identify every application-specific dynamic segment;
+- thread-local context does not propagate into application-created threads or fibers;
+- deferred exceptions raised only while enumerating a streaming response body are not captured;
+- Rails-specific installation and route discovery remain planned for version 0.5.
+
+## [0.3.0.pre.1] - 2026-07-20
+
+### Added
+
+- explicit delivery-state counters for accepted, queued, serialized, sent, retried, dropped, and rejected events;
+- finite exponential retry with bounded jitter and `Retry-After` support;
+- retry classification for network errors, HTTP 408, 429, and 5xx responses;
+- closed, open, and half-open circuit breaker states;
+- fixed-capacity in-memory backlog restricted to sanitized serialized events;
+- bounded remote configuration for sampling, event types, payload limits, exact fingerprint ignores, send interval, and kill switch;
+- resilience contracts, unit tests, module documentation, ADR, executable example, and outage benchmark.
+
+### Changed
+
+- asynchronous and synchronous delivery now pass through `DeliveryPipeline`;
+- `WorkerPool` delegates delivery policy instead of sending directly through a transport;
+- version advanced to `0.3.0.pre.1`.
+
+### Known limitations
+
+- backlog is not persisted and is lost when the process exits;
+- backlog draining requires later delivery activity;
+- no dedicated remote-configuration polling endpoint;
+- no automatic Rack, Rails, or job integration.
+
 ## [0.2.0.pre.1] - 2026-07-19
 
 ### Added

data/README.md

@@ -1,16 +1,18 @@
 # Chronos Ruby
 
-Chronos Ruby is the framework-independent client for sending Ruby application errors to Chronos. Version 0.2 is the privacy-focused legacy foundation: it captures exceptions manually, sanitizes sensitive data, builds a bounded JSON event, and delivers it synchronously or through a fixed-size asynchronous queue.
+Chronos Ruby is the framework-independent client for sending Ruby application errors to Chronos. Version 0.4 adds automatic Rack exception capture, isolated request context, and bounded breadcrumbs to the privacy and resilience foundations from earlier releases.
 
 ## What the gem collects
 
-For each exception, version 0.2 can collect:
+For each exception, version 0.4 can collect:
 
 - exception class, message, structured backtrace, and chained causes;
 - timestamp, severity, tags, and an optional fingerprint;
 - application-supplied context, parameters, session, and user fields;
 - Ruby version, engine, platform, process ID, opaque thread ID, and hostname;
 - application version, environment, and service name.
+- Rack method, normalized route, status, duration, request ID, host, query-free path, optional user agent, controller/action, response size, trace ID, and already-parsed parameters when the middleware is used;
+- bounded breadcrumbs explicitly supplied by the application or integration.
 
 See [Data collected](docs/data-collected.md) for the complete field table.
 
@@ -20,7 +22,7 @@ Chronos Ruby does not inspect environment variables, request bodies, cookies, HT
 
 ## Supported Ruby and Rails versions
 
-Version 0.x targets Ruby 2.2.10 through Ruby 2.6. Version 0.2 is independent of Rails and does not yet declare support for any Rails integration. All supported combinations must pass dedicated CI before being listed as supported.
+Version 0.x targets Ruby 2.2.10 through Ruby 2.6. Version 0.4 implements the Rack protocol but does not yet declare Rails support. All supported combinations must pass dedicated CI before being listed as supported.
 
 See [Compatibility](docs/compatibility.md).
 
@@ -29,7 +31,7 @@ See [Compatibility](docs/compatibility.md).
 The current public build is a pre-release. Add its exact version to the application's `Gemfile`:
 
 ```ruby
-gem "chronos-ruby", "0.2.0.pre.1"
+gem "chronos-ruby", "0.4.0.pre.1"
 ```
 
 Install with a Bundler version compatible with the application. For the oldest supported runtime:
@@ -47,7 +49,7 @@ gem install chronos-ruby --pre
 
 ## Rails installation
 
-Rails automatic integration is not part of version 0.2. A Rails application may use the plain Ruby API, but this does not constitute declared Rails support. Rack and Rails adapters are planned for later legacy releases.
+Rails automatic installation is not part of version 0.4. A Rails application may install the Rack middleware manually, but this does not constitute declared Rails support. Railtie and generator support are planned for version 0.5.
 
 ## Minimum configuration
 
@@ -70,7 +72,14 @@ HTTPS verification is enabled by default. HTTP requires explicitly setting `ssl_
 
 ## Automatic capture
 
-Automatic exception capture is not implemented in version 0.2. Applications must call `Chronos.notify` or `Chronos.notify_sync`. Rack, Rails, and worker hooks will be introduced only after their compatibility suites exist.
+Rack applications can capture unhandled exceptions automatically and preserve the application error semantics:
+
+```ruby
+use Chronos::Integrations::Rack::Middleware,
+    :include_user_agent => false
+```
+
+The middleware notifies asynchronously and re-raises the same exception. It never reads the request body, raw query string, cookies, authorization headers, or response body. See [Rack integration and context](docs/modules/rack-context.md).
 
 ## Manual capture
 
@@ -101,15 +110,25 @@ User data is opt-in and must contain only values your application is allowed to
 Chronos.notify(error, :user => {"id" => "customer-42", "role" => "operator"})
 ```
 
-Version 0.2 sanitizes this context before delivery. Data minimization remains the application's responsibility.
+Version 0.4 sanitizes this context before delivery and before it can enter retry storage. Data minimization remains the application's responsibility.
 
 ## Breadcrumbs
 
-Breadcrumbs are not implemented in version 0.2.
+Breadcrumbs use a fixed circular buffer scoped to the current execution:
+
+```ruby
+Chronos.add_breadcrumb(
+  :category => "custom",
+  :message => "payment started",
+  :metadata => {"provider" => "example"}
+)
+```
+
+No log, SQL, HTTP, cache, job, request body, or response body payload is collected automatically. Unknown categories become `custom`, and metadata is bounded and sanitized before queueing.
 
 ## Filters and LGPD
 
-Version 0.2 recursively redacts sensitive keys and detects Bearer tokens, JWTs, e-mail addresses, CPF, CNPJ, and valid payment-card candidates in free text. IPv4 addresses are anonymized by default. Applications can add blocklist matchers, hash selected identifiers, or install custom filters:
+Version 0.4 recursively redacts sensitive keys and detects Bearer tokens, JWTs, e-mail addresses, CPF, CNPJ, and valid payment-card candidates in free text. IPv4 addresses are anonymized by default. Applications can add blocklist matchers, hash selected identifiers, or install custom filters:
 
 ```ruby
 Chronos.configure do |config|
@@ -133,19 +152,19 @@ Chronos.configure do |config|
 end
 ```
 
-Exception-specific ignore rules are not available in version 0.2.
+Local exception-specific ignore callbacks are not available in version 0.4. The server may provide a bounded list of exact fingerprints to ignore; it cannot provide regular expressions or executable rules.
 
 ## Performance monitoring
 
-Request, SQL, cache, job, and external HTTP monitoring are not implemented in version 0.2. The local capture pipeline is bounded and HTTP delivery runs outside the caller thread when `Chronos.notify` is used.
+Request timing events, SQL, cache, job, and external HTTP monitoring are not implemented in version 0.4. Rack exception context is bounded, and HTTP delivery runs outside the caller thread when `Chronos.notify` is used.
 
 ## Sidekiq and Active Job
 
-Sidekiq and Active Job integrations are not implemented in version 0.2. Calling the manual API from a job is possible, but automatic capture and deduplication are not yet guaranteed.
+Sidekiq and Active Job integrations are not implemented in version 0.4. Calling the manual API from a job is possible, but automatic capture and deduplication are not yet guaranteed.
 
 ## Deploy tracking
 
-Deploy notifications are not implemented in version 0.2. `app_version` may be included in exception events for release correlation.
+Deploy notifications are not implemented in version 0.4. `app_version` may be included in exception events for release correlation.
 
 ## Asynchronous queue
 
@@ -156,16 +175,23 @@ flowchart LR
   E[Exception] --> N[Notice builder]
   N --> P[Privacy sanitizer]
   P --> S[Safe bounded serializer]
-  S --> Q[Bounded queue]
+  S --> D[Delivery pipeline]
+  D --> Q[Bounded queue]
   Q --> W[Fixed worker pool]
-  W --> H[Net::HTTP transport]
+  W --> R[Retry and circuit breaker]
+  R --> H[Net::HTTP transport]
+  R --> B[Bounded memory backlog]
 ```
 
 Use `Chronos.flush(timeout)` to wait for accepted events and `Chronos.close(timeout)` during shutdown. Workers are recreated after a process fork.
 
 ## Retry and backlog
 
-Version 0.2 classifies network failures, `429`, `4xx`, and `5xx`, but does not retry or persist events. Failed deliveries are dropped after the attempt. Bounded retry and backlog are planned for version 0.3.
+The resilience layer introduced in version 0.3 retries network errors, HTTP `408`, `429`, and `5xx` responses with exponential backoff, bounded jitter, and a finite attempt count. Other `4xx` responses are permanent and are not retried. A circuit breaker pauses requests after repeated failures, preventing retry storms.
+
+After retries are exhausted, the already sanitized `SerializedEvent` may enter a fixed-capacity memory backlog. The backlog drops new items when full, is lost when the process exits, and never writes to disk. A later successful half-open probe drains backlog items as new events arrive.
+
+The SaaS may return a JSON policy in the bounded `X-Chronos-Remote-Configuration` response header. Only sampling rate, enabled event types, a lower payload limit, exact ignored fingerprints, send interval, and kill switch are accepted. Remote values cannot change the host, project credentials, TLS, local maximums, code, or regular expressions. See [Retry and backlog](docs/modules/retry-backlog.md) and [Remote configuration](docs/modules/remote-configuration.md).
 
 ## How it works internally
 
@@ -173,8 +199,10 @@ The code follows hexagonal boundaries:
 
 - `Chronos::Core` contains immutable notices, sanitization, and safe normalization;
 - `Chronos::Application` coordinates capture;
+- `Chronos::Application::DeliveryPipeline` owns bounded retry and remote policy;
 - `Chronos::Ports` defines delivery behavior;
-- `Chronos::Adapters` implements Net::HTTP delivery;
+- `Chronos::Adapters` implements Net::HTTP delivery and thread-local context;
+- `Chronos::Integrations::Rack` implements optional automatic Rack capture;
 - `Chronos::Internal` owns bounded queueing, workers, and defensive logging.
 
 The core has no dependency on Rails, Rack, Sidekiq, or ActiveSupport. See [Architecture](docs/architecture.md).
@@ -194,6 +222,17 @@ Chronos.configure do |config|
   config.workers = 1
   config.timeout = 5.0
   config.open_timeout = 2.0
+  config.max_retries = 3
+  config.retry_base_interval = 0.5
+  config.retry_max_interval = 30.0
+  config.retry_jitter = 0.25
+  config.backlog_size = 100
+  config.circuit_failure_threshold = 5
+  config.circuit_reset_timeout = 30.0
+  config.remote_configuration = true
+  config.context_store = :thread_local
+  config.breadcrumb_capacity = 20
+  config.breadcrumb_max_bytes = 2048
 end
 ```
 
@@ -205,20 +244,22 @@ Configuration errors are raised during `Chronos.configure`. Capture and delivery
 
 ## Benchmark
 
-Run the version 0.2 benchmarks with:
+Run the version 0.4 benchmarks with:
 
 ```bash
 bundle _1.17.3_ exec ruby benchmarks/capture_exception.rb
 bundle _1.17.3_ exec ruby benchmarks/serialization.rb
 bundle _1.17.3_ exec ruby benchmarks/filtering.rb
 bundle _1.17.3_ exec ruby benchmarks/queue.rb
+bundle _1.17.3_ exec ruby benchmarks/retry_backlog.rb
+bundle _1.17.3_ exec ruby benchmarks/request_overhead.rb
 ```
 
 Results depend on runtime, hardware, and payload. No performance comparison is claimed until repeatable measurements are published.
 
 ## Migration from Airbrake
 
-An Airbrake migration guide will be added before the legacy 1.0 release. Version 0.2 does not claim API compatibility or automatic replacement.
+An Airbrake migration guide will be added before the legacy 1.0 release. Version 0.4 does not claim API compatibility or automatic replacement.
 
 ## Local development
 

data/contracts/rack-context-v1.schema.json

@@ -0,0 +1,43 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://chronos.example/schemas/rack-context-v1.schema.json",
+  "title": "Chronos Rack exception context v1",
+  "type": "object",
+  "additionalProperties": true,
+  "required": ["request", "trace_id", "breadcrumbs"],
+  "properties": {
+    "trace_id": {"type": "string", "minLength": 1},
+    "request": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["method", "route", "status", "duration_ms", "request_id", "host", "path"],
+      "properties": {
+        "method": {"type": "string"},
+        "route": {"type": "string"},
+        "status": {"type": "integer"},
+        "duration_ms": {"type": "number", "minimum": 0},
+        "request_id": {"type": ["string", "null"]},
+        "user_agent": {"type": ["string", "null"]},
+        "host": {"type": "string"},
+        "path": {"type": "string"},
+        "controller": {"type": ["string", "null"]},
+        "action": {"type": ["string", "null"]},
+        "response_size": {"type": ["integer", "null"], "minimum": 0}
+      }
+    },
+    "breadcrumbs": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["category", "message", "metadata", "timestamp"],
+        "properties": {
+          "category": {"enum": ["custom", "log", "request", "query", "external_http", "cache", "job"]},
+          "message": {"type": "string"},
+          "metadata": {"type": "object"},
+          "timestamp": {"type": "string"}
+        }
+      }
+    }
+  }
+}

data/docs/adr/ADR-005-sanitize-before-backlog.md

@@ -2,7 +2,7 @@
 
 ## Status
 
-Accepted for version 0.2; no backlog exists yet.
+Accepted and implemented in version 0.3.
 
 ## Context
 
@@ -10,7 +10,7 @@ Persisting unsanitized events would increase privacy and credential exposure ris
 
 ## Decision
 
-`PayloadSerializer` must run `Sanitizer` before `SafeSerializer`, queueing, transport, or any future retry and persistent backlog. Raw notices remain transient in process memory and never enter delivery storage.
+`PayloadSerializer` must run `Sanitizer` before `SafeSerializer`, queueing, transport, retry, or backlog. `MemoryBacklog` accepts only `SerializedEvent`. Raw notices remain transient in process memory and never enter delivery storage.
 
 ## Alternatives
 

data/docs/adr/ADR-011-bounded-resilience-and-remote-control.md

@@ -0,0 +1,27 @@
+# ADR-011 — Bounded resilience and restricted remote control
+
+## Status
+
+Accepted for version 0.3.
+
+## Context
+
+Chronos must tolerate prolonged SaaS outages in legacy applications without unbounded memory, unlimited retries, extra per-event threads, unsanitized storage, or a remote-control channel capable of changing security boundaries.
+
+## Decision
+
+Place retry orchestration in `DeliveryPipeline`. Use finite exponential backoff with bounded positive jitter, a simple closed/open/half-open circuit breaker, and a fixed-capacity in-memory backlog that accepts only sanitized `SerializedEvent` values. Do not persist events to disk in version 0.3.
+
+Accept remote policy only from a size-limited JSON response header after successful authenticated event delivery. Apply a fixed scalar allowlist and local upper bounds. Reject executable content, remote regular expressions, host, credentials, TLS, and capacity changes.
+
+## Alternatives
+
+Retry inside `NetHttpTransport` was rejected because transport classification and delivery policy would become coupled. An unbounded queue was rejected because endpoint availability would control host memory. Immediate disk persistence was rejected because permissions, rotation, expiry, checksums, corruption, and privacy need an independent design. Arbitrary remote JSON or code callbacks were rejected as an unsafe control plane.
+
+## Positive consequences
+
+Outage memory remains bounded, retry storms are contained, transport stays replaceable, privacy precedes backlog, and remote operators can reduce or stop later collection without changing endpoint security.
+
+## Negative consequences
+
+Memory backlog is lost on restart and drains only when later delivery activity occurs. Synchronous notification may wait through retry delays. Process-local sampling is approximate. A response header limits policy size and complexity.

data/docs/adr/ADR-012-rack-context-isolation.md

@@ -0,0 +1,27 @@
+# ADR-012 — Rack capture with selectable execution context
+
+## Status
+
+Accepted for version 0.4.
+
+## Context
+
+Automatic Rack capture needs request-scoped state, but the legacy line cannot rely on modern fiber-local APIs. Loading the plain Ruby gem must not force Rack into applications that do not use it. Request and response bodies also carry disproportionate privacy and performance risk.
+
+## Decision
+
+Implement a Rack-protocol middleware without a runtime Rack dependency. Catch failures from the downstream application call, notify asynchronously, and re-raise the same exception. Never read `rack.input`, raw query strings, cookies, authorization headers, or response body enumeration. Use already-parsed parameter hashes only.
+
+Define a `ContextStore` port and use a selectable thread-local adapter by default. Restore nested scopes in `ensure`. Keep breadcrumbs in a fixed circular per-execution buffer and sanitize them with the rest of the event before queueing.
+
+## Alternatives
+
+Requiring Rack from the core was rejected because it would add dependency and resolution risk to plain Ruby legacy applications. Global or process-wide context was rejected because concurrent requests would leak data. Automatic body parsing and body proxies were deferred because they change I/O behavior and complicate streaming lifecycle ownership.
+
+## Positive consequences
+
+Plain Ruby loading remains dependency-free, concurrent request context is isolated, middleware failure semantics are preserved, and diagnostic memory is bounded.
+
+## Negative consequences
+
+Thread-local context does not propagate to application-created threads or fibers. Generic route normalization is less precise than router-specific integration. Exceptions raised only during deferred response-body enumeration are outside version 0.4 capture.

data/docs/architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-Chronos Ruby 0.2 uses hexagonal boundaries so the legacy core remains independent of frameworks and delivery infrastructure.
+Chronos Ruby 0.4 uses hexagonal boundaries so the legacy core remains independent of frameworks and delivery infrastructure.
 
 ```mermaid
 flowchart TB
@@ -8,24 +8,33 @@ flowchart TB
   Application --> Core[Core / Notice and serialization]
   Application --> Ports[Ports / Transport contract]
   Ports --> Adapter[Adapters / NetHttpTransport]
-  Application --> Internal[Internal / BoundedQueue and WorkerPool]
+  Application --> Delivery[Application / DeliveryPipeline]
+  Delivery --> Internal[Internal / BoundedQueue, WorkerPool, and MemoryBacklog]
   Internal --> Ports
+  Rack[Integrations / Rack middleware] --> Facade
+  Facade --> Context[Ports / ContextStore]
+  Context --> ThreadLocal[Adapters / ThreadLocalContextStore]
 ```
 
 ## Boundaries
 
 - Domain/Core owns immutable event values and Ruby normalization.
 - Application owns use-case ordering and failure containment.
-- Ports define behavior expected from infrastructure.
-- Adapters contain Net::HTTP and TLS behavior.
+- Ports define behavior expected from transport and execution-context infrastructure.
+- Adapters contain Net::HTTP, TLS, and thread-local context behavior.
 - Internal contains private concurrency and diagnostic mechanisms.
+- Integrations contain optional framework entry points and never enter the domain boundary.
 
 The `Chronos` module is a thin facade. Rails, Rack, ActiveSupport, Sidekiq, and job libraries must not be required by the core.
 
+## Rack capture flow
+
+The Rack middleware establishes a context-store scope, adds a bounded request breadcrumb, and calls the downstream application. An unhandled exception is enriched with request duration and status, captured through the normal notice pipeline, then re-raised unchanged. The context-store adapter restores or clears its value in `ensure`. The middleware implements the Rack protocol without requiring the Rack library.
+
 ## Capture flow
 
-An exception becomes an immutable notice. `Sanitizer` removes sensitive values before `SafeSerializer` creates a bounded JSON envelope. Asynchronous capture inserts only that sanitized serialized event into the queue. A fixed worker sends it through the transport. Synchronous capture bypasses the queue but uses the same privacy boundary.
+An exception becomes an immutable notice. `Sanitizer` removes sensitive values before `SafeSerializer` creates a bounded JSON envelope. Asynchronous capture inserts only that sanitized serialized event into the queue. A fixed worker sends it through `DeliveryPipeline`, which applies finite retry, a circuit breaker, and a fixed memory backlog. Synchronous capture bypasses the queue but uses the same privacy and resilience boundaries.
 
 ## Failure policy
 
-Explicit invalid configuration raises `Chronos::ConfigurationError`. Capture, serialization, logger, worker, TLS, network, and HTTP failures do not escape into the host application. They produce `false`, a transport result, or a bounded logger diagnostic.
+Explicit invalid configuration raises `Chronos::ConfigurationError`. Capture, serialization, logger, worker, retry, circuit, TLS, network, HTTP, and remote-policy failures do not escape into the host application. They produce `false`, a classified transport result, a bounded state transition, or a bounded logger diagnostic.

data/docs/compatibility.md

@@ -4,14 +4,14 @@ Chronos Ruby 0.x is the legacy line. Technical compatibility does not make an en
 
 | Ruby | Rails integration | Status | Evidence |
 |---|---|---|---|
-| 2.2.10 | None in 0.1 | Best effort | Local unit, contract, integration, fork, and fake-server suite |
-| 2.3.8 | None in 0.1 | Best effort | Dedicated CI job pending first successful run |
-| 2.4.10 | None in 0.1 | Best effort | Dedicated CI job pending first successful run |
-| 2.5.9 | None in 0.1 | Best effort | Dedicated CI job pending first successful run |
-| 2.6.10 | None in 0.1 | Best effort | Dedicated CI job pending first successful run |
+| 2.2.10 | Rack protocol in 0.4; no Rails | Best effort | Dedicated legacy core CI and Rack contract tests |
+| 2.3.8 | Rack protocol in 0.4; no Rails | Best effort | Dedicated legacy core CI and Rack contract tests |
+| 2.4.10 | Rack protocol in 0.4; no Rails | Best effort | Dedicated legacy core CI and Rack contract tests |
+| 2.5.9 | Rack protocol in 0.4; no Rails | Best effort | Dedicated legacy core CI and Rack contract tests |
+| 2.6.10 | Rack protocol in 0.4; no Rails | Best effort | Dedicated legacy core CI and Rack contract tests |
 | 2.7 and newer | None in 0.x | Unsupported | Belongs to transitional or modern lines |
 
-No Rails version is declared supported by version 0.2. Rails applications may call the plain Ruby API manually. Rails support requires a real example application, framework integration tests, and a successful dedicated matrix job.
+No Rails version is declared supported by version 0.4. The middleware is tested against the Rack protocol shape without adding a Rack runtime dependency. Rails support requires a real example application, Railtie integration tests, and a successful dedicated matrix job.
 
 Status meanings:
 

data/docs/configuration.md

@@ -29,6 +29,21 @@
 | `hash_keys` | Optional | `[]` | Scalar identifier keys replaced by scoped SHA-256 values |
 | `filters` | Optional | `[]` | Callable application-specific privacy filters |
 | `anonymize_ip` | Recommended | `true` | Replaces the final octet of supplied IPv4 addresses |
+| `max_retries` | Optional | `3` | Maximum retry attempts after the first delivery failure |
+| `retry_base_interval` | Optional | `0.5` | Initial exponential-backoff delay in seconds |
+| `retry_max_interval` | Optional | `30.0` | Maximum local or `Retry-After` delay in seconds |
+| `retry_jitter` | Optional | `0.25` | Random positive jitter fraction between `0.0` and `1.0` |
+| `backlog_size` | Optional | `100` | Maximum sanitized events retained in memory after delivery failure; `0` disables retention |
+| `circuit_failure_threshold` | Optional | `5` | Consecutive retryable failures before opening the circuit |
+| `circuit_reset_timeout` | Optional | `30.0` | Seconds before one half-open delivery probe |
+| `remote_configuration` | Optional | `true` | Accepts only the documented bounded remote policy fields |
+| `remote_config_max_bytes` | Optional | `4096` | Maximum remote policy response-header bytes |
+| `sampling_rate` | Optional | `1.0` | Local upper bound for exception sampling |
+| `enabled_event_types` | Optional | `["exception"]` | Local event-type allowlist; only exception exists in version 0.4 |
+| `max_remote_send_interval` | Optional | `60.0` | Local upper bound for remotely requested send spacing |
+| `context_store` | Optional | `:thread_local` | `:thread_local` or an object implementing `get`, `set`, `clear`, and `with_context` |
+| `breadcrumb_capacity` | Optional | `20` | Positive count of newest breadcrumbs retained per execution |
+| `breadcrumb_max_bytes` | Optional | `2048` | Maximum bytes per normalized breadcrumb; minimum `128` |
 
 ```ruby
 Chronos.configure do |config|
@@ -41,9 +56,16 @@ Chronos.configure do |config|
   config.workers = 1
   config.blocklist_keys += [:medical_record, /bank_account/i]
   config.hash_keys += [:customer_id]
+  config.max_retries = 3
+  config.backlog_size = 100
+  config.circuit_failure_threshold = 5
+  config.context_store = :thread_local
+  config.breadcrumb_capacity = 20
 end
 ```
 
 Privacy matcher collections and filters are copied into the immutable runtime snapshot. Matchers must be String, Symbol, or Regexp values, and every custom filter must respond to `call`.
 
 The gem never reads all environment variables automatically. The host application decides which values to pass. See [Privacy and LGPD](privacy-lgpd.md) before adding application context.
+
+Remote configuration can only reduce collection within local bounds. It cannot increase `max_payload_size` or `sampling_rate`, enable an unsupported or locally disabled event type, change the endpoint, replace credentials, disable TLS verification, or install executable matching rules.

data/docs/data-collected.md

@@ -1,6 +1,6 @@
 # Data collected
 
-Version 0.2 emits only manually submitted exception events. All fields pass through the privacy sanitizer and bounded safe serializer before delivery.
+Version 0.4 emits exception events submitted manually or captured by the optional Rack middleware. All fields pass through the privacy sanitizer and bounded safe serializer before queueing, retry storage, or delivery.
 
 | Data | Default | Source |
 |---|---|---|
@@ -15,8 +15,14 @@ Version 0.2 emits only manually submitted exception events. All fields pass thro
 | Context, parameters, session, user | Optional and sanitized | Explicit capture arguments |
 | Tags and fingerprint | Optional and sanitized | Explicit capture arguments |
 | IPv4 address in supplied text | Anonymized | Explicit capture arguments |
+| Rack method, normalized route, status, duration, request ID, host, query-free path, trace ID | Collected with Rack middleware | Rack environment and local clock |
+| Rack user agent | Disabled by default | `HTTP_USER_AGENT` when middleware option is enabled |
+| Rack controller/action | Collected when already supplied | Explicit Chronos or Action Dispatch environment values |
+| Rack parameters | Collected only when already parsed | Explicit, Rack, or Action Dispatch parameter hashes |
+| Response size | `Content-Length` when present | Rack response headers |
+| Breadcrumbs | Explicit and bounded | Application and Chronos integration |
 
-The gem never collects request bodies, response bodies, cookies, HTTP authorization headers, environment variables in bulk, source code, SQL bind values, database rows, or installed gems in version 0.2.
+The gem never collects request bodies, response bodies, raw query strings, cookies, HTTP authorization headers, environment variables in bulk, source code, SQL bind values, database rows, or installed gems in version 0.4.
 
 The secret `project_key` is an authentication header and is excluded from the JSON payload and logger diagnostics. The envelope field named `project_key` contains the public `project_id` required by the current v1 server contract.
 

data/docs/examples/plain-ruby.md

@@ -17,4 +17,10 @@ For a network-free privacy audit, run:
 bundle _1.17.3_ exec ruby examples/plain-ruby/privacy_audit.rb
 ```
 
+For a network-free outage and bounded-backlog example, run:
+
+```bash
+bundle _1.17.3_ exec ruby examples/plain-ruby/resilient_delivery.rb
+```
+
 The example builds the final event locally and demonstrates key redaction, e-mail and Bearer-token detection, application-specific blocklisting, and identifier hashing.

data/docs/modules/async-queue.md

@@ -10,8 +10,12 @@ stateDiagram-v2
   Accepted --> Queued
   Queued --> Sending
   Sending --> Sent
-  Sending --> Dropped: delivery failure in 0.1
+  Sending --> Retried: retryable failure
+  Retried --> Sending: policy permits
+  Retried --> Backlog: attempts exhausted
+  Backlog --> Sending: later recovery probe
+  Sending --> Rejected: permanent 4xx
   Accepted --> Dropped: queue full
 ```
 
-Version 0.2 has no disk persistence and no retry. Only sanitized serialized events enter the queue. Queue statistics expose current size, capacity, accepted events, and dropped events. Tests cover full queues, waiter wakeup, lazy startup, contained failures, timed shutdown, double close, flush, and fork behavior.
+Version 0.3 adds retry and a separate fixed-size memory backlog, but no disk persistence. Only sanitized serialized events enter either structure. Queue statistics expose current size, capacity, accepted events, and dropped events. Delivery diagnostics additionally expose state counters, backlog statistics, and circuit state. Tests cover full queues, waiter wakeup, lazy startup, contained failures, timed shutdown, double close, flush, fork behavior, and prolonged endpoint failure.

data/docs/modules/notice-pipeline.md

@@ -13,10 +13,11 @@ flowchart LR
   Sanitizer --> SafeSerializer
   SafeSerializer --> PayloadSerializer
   PayloadSerializer --> SerializedEvent
+  SerializedEvent --> DeliveryPipeline
 ```
 
 `Notice` is immutable. Parsers are stateless. Raw notice values exist only in process memory. The sanitizer removes sensitive keys and recognized personal data before the safe serializer accepts JSON primitives, bounds nested structures, tolerates invalid encoding, and represents unknown objects without arbitrary application serialization.
 
-Version 0.2 deliberately excludes sampling, retry, and fingerprint policy. These can be inserted after sanitization without changing transport or queue code.
+Version 0.3 passes the serialized event to `DeliveryPipeline`. The pipeline applies remote sampling and exact fingerprint policy before serialization where possible, then manages queueing, retry, circuit state, and bounded memory backlog without changing transport or queue code.
 
 Unit and contract tests verify missing backtraces, cyclic causes, invalid encoding, unsafe objects, payload limits, and the v1 envelope.

data/docs/modules/rack-context.md

@@ -0,0 +1,59 @@
+# Rack integration, execution context, and breadcrumbs
+
+Version 0.4 adds automatic capture through `Chronos::Integrations::Rack::Middleware`. The integration implements the Rack protocol directly and does not require Rack when `chronos-ruby` is loaded. Add the middleware after configuring Chronos:
+
+```ruby
+use Chronos::Integrations::Rack::Middleware,
+    :include_user_agent => false
+```
+
+## Capture behavior
+
+The middleware catches an exception raised by the downstream application, submits it asynchronously, and re-raises the same exception object. A notification or logger failure cannot replace the application failure. An `ensure` boundary clears request context in every outcome.
+
+Captured request fields are method, normalized route, status, duration in milliseconds, request ID, optional user agent, host, query-free path, controller/action when already supplied, approximate response size from `Content-Length`, a generated or supplied trace ID, already-parsed parameters, and application-supplied user context. The final event serializer sanitizes every field before queueing.
+
+The middleware never reads `rack.input`, copies `QUERY_STRING`, parses a body, enumerates a response body, or reads cookies and authorization headers. Parameters are collected only from already-materialized hashes at `rack.request.query_hash`, `action_dispatch.request.query_parameters`, `action_dispatch.request.path_parameters`, or the explicit `chronos.parameters` key. User context is opt-in through `chronos.user`.
+
+Without an explicit `chronos.route` or `action_dispatch.route_uri_pattern`, numeric and UUID path segments are replaced with `:id`. This is a conservative cardinality guard, not a complete router-aware normalizer.
+
+## Context store
+
+`Chronos::Ports::ContextStore` defines `get`, `set`, `clear`, and `with_context`. The legacy default, `Chronos::Adapters::ThreadLocalContextStore`, isolates each thread and restores nested scopes in `ensure`. It deliberately does not propagate state into newly created threads or fibers.
+
+A custom strategy can be selected at configuration time if it implements the complete port:
+
+```ruby
+Chronos.configure do |config|
+  # credentials omitted
+  config.context_store = MyContextStore.new
+end
+```
+
+Application code can add scoped values. Manual notifications issued inside the block inherit them:
+
+```ruby
+Chronos.with_context(:user => {"id" => "customer-42"}) do
+  Chronos.notify(error)
+end
+```
+
+## Breadcrumbs
+
+`Chronos.add_breadcrumb` records an explicit marker in the current execution buffer:
+
+```ruby
+Chronos.add_breadcrumb(
+  :category => "custom",
+  :message => "payment authorization started",
+  :metadata => {"provider" => "example"}
+)
+```
+
+Allowed categories are `custom`, `log`, `request`, `query`, `external_http`, `cache`, and `job`; an unknown value becomes `custom`. No log, SQL, body, cache, job, or external HTTP payload is captured automatically in 0.4. Metadata exists only when the application or a later integration explicitly supplies it.
+
+The default circular buffer keeps the newest 20 entries. Each breadcrumb is normalized to JSON primitives with bounded depth, collections, strings, nodes, and serialized bytes. The entire exception payload still passes through the privacy sanitizer before it can enter the queue or retry backlog.
+
+## Concurrency and limitations
+
+Concurrent Rack threads receive distinct user, parameter, breadcrumb, and trace values. Context does not cross threads automatically, so applications that start their own thread must establish a new scope explicitly. Version 0.4 captures exceptions raised during the initial Rack application call; deferred failures raised only while a server enumerates a streaming response body are not intercepted.