[docs] Update documentation for strict mode network validation features from 2026-02-13

[github-actions]

Documentation Updates - 2026-02-13

This PR updates the documentation based on features merged in the last 24 hours.

Features Documented

1. Strict mode ecosystem validation for all engines (from Enforce strict mode network domain validation for all engines #15409)

   • Strict mode now applies network domain validation to ALL engines, including codex
   • Previously only engines without LLM gateway support enforced known ecosystem domains
   • Updated to clarify this unified policy across all engines

2. Helpful error messages for ecosystem suggestions (from Add ecosystem identifier suggestions to strict mode network validation errors #15424)

   • When strict mode rejects individual ecosystem domains (e.g., pypi.org), error messages now suggest the appropriate ecosystem identifier (e.g., python)
   • Added examples of the new error message format
   • Documented the "Did you mean" suggestion feature

Changes Made

• docs/src/content/docs/reference/network.md:

  • Added new "Strict Mode Validation" section explaining ecosystem identifier requirements
  • Documented that strict mode applies to all engines (not just those without LLM gateway support)
  • Added examples of helpful error messages with ecosystem suggestions
  • Included examples showing rejected vs. accepted configurations

• docs/src/content/docs/guides/network-configuration.md:

  • Added new "Strict Mode and Ecosystem Identifiers" section in the guide
  • Provided practical examples of rejected and accepted configurations
  • Added example of the new error message format with suggestions
  • Updated "Security Best Practices" to include keeping strict mode enabled

• docs/src/content/docs/reference/frontmatter.md:

  • Updated strict mode enforcement areas to include ecosystem identifier requirement
  • Added note about helpful error messages with ecosystem suggestions
  • Added cross-reference to the new Network Permissions strict mode validation section
  • Clarified that this validation applies to all engines

Merged PRs Referenced

• Enforce strict mode network domain validation for all engines #15409 - Enforce strict mode network domain validation for all engines
• Add ecosystem identifier suggestions to strict mode network validation errors #15424 - Add ecosystem identifier suggestions to strict mode network validation errors
• [WIP] Update terminology from discussions to issues #15421 - Update terminology from discussions to issues (already reflected in docs)
• Add Community Feedback link to documentation footer #15423 - Add Community Feedback link to documentation footer (UI change only)

Notes

The documentation now clearly explains:

• Strict mode network validation applies to ALL engines uniformly
• Individual ecosystem domains are rejected in strict mode with helpful suggestions
• Custom domains (not part of known ecosystems) are still allowed in strict mode
• Error messages provide "Did you mean" suggestions mapping domains to ecosystems
• Users can disable strict mode for development/testing if needed

🤖 Generated with [Claude Code]((claude.com/redacted)

AI generated by Daily Documentation Updater

• expires on Feb 14, 2026, 3:13 PM UTC

[pelikhan]

@copilot custom domains are always refused in strict mode

[Copilot]

@pelikhan I've opened a new pull request, #15431, to work on those changes. Once the pull request is ready, I'll request review from you.