mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
vercel[bot]
57dce98fe4
The run-limit guidance added here hangs off `/worlds/vercel#per-run-limits`, and the skill sends agents to `node_modules/workflow/docs/`. But `docs/content/worlds/` is a sibling of `docs/content/docs/`, so `packages/workflow`'s prepack never copied it: every `/worlds/...` link in the bundled pages was a dead end for an agent, including the hub this guidance points at. Copy `worlds/v5` into `docs/worlds/` and list it in the skill's documentation-structure map. Two claims contradicted pages this PR already touches: - `child-workflows.mdx` opened by calling a 500-child spawn practical, while its own Tips and its "chunked spawning" section say to start them in chunks of 10-50. Point the bullet at that section. - `whats-new.mdx` said the event ceiling can be tuned "as a fallback", but `runtime-tuning.mdx` states that `WORKFLOW_MAX_EVENTS` does not override the Vercel World's service-owned value. Scope the claim to the Worlds where it is true. Guard: assert prepack copies the worlds tree and the skill lists it, and extend the anchor check to same-page `(#anchor)` jumps. Both fail when the change is reverted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Pranay Prakash <1797812+pranaygp@users.noreply.github.com> Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>