Fix processingTime semantics, schema caching, and restarts

.actor/actor.json

@@ -3,7 +3,7 @@
   "name": "webhook-debugger-logger",
   "title": "Webhook Debugger, Logger & API Mocking Suite",
   "description": "Enterprise-grade tool to test, debug, and mock webhooks. Features real-time SSE streaming, request replay, HTTP forwarding, and JSON schema validation. Perfect for Stripe, GitHub, and Shopify integrations.",
-  "version": "3.0.4",
+  "version": "3.0.5",
   "output": "./output_schema.json",
   "input": "./input_schema.json",
   "webServerSchema": "./web_server_schema.json",

.actor/dataset_schema.json

@@ -104,8 +104,8 @@
       },
       "processingTime": {
         "type": "integer",
-        "title": "Latency (ms)",
-        "description": "Time taken to process the request",
+        "title": "Processing Time (ms)",
+        "description": "Time taken to process the request before any simulated response delay is applied",
         "example": 5
       },
       "remoteIp": {
@@ -224,7 +224,7 @@
             "label": "Size (Bytes)"
           },
           "processingTime": {
-            "label": "Latency (ms)"
+            "label": "Processing Time (ms)"
           },
           "remoteIp": {
             "label": "Source IP"

.actor/output_schema.json

@@ -38,7 +38,13 @@
         "desc": true
       },
       "display": {
-        "component": "table"
+        "component": "table",
+        "properties": {
+          "processingTime": {
+            "label": "Processing Time (ms)",
+            "format": "number"
+          }
+        }
       }
     },
     "details": {

.actor/web_server_schema.json

@@ -3,7 +3,7 @@
   "info": {
     "title": "Webhook Debugger & Logger API",
     "description": "OpenAPI description for the Webhook Debugger & Logger Actor web server. Authentication is configuration-driven: when authKey is configured, management routes require either a bearer token or the key query parameter; when authKey is unset, those routes remain accessible without credentials.",
-    "version": "3.0.4"
+    "version": "3.0.5"
   },
   "servers": [
     {
@@ -80,7 +80,7 @@
                 "schema": {
                   "type": "string"
                 },
-                "example": "Webhook Debugger & Logger (v3.0.4)\nActive Webhooks: 1\nSignature Verification: STRIPE"
+                "example": "Webhook Debugger & Logger (v3.0.5)\nActive Webhooks: 1\nSignature Verification: STRIPE"
               }
             }
           },
