[waleedlatif1]

Summary

• Run Blacksmith mobile and docs WebKit acceptance through a matching, digest-pinned browser container. Keep the app, fixtures, native modules and harness on the host.
• Preserve Chromium and GitHub fallback, all existing checks and report paths, and owned cleanup on failures and cancellation.

Type of Change

• Improvement

Testing

Three paired runs preserved 1,164 check results (including 24 existing unavailable results) and 774 host screenshots. Docs jobs saved 68–71 seconds per pair; the parallel mobile group's slowest job improved in all three pairs. Individual shard timings vary. Cold and warm image pulls, native AMD64 identity, failure traces, endpoint rejection and ownership/cancellation cleanup were verified.

Full root test (727 fresh script cases, fresh app and CLI suites, all 20 workspace tasks); lint; 29 workspace type checks; all 62 audits; actionlint; ShellCheck; cleanup and test-audit review.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 4, 2026 1:27am UTC

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 7 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Blacksmith mobile and docs WebKit jobs now use a digest-pinned browser container. The app, fixtures, and test scripts stay on the host.

• Blacksmith mobile and docs WebKit tests use a pinned browser container.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Acceptance job] --> B{Blacksmith WebKit?}
  B -->|Yes| C[Start pinned browser container]
  C --> D[Host test script connects over loopback]
  B -->|No| E[Install and launch native browser]
  D --> F[Host app and fixtures]
  E --> F
  D --> G[Host reports and screenshots]
  C --> H[Check ownership and stop container]

Loading

_{Reviews (1) · Last reviewed commit: "improvement(ci): run WebKit acceptance i..." · Reviewed by Greptile}