Update terminology from "standardization" to "governance" for API validation features

[Copilot]

Goal

Rebrand "standardization" to "governance" across documentation and tool descriptions while ensuring LLM agents recognize both terms as equivalent.

Design

Documentation-only changes. Code identifiers (variable names, function names, API endpoints, schemas) remain unchanged for backward compatibility. Added explicit notes that both terms refer to the same feature to aid LLM comprehension.

Changeset

• Tool descriptions (src/swagger/client/tools.ts): Updated titles and summaries

  • "Scan API Standardization" → "Scan API Governance"
  • "Standardize API" → "Apply API Governance Rules"
  • Added clarification notes: "Governance was previously called 'standardization'"

• Documentation (docs/products/SmartBear MCP Server/swagger-studio-integration.md): Updated all references to use "governance" with "(formerly standardization)" notation

• README.md: Updated Studio feature description to "governance (formerly standardization)"

• CHANGELOG.md: Updated unreleased entries to reflect new terminology with migration note

Testing

All 533 tests pass. Build and lint clean. CodeQL found no issues.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• scarf.sh
  • Triggering command: /usr/local/bin/node node ./report.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

standardization jest teraz marketingowo nazwane governance; czy masz jakis pomysl zeby dodac do opisu dla agenta llm zeby rozumial oba slowa? podobnie w readme i dokumentacji

SUMMARY

TITLE: Update terminology from "Standardization" to "Governance" across documentation

USER INTENT: The user wants to update documentation to reflect that "standardization" is now marketed as "governance" and needs to ensure the LLM agent understands both terms as synonymous.

TASK DESCRIPTION:
Update documentation to use "governance" as the primary term while maintaining backward compatibility with "standardization." The goal is to:

• Reflect the new marketing terminology ("governance")
• Ensure the LLM agent recognizes both terms as equivalent
• Update README and other documentation consistently
• Maintain clarity for users who may know the feature by either name

EXISTING:

• Current documentation uses "standardization" as the primary term
• The feature exists and is functional under the "standardization" name
• There is existing documentation in README and other files that references standardization

PENDING:

• Add clarification to agent descriptions/prompts that "governance" and "standardization" are equivalent terms
• Update README to use "governance" as the primary term with a note that it was previously called "standardization"
• Update other documentation files to reflect the new terminology
• Ensure the LLM agent's system prompts or context includes understanding of both terms

CODE STATE:

• No specific files or code snippets were provided in the conversation
• Documentation files to be modified: README.md and potentially other documentation files
• Agent description/prompt files need updates (specific paths not mentioned)

RELEVANT CODE/DOCUMENTATION SNIPPETS:
None provided in the conversation.

OTHER NOTES:

• This is primarily a documentation/terminology update rather than a functional code change
• The rebranding from "standardization" to "governance" is for marketing purposes
• Both terms should be recognized to avoid confusion for existing users and to help the LLM understand queries using either terminology
• Consider adding a parenthetical note like "Governance (formerly Standardization)" in key documentation sections
• For LLM agent prompts, could add context like: "Note: Governance and standardization refer to the same feature"

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.