chore(privacy): scrub real-org references from plugin internals (phase 2)

Same bulk replacement applied to plugin-internal KB, examples, fixtures,
tests, and docs. Real organization names, persona names, internal system
identifiers, and domain-specific terms replaced with fictional generic
public-sector entity (DDT) and generic terminology.

Scope:
- okr/ — examples, governance, framework, integrations, sources
- ms-ai-architect/ — KB references (engineering, governance, security,
  infrastructure, advisor), tests/fixtures, agents, docs
- linkedin-thought-leadership/ — voice samples, network-builder,
  examples (genericized identifying headlines to "[your organization]")
- llm-security/ — research notes, scan report

Manual genericization beyond bulk replace:
- okr SKILL.md "Primary user / Domain" — generic Norwegian public sector
- linkedin-voice SKILL.md headline placeholder
- network-builder.md headline placeholder
- high-engagement-posts.md voice sample employer line + hashtag

Phase 3 (factual-attribution review) remains: a few KB files attribute
publicly known transport-sector docs/datasets (e.g. håndbok V440, NVDB)
to the fictional DDT after bulk replace. Needs manual semantic review
to either remove or restore correct citation without re-introducing
affiliation references.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

plugins/okr/README.md

@@ -20,7 +20,7 @@
 
 Every organization has a strategy. Few manage to turn it into goals that teams actually work toward.
 
-OKR (Objectives and Key Results) is a proven framework for that translation — used by Google, Intel, and increasingly by Norwegian public sector organizations like NAV, FINN.no, and Statens vegvesen. But adopting OKR is hard. The methodology sounds simple ("write inspiring goals with measurable results") until you try it. Then you hit real questions:
+OKR (Objectives and Key Results) is a proven framework for that translation — used by Google, Intel, and increasingly by Norwegian public sector organizations like NAV, FINN.no, and Direktoratet for digital tjenesteutvikling. But adopting OKR is hard. The methodology sounds simple ("write inspiring goals with measurable results") until you try it. Then you hit real questions:
 
 - *How do we connect our OKR to the goals in our tildelingsbrev?*
 - *What's a good Key Result vs. just an activity disguised as one?*