Rename Vexer to Excititor

docs/dev/30_EXCITITOR_CONNECTOR_GUIDE.md

@@ -1,18 +1,18 @@
-# Vexer Connector Packaging Guide
+# Excititor Connector Packaging Guide
 
-> **Audience:** teams implementing new Vexer provider plug‑ins (CSAF feeds,
+> **Audience:** teams implementing new Excititor provider plug‑ins (CSAF feeds,
 > OpenVEX attestations, etc.)  
-> **Prerequisites:** read `docs/ARCHITECTURE_VEXER.md` and the module
-> `AGENTS.md` in `src/StellaOps.Vexer.Connectors.Abstractions/`.
+> **Prerequisites:** read `docs/ARCHITECTURE_EXCITITOR.md` and the module
+> `AGENTS.md` in `src/StellaOps.Excititor.Connectors.Abstractions/`.
 
-The Vexer connector SDK gives you:
+The Excititor connector SDK gives you:
 
 - `VexConnectorBase` – deterministic logging, SHA‑256 helpers, time provider.
 - `VexConnectorOptionsBinder` – strongly typed YAML/JSON configuration binding.
 - `IVexConnectorOptionsValidator<T>` – custom validation hooks (offline defaults, auth invariants).
 - `VexConnectorDescriptor` & metadata helpers for consistent telemetry.
 
-This guide explains how to package a connector so the Vexer Worker/WebService
+This guide explains how to package a connector so the Excititor Worker/WebService
 can load it via the plugin host.
 
 ---
@@ -20,12 +20,12 @@ can load it via the plugin host.
 ## 1. Project layout
 
 Start from the template under
-`docs/dev/templates/vexer-connector/`. It contains:
+`docs/dev/templates/excititor-connector/`. It contains:
 
 ```
-Vexer.MyConnector/
+Excititor.MyConnector/
 ├── src/
-│   ├── Vexer.MyConnector.csproj
+│   ├── Excititor.MyConnector.csproj
 │   ├── MyConnectorOptions.cs
 │   ├── MyConnector.cs
 │   └── MyConnectorPlugin.cs
@@ -36,8 +36,8 @@ Vexer.MyConnector/
 Key points:
 
 - Target `net10.0`, enable `TreatWarningsAsErrors`, reference the
-  `StellaOps.Vexer.Connectors.Abstractions` project (or NuGet once published).
-- Keep project ID prefix `StellaOps.Vexer.Connectors.<Provider>` so the
+  `StellaOps.Excititor.Connectors.Abstractions` project (or NuGet once published).
+- Keep project ID prefix `StellaOps.Excititor.Connectors.<Provider>` so the
   plugin loader can discover it with the default search pattern.
 
 ### 1.1 csproj snippet
@@ -51,7 +51,7 @@ Key points:
     <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
   </PropertyGroup>
   <ItemGroup>
-    <ProjectReference Include="..\..\..\src\StellaOps.Vexer.Connectors.Abstractions\StellaOps.Vexer.Connectors.Abstractions.csproj" />
+    <ProjectReference Include="..\..\..\src\StellaOps.Excititor.Connectors.Abstractions\StellaOps.Excititor.Connectors.Abstractions.csproj" />
   </ItemGroup>
 </Project>
 ```
@@ -135,7 +135,7 @@ this contract today.
 public sealed class MyConnectorPlugin : IConnectorPlugin
 {
     private static readonly VexConnectorDescriptor Descriptor =
-        new("vexer:my-provider", VexProviderKind.Vendor, "My Provider VEX");
+        new("excititor:my-provider", VexProviderKind.Vendor, "My Provider VEX");
 
     public string Name => Descriptor.DisplayName;
 
@@ -150,8 +150,8 @@ public sealed class MyConnectorPlugin : IConnectorPlugin
 }
 ```
 
-> **Note:** the Vexer Worker currently instantiates connectors through the
-> shared `IConnectorPlugin` contract. Once a dedicated Vexer plugin interface
+> **Note:** the Excititor Worker currently instantiates connectors through the
+> shared `IConnectorPlugin` contract. Once a dedicated Excititor plugin interface
 > lands you simply swap the base interface; the descriptor/connector code
 > remains unchanged.
 
@@ -159,18 +159,18 @@ Provide a manifest describing the assembly for operational tooling:
 
 ```yaml
 # manifest/connector.manifest.yaml
-id: vexer-my-provider
-assembly: StellaOps.Vexer.Connectors.MyProvider.dll
-entryPoint: StellaOps.Vexer.Connectors.MyProvider.MyConnectorPlugin
+id: excititor-my-provider
+assembly: StellaOps.Excititor.Connectors.MyProvider.dll
+entryPoint: StellaOps.Excititor.Connectors.MyProvider.MyConnectorPlugin
 description: >
   Official VEX feed for ExampleCorp products (CSAF JSON, daily updates).
 tags:
-  - vexer
+  - excititor
   - csaf
   - vendor
 ```
 
-Store manifests under `/opt/stella/vexer/plugins/<connector>/manifest/` in
+Store manifests under `/opt/stella/excititor/plugins/<connector>/manifest/` in
 production so the deployment tooling can inventory and verify plug‑ins.
 
 ---
@@ -178,9 +178,9 @@ production so the deployment tooling can inventory and verify plug‑ins.
 ## 4. Packaging workflow
 
 1. `dotnet publish -c Release` → copy the published DLLs to
-   `/opt/stella/vexer/plugins/<Provider>/`.
+   `/opt/stella/excititor/plugins/<Provider>/`.
 2. Place `connector.manifest.yaml` next to the binaries.
-3. Restart the Vexer Worker or WebService (hot reload not supported yet).
+3. Restart the Excititor Worker or WebService (hot reload not supported yet).
 4. Verify logs: `VEX-ConnectorLoader` should list the connector descriptor.
 
 ### 4.1 Offline kits
@@ -195,7 +195,7 @@ production so the deployment tooling can inventory and verify plug‑ins.
 ## 5. Testing checklist
 
 - Unit tests around options binding & validators.
-- Integration tests (future `StellaOps.Vexer.Connectors.Abstractions.Tests`)
+- Integration tests (future `StellaOps.Excititor.Connectors.Abstractions.Tests`)
   verifying deterministic logging scopes:
   `logger.BeginScope` should produce `vex.connector.id`, `vex.connector.kind`,
   and `vex.connector.operation`.
@@ -206,7 +206,7 @@ production so the deployment tooling can inventory and verify plug‑ins.
 
 ## 6. Reference template
 
-See `docs/dev/templates/vexer-connector/` for the full quick‑start including:
+See `docs/dev/templates/excititor-connector/` for the full quick‑start including:
 
 - Sample options class + validator.
 - Connector implementation inheriting from `VexConnectorBase`.

docs/dev/templates/excititor-connector/manifest/connector.manifest.yaml

@@ -0,0 +1,8 @@
+id: excititor-my-provider
+assembly: StellaOps.Excititor.Connectors.MyProvider.dll
+entryPoint: StellaOps.Excititor.Connectors.MyProvider.MyConnectorPlugin
+description: |
+  Example connector template. Replace metadata before shipping.
+tags:
+  - excititor
+  - template

docs/dev/templates/excititor-connector/src/Excititor.MyConnector.csproj

@@ -7,6 +7,6 @@
   </PropertyGroup>
   <ItemGroup>
     <!-- Adjust the relative path when copying this template into a repo -->
-    <ProjectReference Include="..\..\..\..\src\StellaOps.Vexer.Connectors.Abstractions\StellaOps.Vexer.Connectors.Abstractions.csproj" />
+    <ProjectReference Include="..\..\..\..\src\StellaOps.Excititor.Connectors.Abstractions\StellaOps.Excititor.Connectors.Abstractions.csproj" />
   </ItemGroup>
 </Project>

docs/dev/templates/excititor-connector/src/MyConnector.cs

@@ -2,10 +2,10 @@ using System.Collections.Generic;
 using System.Collections.Immutable;
 using System.Runtime.CompilerServices;
 using Microsoft.Extensions.Logging;
-using StellaOps.Vexer.Connectors.Abstractions;
-using StellaOps.Vexer.Core;
+using StellaOps.Excititor.Connectors.Abstractions;
+using StellaOps.Excititor.Core;
 
-namespace StellaOps.Vexer.Connectors.MyProvider;
+namespace StellaOps.Excititor.Connectors.MyProvider;
 
 public sealed class MyConnector : VexConnectorBase
 {

docs/dev/templates/excititor-connector/src/MyConnectorOptions.cs

@@ -1,6 +1,6 @@
 using System.ComponentModel.DataAnnotations;
 
-namespace StellaOps.Vexer.Connectors.MyProvider;
+namespace StellaOps.Excititor.Connectors.MyProvider;
 
 public sealed class MyConnectorOptions
 {

docs/dev/templates/excititor-connector/src/MyConnectorOptionsValidator.cs

@@ -1,7 +1,7 @@
 using System.Collections.Generic;
-using StellaOps.Vexer.Connectors.Abstractions;
+using StellaOps.Excititor.Connectors.Abstractions;
 
-namespace StellaOps.Vexer.Connectors.MyProvider;
+namespace StellaOps.Excititor.Connectors.MyProvider;
 
 public sealed class MyConnectorOptionsValidator : IVexConnectorOptionsValidator<MyConnectorOptions>
 {

docs/dev/templates/excititor-connector/src/MyConnectorPlugin.cs

@@ -1,15 +1,15 @@
 using Microsoft.Extensions.DependencyInjection;
 using Microsoft.Extensions.Logging;
 using StellaOps.Plugin;
-using StellaOps.Vexer.Connectors.Abstractions;
-using StellaOps.Vexer.Core;
+using StellaOps.Excititor.Connectors.Abstractions;
+using StellaOps.Excititor.Core;
 
-namespace StellaOps.Vexer.Connectors.MyProvider;
+namespace StellaOps.Excititor.Connectors.MyProvider;
 
 public sealed class MyConnectorPlugin : IConnectorPlugin
 {
     private static readonly VexConnectorDescriptor Descriptor = new(
-        id: "vexer:my-provider",
+        id: "excititor:my-provider",
         kind: VexProviderKind.Vendor,
         displayName: "My Provider VEX");
 

docs/dev/templates/vexer-connector/manifest/connector.manifest.yaml

@@ -1,8 +0,0 @@
-id: vexer-my-provider
-assembly: StellaOps.Vexer.Connectors.MyProvider.dll
-entryPoint: StellaOps.Vexer.Connectors.MyProvider.MyConnectorPlugin
-description: |
-  Example connector template. Replace metadata before shipping.
-tags:
-  - vexer
-  - template