[swkeever]

Why

#170 stopped the docs sync with a snapshot of volcano-hosting docs/public at d23abe5. One hosting PR changed docs/public after that: Kong/volcano-hosting#3396 (PATCH /lavaflow/settings accepts the dashboard session). This ports it so it isn't lost when Kong/volcano-hosting#3404 deletes docs/public.

What changed

• content/platform/api-reference/errors.md, content/platform/authentication/security/project-access-tokens.md, and content/platform/guides/lavaflow.md now match volcano-hosting 2dc8049.
• The CLI and SDK sections already match their repos' main; the CLI change from feat(databases): apply migrations in tracked runs volcano-cli#365 (b46711de) was already in feat(docs): author all docs here and stop syncing from product repos #170.

Testing

• pnpm lint:docs content and pnpm check:links: pass.

🤖 Generated with Claude Code

[Copilot]

🔵 Needs a closer look

The referenced hosting PR returns 404, preventing verification that dashboard sessions support owner-only LavaFlow settings updates and that this behavior is released to production.

No open issues 🎉

What changed in this PR

Ports the LavaFlow settings documentation update missed by #170’s final sync snapshot, preserving it as documentation ownership moves to this repository.

Changes:

• Documents live Volcano dashboard sign-ins as accepted credentials for owner-only LavaFlow settings changes.
• Updates related run-start conditions, project-token restrictions, and error guidance consistently.

File	Description
content/​platform/​guides/​lavaflow.md	Adds dashboard sign-in support to settings, run-start, and merging guidance.
content/​platform/​authentication/​security/​project-access-tokens.md	Clarifies owner credentials while preserving project-token restrictions.
content/​platform/​api-reference/​errors.md	Updates LavaFlow permission-error guidance to include dashboard sign-ins.

_{Review effort: Balanced}

[github-actions]

AI review: no P0-P2 findings

Reviewed 570f4aa. Run log

This is a docs-only change. It ports Kong/volcano-hosting#3396 so the LavaFlow settings guide, the errors page, and the project access token page say that a live Volcano dashboard sign-in can change LavaFlow settings, including the settings that need a person (merging, ungated workflows, turning LavaFlow on). The risk is low. One restated passage still lists only the old credentials.

⚪ P3

• content/platform/guides/lavaflow.md:2790 "Turn Code Quality on" still lists only volcano login and expiring platform tokens

Not checked: The AI review read the diff, the code, and the PR's text; it ran no tests or builds and read nothing outside this repository.

• That volcano-hosting 2dc8049 accepts a live dashboard session on PATCH /lavaflow/settings in every case these docs now describe (ungated workflows, merging, code_quality, turning on).
• Whether the person_required error text quoted in errors.md ("changes the rest with a platform token") still matches what the server returns after Kong/volcano-hosting#3396.
• Verify that the deployed Kong/volcano-hosting API supports the documented dashboard sign-ins for settings changes and runs triggered by enabling LavaFlow.

Human review: not needed