Which Optional Extensions Should Stay Outside the Default Template?

[FMCalisto]

The source template now covers the baseline repository surface well, but there are still optional capabilities that may be useful only in some organizations or repository types.

This discussion is intended to identify which extensions should stay outside the default template so that the baseline remains broad, reusable, and low-friction. Examples may include stack-specific workflows, stricter compliance automation, or extra community management features.

A useful outcome would be a short list of optional add-ons that teams can adopt deliberately rather than receiving them by default.