[waleedlatif1]

Summary

• Run extension navigation and composer acceptance in parallel, keeping each fixture lifecycle together and preserving access coverage.
• Bootstrap composer with its own real session and fixtures; preserve every existing behavior callback, screenshot and assertion.
• Retain complete/native entry points and verify all three CI groups through real Git/Turbo attribution.

Type of Change

• Performance improvement

Testing

• Root bun run test, lint, type-check, all audits, artifact generators and block-registry check.
• All 27 existing behavior callback bodies have identical normalized ASTs; graph attribution failed before the split and passes afterward.
• Fresh composer E2E: 10 passed, one existing live-provider skip, 15 screenshots and zero browser errors. Navigation/access require the hosted PR acceptance jobs.
• actionlint, ShellCheck, Bash syntax, cleanup and test-audit.
• Splitting fixtures intentionally adds one cleanup result. Hosted timings will establish the actual wall-time effect.

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.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Ignored	Preview	Nov 3, 2026 11:04pm 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.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; the latest documentation change matches the implemented split.

Summary

Splits browser extension acceptance into navigation, composer, and access jobs.

• Extension checks now run in separate navigation, composer, and access jobs.

No new actionable issues or repository-rule violations were found.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Task["ci:e2e-browser-extension"] --> Navigation["Navigation job"]
  Task --> Composer["Composer job"]
  Task --> Access["Access job"]
  Navigation --> N["Own app, database, browser profile, and report"]
  Composer --> C["Own app, database, browser profile, and report"]
  Access --> A["Own app, database, browser profile, and report"]

Loading

_{Reviews (2) · Last reviewed commit: "docs(ci): describe the three extension a..." · Reviewed by Greptile}

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[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 5 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}