fix(ms-ai-architect): Foundry URL-navnerom-migrering (ai-foundry → foundry/foundry-classic, 141 filer)

Task #5 del 1/3 (URL-migrering). Verifiseringen motbeviste STATE.md-premisset om ren prefix-swap: rebrand er per-URL, ikke mekanisk. En blind sed ai-foundry→foundry ville lagd 56 nye 404-er (classic-stiene finnes ikke under nytt foundry/-prefiks — bekreftet empirisk).

Metode: resolverte alle 237 unike KB-URLer mot live redirects (curl -L), bygde full-URL→full-URL-mapping fra faktisk url_effective. Bevarer locale-form, query (?view=) og #fragment per lenke.

- 231 navnerom-erstatninger over 141 filer (408 forekomster):
  - 161 → azure/foundry/ (98 ren prefix-swap + 10 sti-reorg + reorg-tilfeller)
  - 69 → azure/foundry-classic/ (eldre hub-spor: assistants, hub-DR, on-your-data; faktisk redirect-mål per operatorvalg)
  - 1 → azure/foundry-local/

- 2 døde lenker (404) fikset til verifiserte mål:
  - agent-service → azure/foundry/agents/overview
  - concepts/evaluation-evaluators/ → azure/foundry/how-to/evaluate-generative-ai-app

- 5 path-/display-referanser (uten https://, i backticks/lenketekst) rettet manuelt.

- 6 slug-baserte ai-foundry-treff urørt (scope-grense): managed-grafana-dashboard, security-baseline, power-platform prompt-builder, architecture baseline-chat (sistnevnte slug-rebrand i annet navnerom — mulig fremtidig funn).

- Parkert til task #5 del 2/3: Norway East GPT-5-datasuverenitet-fiks + modellkatalog-utvidelse (5.3/5.4/5.5, gpt-oss, sora-2).

Verifisert: 0 gjenværende azure/ai-foundry/-navnerom i skills/. validate-plugin.sh 219 PASS. test-kb-integrity.sh 117/117 passed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01REiKFhP4w6xGXXqWKpPCJJ

skills/ms-ai-governance/references/responsible-ai/content-safety-implementation.md

@@ -280,7 +280,7 @@ Azure AI Content Safety har PII-detection for completions:
 | **Record-keeping** | Retain logs i 6+ år (Azure Log Analytics long-term retention) |
 
 **Transparency Note:**
-Microsoft publiserer [Transparency Note for Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/content-safety/transparency-note) som dekker:
+Microsoft publiserer [Transparency Note for Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/content-safety/transparency-note) som dekker:
 - System capabilities and limitations
 - Training data og known biases
 - Best practices for deployment
@@ -464,22 +464,22 @@ Scenario: 1 million samtaler/måned, gjennomsnitt 2 meldinger per samtale = 2M t
 1. [What is Azure AI Content Safety?](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/overview)
    *Confidence: High* — Oversikt over features, pricing tiers, region availability, service limits
 
-2. [Content filtering overview (Azure OpenAI)](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/content-filter)
+2. [Content filtering overview (Azure OpenAI)](https://learn.microsoft.com/en-us/azure/foundry-classic/foundry-models/concepts/content-filter)
    *Confidence: High* — Filter categories, severity levels, scenario details for API response behavior
 
 3. [Harm categories in Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/concepts/harm-categories)
    *Confidence: High* — Detaljert beskrivelse av severity levels 0-7 per kategori (hate, sexual, violence, self-harm)
 
-4. [Data, privacy, and security for Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/content-safety/data-privacy)
+4. [Data, privacy, and security for Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/content-safety/data-privacy)
    *Confidence: High* — Data residency, encryption at rest, customer controls, GDPR compliance statements
 
 5. [Custom categories (preview)](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/concepts/custom-categories)
    *Confidence: Medium* — Preview feature, API-detaljer kan endre seg før GA
 
-6. [Transparency note: Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/content-safety/transparency-note)
+6. [Transparency note: Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/content-safety/transparency-note)
    *Confidence: High* — System capabilities, intended uses, limitations, best practices
 
-7. [Default Guidelines & controls policies (Azure OpenAI)](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/default-safety-policies)
+7. [Default Guidelines & controls policies (Azure OpenAI)](https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/default-safety-policies)
    *Confidence: High* — Default severity thresholds for text/image models, table of blocked categories
 
 8. [Azure AI Content Safety Quickstart (C# code samples)](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/quickstart-text?pivots=programming-language-csharp)
@@ -488,7 +488,7 @@ Scenario: 1 million samtaler/måned, gjennomsnitt 2 meldinger per samtale = 2M t
 9. [Mitigate false results in Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/how-to/improve-performance)
    *Confidence: High* — Best practices for severity tuning, custom categories, blocklists
 
-10. [Content Safety in the Microsoft Foundry portal](https://learn.microsoft.com/en-us/azure/ai-foundry/ai-services/content-safety-overview)
+10. [Content Safety in the Microsoft Foundry portal](https://learn.microsoft.com/en-us/azure/foundry-classic/ai-services/content-safety-overview)
     *Confidence: High* — Beskrivelse av Content Safety Studio features, Try it out workflow
 
 **Baseline (modellkunnskap, ikke verifisert mot ferske kilder):**