[NathanFlurry]

Automated docs sync from rivet-dev/rivet@a1c18da.

Do not edit vendor/integrations/ here. Edit the docs in rivet-dev/rivet and this PR updates itself.

[railway-app]

🚅 Deployed to the website-pr-120 environment in rivet-website

Service	Status	Web	Updated
website	😴 Sleeping (View Logs)	Web	Oct 6, 2026 at 9:43 pm UTC

[the-company-company]

🟠 1 medium-severity finding

_{Reviewed commit 54958c7.}

[the-company-company]

🟠 Medium · Keep the Actors-only snippet out of the integrations bundle

No page in vendor/integrations/docs/content references this snippet, while the current base already ships the identical file under vendor/actors/ and references it from the Actors performance-monitoring page. This update therefore adds only a dead duplicate and causes the integrations sync to churn whenever an unrelated Actors example changes. Scope the integrations sync's extra paths to snippets referenced by docs/integrations (or otherwise omit this Actors-only file) in the upstream sync configuration.

[the-company-company]

🟠 1 medium-severity finding

_{Reviewed commit 642c7a3.}

[the-company-company]

🟠 Medium · Keep unrelated Actors files out of the integrations sync

The refreshed diff still contains no integration page that references this snippet; the current base ships the identical file under vendor/actors/, where the performance-monitoring page uses it. The accompanying examples/docs/package.json version change is likewise unrelated to the integration bundle's referenced snippets. Both changes are churn from copying the repository-wide examples/docs tree into every bundle rather than integration content. Scope this sync's extra paths to files referenced by docs/integrations (or otherwise omit these Actors-only updates) in the upstream configuration.

[the-company-company]

🟠 1 medium-severity finding

_{Reviewed commit dd250d1.}

[the-company-company]

🟠 Medium · Keep unrelated Actors files out of the integrations sync

The rebased diff still has no integration page that references this snippet; the current base ships the identical file under vendor/actors/, where the Actors performance-monitoring page uses it. The accompanying examples/docs/package.json version change is also unrelated to any integration page. These changes are churn from copying the repository-wide examples/docs tree into every bundle. Scope the integrations sync's extra paths to files referenced by docs/integrations (or otherwise omit these Actors-only updates) in the upstream configuration.