# Sharding and Reporting

Two valid CI profiles are documented for team adoption.

## A) POV profile (current simple setup)

- reporter: `html` + `github`
- no sharding
- good for bootstrapping and initial module coverage

## B) Target profile (Notion strategy)

- reporter: `blob` + `github`
- test sharding across workers
- merge reports after shards complete
- publish merged HTML report artifact

## When to move from A to B

- regression runtime grows beyond acceptable threshold
- parallelization is needed for merge/deploy gates
- team is ready to operate shard-based debugging flow

## Recommended shard flow

1. run shards (`--shard=i/n`) with blob reporter
2. collect shard artifacts
3. merge reports
4. publish merged HTML report

## Practical guidance

- keep retries conservative
- prefer fixing instability over masking it
- keep artifact retention and naming predictable