[vercel-gh-bot-3]

• Daemon service bindings now supported. Stale: "service fields such as framework, runtime, buildCommand, and bindings fail validation on a daemon." Correction: bindings removed from the rejected list; added a bindings row to the configuration table, a short bindings note, and bindings to the Build Output API descriptor fields. Source: https://vercel.com/docs/daemons/config-reference (last_updated 2018-10-20 per page frontmatter; changelog published 2026-10-30): "| bindings | ServiceBinding[] | No |" and "Vercel rejects any other field, including service fields such as framework, runtime, and buildCommand." Also https://vercel.com/changelog/vercel-daemons-can-now-call-services-with-bindings: "Bindings point one way: services can't bind to daemons." Build Output API: https://vercel.com/docs/build-output-api/daemons lists "bindings?: ServiceBinding[];". Shipped code agrees: packages/cli/src/util/validate-config.ts daemonConfigSchema has bindings; CLI CHANGELOG 65.0.0: "Accept service bindings on daemons in vercel.json." (hence the "Vercel CLI 65.0.0+" note).
• Liveness checks are a new daemon feature the skill did not mention. Stale: "restarts instances that exit or crash". Correction: instances are also restarted when they fail their livenessProbe. Added a livenessProbe row (defaults from the reference), a health-check note (SIGKILL, backoff), and livenessProbe to the Build Output API descriptor fields. Pitfall 1 now says only the daemon's own livenessProbe checks, which run from inside the instance, reach a port it listens on. Source: https://vercel.com/docs/daemons (last_updated 2018-10-20 per frontmatter; changelog https://vercel.com/changelog/add-liveness-checks-to-your-daemons published 2026-10-30): "restarts instances that exit, crash, or fail their [health checks]", "Liveness-triggered restarts send SIGKILL immediately and do not honor", and "Checks run from inside the instance"; config reference: "Consecutive failures before Vercel restarts the container." Shipped code: daemonConfigSchema.livenessProbe in packages/cli/src/util/validate-config.ts; DaemonOutput.livenessProbe in packages/build-utils/src/daemons.ts, which packages/container/src/index.ts copies into .vc-config.json; CLI CHANGELOG 65.2.0: "Support livenessProbe in vercel.json#daemons." (hence "Vercel CLI 65.2.0+"; vercel@latest is 65.9.0).

Verification
run_plugin_checks: build, typecheck, validate, and test all passed (1279 pass, 0 fail).

Test updates
None.

Not changed

• root "Must stay inside the project": matches the config reference, but CLI CHANGELOG 64.6.0 says a daemon root "can now point above the project root directory, such as ../.. in a monorepo, when the files are in the build". Left as documented; flagged as possible docs lag.
• The limits page still lists "Service bindings and rewrites" as unsupported, meaning daemons cannot be the target of a binding; the skill's matching line is still correct.
• https://vercel.com/docs/build-output-api/daemons DaemonDescriptor omits livenessProbe, which the shipped builder writes; docs lag source.

Opened automatically by the vercel-plugin drift agent. Review before merge.