Documentation needed for .continue/configs directory support

[continue]

Summary

PR #11935 introduced support for .continue/configs/ as a third directory (alongside .continue/agents/ and .continue/assistants/) for loading local config profiles. However, this feature is not documented.

Feature Details

• YAML files placed in .continue/configs/ (workspace or global) are now automatically discovered, watched, and loaded as local profiles
• This provides a way to organize multiple config profiles in a directory rather than using a single config.yaml file
• The feature works at both workspace level (<workspace>/.continue/configs/) and global level (~/.continue/configs/)

Documentation Gap

The following documentation files need to be updated to reflect this new capability:

1. docs/customize/deep-dives/configuration.mdx - This is the main configuration documentation and should explain the .continue/configs/ directory option
2. docs/guides/understanding-configs.mdx - Should mention this as an option for organizing local configs
3. docs/guides/configuring-models-rules-tools.mdx - The 'Organization' section lists directories for models, rules, and tools but should also mention configs
4. docs/reference.mdx - May benefit from a note about profile organization options

Suggested Documentation

The docs should explain:

• That .continue/configs/ is now supported alongside .continue/agents/ and .continue/assistants/
• How to create config profiles in this directory
• That files are automatically discovered, watched, and loaded
• The difference between using ~/.continue/config.yaml vs ~/.continue/configs/ directory

Related PR

• PR feat: add .continue/configs support #11935: feat: add .continue/configs support