What problem does it solve? Teams running Kubernetes test and preview environments need to stub external HTTP dependencies without deploying a mock server per application, and without stub collisions or cross-team interference on shared infrastructure. ## Core Features & Use Cases - Shared WireMock addon chart: Packages WireMock as a baseline addon in the testing-system namespace with a single-replica Recreate Deployment, NetworkPolicy gating by consumer label, and production gating defaulted off. - Declarative per-release stubs: Consumer apps declare stubs in Helm values; library helpers (myorg.wiremock.syncJob, stubsConfigMap, cleanupJob) register them via the WireMock Admin API with metadata.owner=<release> tagging and /__mocks__/<release>/ URL-prefix isolation for atomic replace. - WireMock.Net boundary guidance: Distinguishes the shared Java WireMock cluster instance from in-process WireMock.Net servers for xUnit unit tests, including fixture and stubbing examples. - Use Case: A platform engineer adds addon_charts/wiremock/ to the GitOps repo, then a consumer service sets mocks.wiremock.enabled: true with stub entries in values-test.yaml and gets its mocks registered automatically on the next ArgoCD sync. ## Quick Start Ask the AI to add a shared WireMock addon chart and wire a consumer Helm chart to register its stub mappings in the testing-system namespace.