Resilient Browser Automation v1.0.0

Resilient Browser Automation v1.0.0

v1.0.0 is the first stable portfolio release of a production-style C# browser
automation worker focused on recovery, idempotency, and inspectable failure
evidence rather than a single happy-path script.

What it proves

• Chromium automation through Playwright for .NET 10 with isolated browser
  contexts and stable semantic locators.
• Exactly-once observable results per jobId, SQLite uniqueness, and a
  checkpoint committed only after page items are durable.
• Resume after a real page-3 failure without replaying pages 1-2.
• Classified transient recovery for HTTP 503 plus Retry-After, bounded
  exponential backoff, jitter, and finite timeout budgets.
• Graceful cancellation, bounded concurrency, per-target rate limiting,
  structured logs, and OpenTelemetry metrics.
• Redacted terminal evidence containing JSON metadata, HTML, screenshot, and a
  Playwright trace.

Reproduce it

Requirements: Docker Desktop or another Docker Engine with Compose.

git clone https://github.com/bockuden/resilient-browser-automation.git
cd resilient-browser-automation
git checkout v1.0.0
.\eng\demo-compose.ps1

The demo uses the exact released image
ghcr.io/bockuden/resilient-automation-test-stand:1.1.3; it does not build or
import Python source from this repository.

Verified release pair

• Tagged C# release commit: 01854c8.
• Test Stand release: 1.1.3.
• Test Stand image digest:
  sha256:39d0b70a874b8cf2f9ba9be6c8743530953e22c1c9d2775445341aecd2cf2bcd.
• Release CI: dotnet-fast and browser-e2e passed.
• Local full Compose proof: 9 completed jobs, 1 expected cancelled job, 1
  expected failed job with artifacts, and 117 persisted catalog items.

The reusable failure sandbox is maintained independently in
bockuden/resilient-automation-test-stand.
The exact version history is recorded in the
compatibility matrix.

Known boundaries

This project demonstrates single-process worker architecture. It intentionally
does not claim distributed scheduling, anti-bot evasion, CAPTCHA solving,
proxy rotation, or production-scale crawling. See
limitations
and
security.