Opening this issue to track issues which are resolved by documentation changes in a single place.

#1019

This is addressed in #1913

#1502

• Needed doc change: document the caveat that setGlobalOptions() must run before function definitions are evaluated, and that with multi-file JS/ESM layouts, import order / module evaluation can prevent global options from applying as users expect.
• Why: the current 2nd gen reference still states that setGlobalOptions() “sets default options for all functions written using the 2nd gen SDK,” but the docs do not mention the multi-file / ESM import-order caveat or recommend a safe pattern. The organize/manage pages also do not describe this.
• Docs checked: 2nd gen API reference, Manage functions, Organize multiple functions

#1616

The documentation regarding the process of upgrading from v1 to v2 has been updated here to make things clearer.