[subnetmarco]

Summary

First of three stacked PRs for volcano deploy. The only behavior changes are the durable hint text in local mode and the manifest name in durable messages.

• export the deploy steps so one command can run them in sequence: DeployAll for functions and durable functions, Deploy for frontends and variables, DeployManifest for config, ApplyAll for migrations
• function and durable deploys take an explicit manifest path instead of always reading the default one. Messages name the manifest they read: the path the caller passed, or volcano-config.yaml when the default lookup found it
• ApplyAll trims the database and refuses an empty one, like migration up
• envfile exports ResolvePath and ErrNotFound, so a caller can tell a missing default env file from other failures
• durable hints use CommandPath, so local volcano functions deploy names volcano durable deploy instead of the cloud command
• the exported entry points document that their writers are required

Stack:

1. this PR
2. local frontends
3. volcano deploy

Verification

• make lint
• go test ./...: the durable hint test covers both the cloud and the local tree
• the local-mode E2E asserts the local volcano durable deploy --all hint

[Copilot]

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

[subnetmarco]

The extraction is clean. I found no behavior change, and the new DeployAll tests cover the named-manifest path for both function kinds.

One mismatch with the description: the bullet "durable hints use CommandPath" isn't in this diff. functions deploy -f still hardcodes volcano cloud durable deploy -f, and so does the hint in excludeDurable. Both switch to CommandPath in #298. Either move that hunk here or drop the bullet, so the squash message matches what lands.

[swkeever]

Approving. The extraction preserves behavior for the existing commands. The only user-visible change is the local durable hint naming volcano durable deploy, which exists in the local tree. #297 and #298 only add to these entry points.

Nits inline, none blocking. One without a line to anchor: the exported entry points (functions.DeployAll, durable.DeployAll, frontends.Deploy, variables.Deploy, config.DeployManifest) panic on the first print if a caller leaves Out or ErrOut nil. The only caller today sets both; defaulting them or documenting that both are required would protect the next one.