✨ Show experimental APIs on the API docs

[taras]

Motivation

Closes #1200.

We're adding experimental APIs in 4.1, but we don't currently have a way to show experimental APIs on the website.

Approach

1. useDenoDoc includes experimental flag which is added for symbols that are exported from ./experimental package export
2. added a route that shows experimental symbols at `/api/${s.name}/experimental/:symbol``
3. list pages now takes groups of symbols to show which includes experimental and default export
4. showing a banner on experimental routes

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/effection@1205

commit: c0766ef

[codspeed-hq]

Merging this PR will improve performance by 11.32%

⚡ 1 improved benchmark
✅ 5 untouched benchmarks

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Memory	effection-inline.recursion	3.7 KB	3.3 KB	+11.32%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing tm/1200-experimental-badge (c0766ef) with v4 (4f400d0)}

[cowboyd]

One thing I noticed is that it is using the JSR name for the endpoint "@effection/effection/experimental"

But for consumers from NPM, and honestly, consumers from JSR that use an import map to map @effection/effection -> effection will see this in code as `import { createApi } from "effection/experimental"

[taras]

Good catch — fixed in c0766ef. The experimental banner now reads effection/experimental (the npm name / import-map form) instead of the JSR-scoped @effection/effection/experimental, matching what consumers actually write in an import.