@@ -1137,7 +1137,8 @@
             "type": "integer"
           },
           "processingTime": {
-            "type": "integer"
+            "type": "integer",
+            "description": "Server-side processing time in milliseconds before any configured responseDelayMs simulation is applied"
           },
           "requestId": {
             "type": "string"

.claude/rules/testing.md

@@ -54,11 +54,13 @@ const wait = (ms) => new Promise((r) => setTimeout(r, ms));
 ### shared-mocks.js
 
 - `apifyMock`, `axiosMock`, `dnsPromisesMock`, `ssrfMock` - Pre-configured mocks
+- `apifyMock` includes both `Actor.on(...)` and `Actor.off(...)` support for lifecycle-oriented harness teardown
 - `createDatasetMock(items, { autoRegister })` - Dataset with getData/pushData/getInfo
 - `createKeyValueStoreMock(overrides)` - KV store mock
 - `createMockWebhookManager(overrides)` - WebhookManager mock
 - `setupBasicApifyMock(mockInstance, options)` - Configure apifyMock
 - `resetNetworkMocks()` - Reset SSRF, DNS, Axios to defaults
+- `fsPromisesMock` - Shared `node:fs/promises` mock surface, including `mkdtemp()` for temp-dir based harness setup
 - `loggerMock` - Shared logger mock for assertions
 
 ### test-utils.js
@@ -77,7 +79,7 @@ const wait = (ms) => new Promise((r) => setTimeout(r, ms));
 ### Other Helpers
 
 - `middleware-test-utils.js`: `createMiddlewareTestContext()`, `runMiddlewareWithTimers()`
-- `app-utils.js`: `setupTestApp()` - Initialize app + supertest for integration tests
+- `app-utils.js`: `setupTestApp()` - Initialize app + supertest for integration tests; teardown also removes transient Actor listeners and process signal handlers registered during boot
 - `db-hooks.js`: `resetDb()` - Clear DuckDB logs table
 - `signature-utils.js`: `createStripeSignature()`, `createShopifySignature()`, `createGitHubSignature()`, `createSlackSignature()`
 
@@ -231,13 +233,17 @@ let appClient, teardownApp;
 beforeAll(async () => {
   ({ appClient, teardownApp } = await setupTestApp());
 });
-afterAll(() => teardownApp());
+afterAll(async () => {
+  await teardownApp();
+});
 
 test("GET /health", async () => {
   expect((await appClient.get("/health")).status).toBe(200);
 });
 ```
 
+Use the harness teardown instead of manually removing process or Actor listeners inside individual integration suites.
+
 ### Dataset Mocking
 
 ```javascript

.github/workflows/link-check.yml

@@ -103,7 +103,11 @@ jobs:
 
             try {
               const { origin, pathname } = new URL(value);
-              return `${origin}${pathname}`;
+              const normalizedPathname =
+                pathname !== '/' && pathname.endsWith('/')
+                  ? pathname.slice(0, -1)
+                  : pathname;
+              return `${origin}${normalizedPathname}`;
             } catch {
               return null;
             }
@@ -114,6 +118,9 @@ jobs:
             'https://www.npmjs.com/package/webhook-debugger-logger',
             'https://www.npmjs.com/package/isolated-vm?activeTab=readme',
             'https://img.shields.io/coderabbit/prs/github/ar27111994/webhook-debugger-logger?utm_source=oss&utm_medium=github&utm_campaign=ar27111994%2Fwebhook-debugger-logger&labelColor=171717&color=FF570A&link=https%3A%2F%2Fcoderabbit.ai&label=CodeRabbit+Reviews',
+            'https://www.patreon.com/cw/ar27111994',
+            'https://liberapay.com/ar27111994',
+            'https://thanks.dev/d/gh/ar27111994',
           ];
           const softHandledUrlKeys = new Set(
             softHandledUrls.map((value) => normalizeUrlKey(value)).filter(Boolean),

.gitignore

@@ -12,3 +12,4 @@ coverage/
 !.github/coverage/
 !.github/coverage/*.json
 .tsbuildinfo
+*.tmp*

.lycheeignore

@@ -26,5 +26,6 @@
 ^(?:http://)169\.254\.169\.254/latest(?:/|$)
 ^(?:http://)(?:empty\.domain|nonexistent\.domain)(?:/|$)
 ^(?:http://)(?:weird-dns|string-throw)\.com(?:/|$)
+^(?:http://)metadata\.cloud(?:/|$)
 ^(?:https://)xn--unicode-domain\.com(?:/|$)
 ^(?:https://)google\.com/foo(?:/|$)

CHANGELOG.md

@@ -3,6 +3,19 @@
 All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.0.5] - 2026-04-21
+
+### Fixed (3.0.5)
+
+- **Latency Metrics**: Make `processingTime` consistently represent server-side processing time only, excluding any configured `responseDelayMs` simulation from persisted log data.
+- **Performance**: Cache compiled JSON Schema validators so repeated requests and stable hot-reload configurations do not trigger unnecessary recompilation on the webhook path.
+- **Lifecycle**: Reset webhook-manager singleton state during test teardown and recreate the sync-service limiter after shutdown so repeated initialize/stop/start flows remain stable.
+- **Shutdown Ordering**: Drain the HTTP listener before stopping `SyncService` and closing DuckDB so in-flight requests and readiness probes do not race read-model teardown.
+- **DuckDB Lifecycle**: Drain both pooled and in-use DuckDB connections before resetting the singleton so repeated DB teardown and rebuild flows do not leave stale handles behind.
+- **DuckDB Reset Coordination**: Keep the reset gate for new DuckDB callers while allowing already-queued writes and transactions to drain first, preventing reset deadlocks in the serialized write path.
+- **Contracts & Docs**: Align dataset, output, OpenAPI, README, architecture, and API reference documentation with the finalized `processingTime` semantics and response-delay behavior.
+- **Tests**: Add regression coverage for latency semantics, validator-cache reuse and memoized schema cache keys, DuckDB reset coordination with active reads plus queued write/transaction drain paths, malformed JSON sanitation persistence, restart-safe integration harness cleanup, shutdown-only sync error suppression, and spawned-process close-path resilience.
+
 ## [3.0.4] - 2026-04-18
 
 ### Fixed (3.0.4)