docs(durable): align local execution guidance

[tkkhq]

Tracking

• Related: feat(durable): run durable functions in local mode #219
• Related: https://github.com/Kong/volcano-hosting/pull/1207
• Supersedes: feat(durable): restore CLI command group #205

Why

• the CLI runs durable functions locally, while its public docs still say durable execution is cloud-only and refused by the local server
• the durable overview says executions run for hours, while the platform execution timeout is 366 days

Summary

• document volcano durable as the local counterpart to volcano cloud durable
• document immediate local waits and the LOCAL_DURABLE_REAL_TIME override
• use the public HOBBY and SUPERAGENT plan names in CLI documentation
• align the execution-duration wording with the 366-day platform limit

Verification

• git diff --check origin/main...HEAD
• shared Volcano documentation linter passed against docs/

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[shawnwu-kong]

[P2] Clarify that top-level resource commands do not fall back to cloud

In docs/README.md:56–58, the updated paragraph includes volcano durable … in the claim that commands use the local environment when running and otherwise use the cloud project. However, NewResourceCommands wires durable commands through withLocalConfig in internal/cmd/local/local.go, which always loads local server metadata. If the local container is absent or stopped, FetchInfo returns ErrLocalNotRunning; there is no cloud fallback. A user following this guidance to run volcano durable list against their cloud project would get an error instead.

Please state that top-level resource commands target local development and that cloud operations require the explicit volcano cloud … prefix.

[shawnwu-kong]

approve with a p2

[tkkhq]

Fixed in b0dce7c. The overview now states that top-level resource commands always target local development and require the explicit volcano cloud … prefix for cloud operations; the same stale active-context wording was also removed from docs/functions.md.