Function config you can git blame

Timeouts, CORS, memory, log level: a script's runtime settings are magic comments at the top of its own file. They deploy when the file deploys, diff when the file diffs, and git blame answers who set the 30-second timeout and when.

They're also an API. One endpoint reads a script's parsed comments; an update endpoint rewrites them; a bulk-update sweeps a change across many scripts at once: raise every timeout for the migration, then sweep them back down.

Function config usually lives in a console, where it drifts quietly away from the repo until an incident finds the difference.

The config is in the file, and the file has an API.