CCM-11327: Remove client config (#1)

* CCM-11327: Update README with purpose of this repo

* CCM-11327: Remove client-specific model files

Author: m-houston

.gitignore

@@ -25,3 +25,4 @@ dist
 /.idea
 
 .env
+/.envrc

README.md

@@ -1,50 +1,40 @@
-# NHS Notify Config
+# NHS Notify Supplier Config
 
-This repository contains code and schemas for NHS Notify configuration management, event publishing, and onboarding automation.
+This repository contains code and schemas for NHS Notify supplier configuration management and event publishing.
 
 ## Purpose
 
-- **Configuration Model:** Defines and manages client, campaign, quota, supplier, and routing configuration for NHS Notify.
-- **Event Schemas:** Publishes configuration changes as events to an event bus for consumption by other system components.
-- **Onboarding Automation:** Automates and streamlines the onboarding of new integrators, supporting self-serve and admin-driven workflows.
+- **Configuration Model:** Defines and manages supplier, quota, routing, and related configuration for NHS Notify
+  suppliers.
+- **Event Schemas:** Publishes configuration changes as events to an event bus for consumption by other system
+  components.
 
 ## Design
 
 ### Configuration Management
 
-A phased approach will be used to improve client configuration management:
+A phased approach will be used to improve supplier configuration management:
 
 1. **Libraries & Validation:** Standardise configuration and naming, reduce manual errors, and improve auditability.
-2. **API Layer:** Centralise access to configuration data.
-3. **Web UI:** Enable operations/admin teams to manage configuration with validation and audit trails.
+2. **API Layer:** Centralise access to supplier configuration data.
+3. **Web UI:** Enable operations/admin teams to manage supplier configuration with validation and audit trails.
 
 Configuration entities include:
 
-- `client`, `campaign`, `client_feature`, `client_quota`, `client_subscription`
-- `mesh_mailbox`, `apim_application`, `govuknotify_account`
-- `supplier_quota`, `channel_supplier`, `queue`, `suppression_filter`, `additional_mesh_report_subscription`
+- `supplier_quota`, `channel_supplier`, `queue`, `suppression_filter`, `govuknotify_account`
 
 Configuration changes are validated, auditable, and published to environments via an event bus.
 
 ### Event Publishing
 
-Configuration changes are published as events to a central event bus, enabling decoupled updates across bounded contexts (core, print supplier API, template/routing UI, user management, etc.).
+Configuration changes are published as events to a central event bus, enabling decoupled updates across bounded
+contexts (core, print supplier API, template/routing UI, user management, etc.).
 
 Event publishing strategies include:
 
 - CLI tools (tactical)
-- Scheduled audit tasks (tactical)
 - Admin/Web UI (strategic, single source of truth)
 
-### Onboarding Automation
-
-Quick Start onboarding will enable rapid, self-serve client setup in INT:
-
-- **Phase 1:** CLI/script automation using minimal data (client name, APIM ID, etc.)
-- **Phase 2:** Web UI for onboarding, protected by CIS2 auth, triggers config change events
-- **Phase 3:** Admin UI for incremental client config management and production promotion
-- **Phase 4:** Full self-serve onboarding via Web UI (admin approval for production)
-
 ## Usage
 
 ### Testing

package-lock.json

@@ -34,7 +34,7 @@
     "tsx": "^4.19.3",
     "typescript-eslint": "^8.35.1"
   },
-  "name": "nhs-notify-config",
+  "name": "nhs-notify-supplier-config",
   "overrides": {
     "pretty-format": {
       "react-is": "19.0.0"

package.json

@@ -6,7 +6,7 @@ const config: Config = {
   testMatch: ["**/__tests__/**/*.ts", "**/?(*.)+(spec|test).ts"],
   moduleFileExtensions: ["ts", "js", "json", "node"],
   moduleNameMapper: {
-    "@nhsdigital/nhs-notify-config-schemas$":
+    "@nhsdigital/nhs-notify-supplier-config-schemas$":
       "<rootDir>/../../packages/schemas/src",
   },
 };

packages/event-builder/jest.config.ts

@@ -1,6 +1,6 @@
 {
   "dependencies": {
-    "@nhsdigital/nhs-notify-config-schemas": "1.0.0",
+    "@nhsdigital/nhs-notify-supplier-config-schemas": "1.0.0",
     "csv-parse": "^5.6.0",
     "zod": "^4.0.17"
   },
@@ -14,7 +14,7 @@
     "jest-mock-extended": "^3.0.7",
     "typescript": "^5.8.2"
   },
-  "name": "nhs-notify-config-event-builder",
+  "name": "nhs-notify-supplier-config-event-builder",
   "private": true,
   "scripts": {
     "build": "tsc",

packages/event-builder/package.json

@@ -8,4 +8,5 @@ export const loadConfig = () => {
   return $Config.parse(process.env);
 };
 
-export const eventSource = "//notify.nhs.uk/app/nhs-notify-config-dev/main";
+export const eventSource =
+  "//notify.nhs.uk/app/nhs-notify-supplier-config-dev/main";