The de, es, and pt-BR concepts/event-matching.mdx pages predate the SHA-3432 _bN start-time bucket documentation (added to en 2026-05-21). They still show the old nba_celtics_lakers_20260208 no-dash/no-bucket ID format and have no bucket section at all.
Because of that, PR #268 (Fixes #265) added the new cross-bucket grouping recipe (the _g{N} doubleheader suffix + two-level matchup grouping) to en only — there was no coherent place to attach it in the stale translations.
Backfill needed for de/es/pt-BR event-matching.mdx:
- The
### Start-time bucket suffix (\_b{N}`)` section (bucket table, ET-anchoring for US sports / UTC otherwise, why-it-exists, cross-book limitation note).
- The
### Doubleheader suffix (\_g{N}`)+### Grouping one matchup across IDssections fromen`.
- Fix the stale
20260208 code-example IDs to the dashed+bucket form (2026-02-08_b3).
Surfaced by the Crisp c8594804 audit (verdicts: Mlaz-code/sharp-api-go#885).
Type: docs
The
de,es, andpt-BRconcepts/event-matching.mdxpages predate the SHA-3432_bNstart-time bucket documentation (added toen2026-05-21). They still show the oldnba_celtics_lakers_20260208no-dash/no-bucket ID format and have no bucket section at all.Because of that, PR #268 (Fixes #265) added the new cross-bucket grouping recipe (the
_g{N}doubleheader suffix + two-level matchup grouping) toenonly — there was no coherent place to attach it in the stale translations.Backfill needed for de/es/pt-BR
event-matching.mdx:### Start-time bucket suffix (\_b{N}`)` section (bucket table, ET-anchoring for US sports / UTC otherwise, why-it-exists, cross-book limitation note).### Doubleheader suffix (\_g{N}`)+### Grouping one matchup across IDssections fromen`.20260208code-example IDs to the dashed+bucket form (2026-02-08_b3).Surfaced by the Crisp c8594804 audit (verdicts: Mlaz-code/sharp-api-go#885).
Type: docs