{"entries":[{"lastCommit":{"author":{"email":"github@dubien.org","name":"Nicolas DUBIEN","when":"2026-04-28T23:37:17.000000+02:00"},"committer":{"email":"noreply@github.com","name":"GitHub","when":"2026-04-28T21:37:17.000000Z"},"hash":"e9a4c4858f906c66213098d845c9b853780ada7e","message":"📝 Add index pages for documentation sections (#6845)\n\n## Description\n\nAdds a landing/index page to every documentation category that\npreviously had none, using the same `index.md` + ``\npattern that the `tutorials/` section already uses. Each new page\ncarries a specific cross-cutting insight (arbitraries pipeline,\ncanonical shrink targets, two-level configuration model, …) instead of\nrephrasing its children — `` handles the child listing\nautomatically.\n\nThe `migration/` category has only one guide today; rather than adding a\nboilerplate landing page, its `_category_.json` is re-pointed directly\nat `from-3.x-to-4.x` so clicking the sidebar category opens the guide.\n\n**New files (10):**\n- `website/docs/introduction/index.md`\n- `website/docs/core-blocks/index.md`\n- `website/docs/core-blocks/arbitraries/index.md`\n- `website/docs/core-blocks/arbitraries/primitives/index.md`\n- `website/docs/core-blocks/arbitraries/composites/index.md`\n- `website/docs/core-blocks/arbitraries/combiners/index.md`\n- `website/docs/core-blocks/arbitraries/fake-data/index.md`\n- `website/docs/configuration/index.md`\n- `website/docs/advanced/index.md`\n- `website/docs/tutorials/quick-start/index.md`\n\n**Modified (1):**\n- `website/docs/migration/_category_.json` — added `link: { type: \"doc\",\nid: \"migration/from-3.x-to-4.x\" }`\n\nVerified locally with `pnpm exec docusaurus build`: every new URL\nrenders with breadcrumb, H1, prose, and the child `DocCardList` cards.\nNo broken links or slug conflicts.\n\n## Checklist\n\n— _Don't delete this checklist and make sure you do the following before\nopening the PR_\n\n- [x] I have a full understanding of every line in this PR — whether the\ncode was hand-written, AI-generated, copied from external sources or\nproduced by any other tool\n- [x] I flagged the impact of my change (minor / patch / major) either\nby running `pnpm run bump` or by following the instructions from the\nchangeset bot\n- [x] I kept this PR focused on a single concern and did not bundle\nunrelated changes\n- [x] I followed the [gitmoji](https://gitmoji.dev/) specification for\nthe name of the PR, including the package scope (e.g. `🐛(vitest)\nSomething...`) when the change targets a package other than `fast-check`\n- [x] I added relevant tests and they would have failed without my PR\n(when applicable)\n\n\n\n---------\n\nCo-authored-by: Claude ","tree":"a0511ac5563cf17792b203950a280b5cdba9fb30"},"mode":"0100644","name":"_category_.json","size":109},{"lastCommit":{"author":{"email":"github@dubien.org","name":"Nicolas DUBIEN","when":"2026-08-18T22:41:53.000000+02:00"},"committer":{"email":"noreply@github.com","name":"GitHub","when":"2026-08-18T20:41:53.000000Z"},"hash":"148b3acd55bf122a77989b8af38f98141a73583e","message":"📝 Fix admonition titles on the website (#7226)\n\n## Description\n\n> AI-agent disclosure: this PR was authored by an automated\n> agent (Claude Code) and has not been\n> line-by-line reviewed by a human before submission.\n\n\n\nFrom an end-user point of view: every admonition carrying a title was\nrendered as raw text on the website. Instead of the expected coloured\n`tip`/`info`/`warning`/`note` box, readers were served literal `:::tip\nTest your custom toString` … `:::` paragraphs, with the title glued to\nthe first sentence of the body. This PR restores the boxes on all of\nthem — 106 admonitions across 43 pages of the docs and the blog.\n\nRoot cause: `future.v4: true` in `website/docusaurus.config.ts` turns\noff the MDX v1 compatibility layer, whose preprocessor\n(`admonitionTitleToDirectiveLabel`) used to rewrite `:::tip Title` into\n`:::tip[Title]` before parsing. Without that rewrite, `remark-directive`\nrefuses the block entirely — any trailing text after the directive name\ninvalidates the opening line — so the whole admonition falls back to\nplain markdown. This was verified against the installed\n`remark-directive@3.0.1`: `:::info Some Title` parses to a `paragraph`,\n`:::info[Some Title]` parses to a `containerDirective` carrying a\n`directiveLabel`.\n\nThe fix migrates the markdown to the directive label syntax that\nDocusaurus documents today, rather than re-enabling\n`mdx1Compat.admonitions`. Opting into `future.v4` looks deliberate, and\nthe compat layer is going away in Docusaurus v4 anyway — turning it back\non would only defer the same migration, on top of being a naive regexp\npass that also rewrites `:::note Title` occurrences inside code blocks.\nUntitled admonitions are unaffected and were left untouched.\n\n\n\nImpact level: none on the published packages — the change is confined to\n`website/`, so no `pnpm run bump` / changeset applies. The PR is limited\nto that single concern.\n\nThe migration was applied by script with code-fence tracking, so\n`:::`-looking lines inside code samples could not be rewritten (there\nwere none). Blockquote and indentation prefixes are preserved.\n\nNo tests were added: the repository has no rendering test for the\nwebsite markdown, and the failure lives in Docusaurus' own MDX pipeline.\nVerification was done instead by re-parsing all 121 markdown/MDX files\nunder `website/` with the very `remark-parse` + `remark-directive`\nversions the site resolves — 113 container directives, 106 of them with\na label, and zero remaining text nodes containing `:::`. Before the\nchange, those same 106 blocks parsed as paragraphs. `prettier --check`\npasses on all website markdown.\n\n## Checklist\n\n— _Don't delete this checklist and make sure you do the following before\nopening the PR_\n\n- [ ] I have a full understanding of every line in this PR — whether the\ncode was hand-written, AI-generated, copied from external sources or\nproduced by any other tool\n- [ ] I flagged the impact of my change (minor / patch / major) either\nby running `pnpm run bump` or by following the instructions from the\nchangeset bot\n- [ ] I kept this PR focused on a single concern and did not bundle\nunrelated changes\n- [ ] I followed the [gitmoji](https://gitmoji.dev/) specification for\nthe name of the PR, including the package scope (e.g. `🐛(vitest)\nSomething...`) when the change targets a package other than `fast-check`\n- [ ] I added relevant tests and they would have failed without my PR\n(when applicable)\n\n\n\n\n---------\n\nCo-authored-by: Claude \nCo-authored-by: Claude Opus 5 ","tree":"39af94e8ad7d3cf53541b4f309a4450c95798c51"},"mode":"0100644","name":"from-3.x-to-4.x.md","size":22718}],"lastCommit":{"author":{"email":"github@dubien.org","name":"Nicolas DUBIEN","when":"2026-08-18T22:41:53.000000+02:00"},"committer":{"email":"noreply@github.com","name":"GitHub","when":"2026-08-18T20:41:53.000000Z"},"hash":"148b3acd55bf122a77989b8af38f98141a73583e","message":"📝 Fix admonition titles on the website (#7226)\n\n## Description\n\n> AI-agent disclosure: this PR was authored by an automated\n> agent (Claude Code) and has not been\n> line-by-line reviewed by a human before submission.\n\n\n\nFrom an end-user point of view: every admonition carrying a title was\nrendered as raw text on the website. Instead of the expected coloured\n`tip`/`info`/`warning`/`note` box, readers were served literal `:::tip\nTest your custom toString` … `:::` paragraphs, with the title glued to\nthe first sentence of the body. This PR restores the boxes on all of\nthem — 106 admonitions across 43 pages of the docs and the blog.\n\nRoot cause: `future.v4: true` in `website/docusaurus.config.ts` turns\noff the MDX v1 compatibility layer, whose preprocessor\n(`admonitionTitleToDirectiveLabel`) used to rewrite `:::tip Title` into\n`:::tip[Title]` before parsing. Without that rewrite, `remark-directive`\nrefuses the block entirely — any trailing text after the directive name\ninvalidates the opening line — so the whole admonition falls back to\nplain markdown. This was verified against the installed\n`remark-directive@3.0.1`: `:::info Some Title` parses to a `paragraph`,\n`:::info[Some Title]` parses to a `containerDirective` carrying a\n`directiveLabel`.\n\nThe fix migrates the markdown to the directive label syntax that\nDocusaurus documents today, rather than re-enabling\n`mdx1Compat.admonitions`. Opting into `future.v4` looks deliberate, and\nthe compat layer is going away in Docusaurus v4 anyway — turning it back\non would only defer the same migration, on top of being a naive regexp\npass that also rewrites `:::note Title` occurrences inside code blocks.\nUntitled admonitions are unaffected and were left untouched.\n\n\n\nImpact level: none on the published packages — the change is confined to\n`website/`, so no `pnpm run bump` / changeset applies. The PR is limited\nto that single concern.\n\nThe migration was applied by script with code-fence tracking, so\n`:::`-looking lines inside code samples could not be rewritten (there\nwere none). Blockquote and indentation prefixes are preserved.\n\nNo tests were added: the repository has no rendering test for the\nwebsite markdown, and the failure lives in Docusaurus' own MDX pipeline.\nVerification was done instead by re-parsing all 121 markdown/MDX files\nunder `website/` with the very `remark-parse` + `remark-directive`\nversions the site resolves — 113 container directives, 106 of them with\na label, and zero remaining text nodes containing `:::`. Before the\nchange, those same 106 blocks parsed as paragraphs. `prettier --check`\npasses on all website markdown.\n\n## Checklist\n\n— _Don't delete this checklist and make sure you do the following before\nopening the PR_\n\n- [ ] I have a full understanding of every line in this PR — whether the\ncode was hand-written, AI-generated, copied from external sources or\nproduced by any other tool\n- [ ] I flagged the impact of my change (minor / patch / major) either\nby running `pnpm run bump` or by following the instructions from the\nchangeset bot\n- [ ] I kept this PR focused on a single concern and did not bundle\nunrelated changes\n- [ ] I followed the [gitmoji](https://gitmoji.dev/) specification for\nthe name of the PR, including the package scope (e.g. `🐛(vitest)\nSomething...`) when the change targets a package other than `fast-check`\n- [ ] I added relevant tests and they would have failed without my PR\n(when applicable)\n\n\n\n\n---------\n\nCo-authored-by: Claude \nCo-authored-by: Claude Opus 5 ","tree":"39af94e8ad7d3cf53541b4f309a4450c95798c51"}}