feat(onnx): add in-process plugin manifest

Add the ONNX Runtime plugin manifest with an explicit in-process installation type, ONNX model compatibility, runtime-profile and model-library panel declarations, and no version-manager or connection-url capability. This keeps ONNX metadata aligned with the Rust in-process session manager instead of pretending there is a binary or Python sidecar install path.

Extend Rust and TypeScript plugin schemas to accept the in-process installation type, and add Rust schema coverage for both a minimal in-process fixture and the checked-in ONNX manifest.

Update the ONNX Runtime serving plan with M3 plugin identity progress and the remaining frontend registry, Rust AppId/version-manager, and lifecycle follow-ups.

Verification: cargo fmt --manifest-path rust/Cargo.toml --all -- --check; cargo test --manifest-path rust/crates/pumas-core/Cargo.toml plugins; npm run -w frontend check:types.

Author: MrScripty

docs/plans/onnx-runtime-embedding-serving/execution-and-coordination.md

@@ -802,6 +802,18 @@ Update during implementation:
   `cargo info half@2.7.1`, `cargo info ndarray@0.17.2`, local `du` checks for
   source/build directories, and a local `find` check for copied
   `libonnxruntime*` artifacts under `rust/target`.
+- 2026-05-12: Started the M3 ONNX app/plugin identity contract with an
+  in-process plugin manifest slice. `launcher-data/plugins/onnx-runtime.json`
+  now declares ONNX Runtime as an enabled in-process runtime with no version
+  manager, no connection URL, `.onnx` model compatibility, and runtime-profile
+  plus ONNX model-library panel declarations. Rust and TypeScript plugin schema
+  types now accept `installationType: "in-process"`, and Rust plugin schema
+  tests parse both a minimal in-process fixture and the checked-in ONNX
+  manifest. Frontend app registry/panel wiring, Rust `AppId`/version-manager
+  alignment, and ONNX runtime-profile lifecycle remain separate M3/M6 slices.
+  Verification passed: `cargo fmt --manifest-path rust/Cargo.toml --all
+  -- --check`, `cargo test --manifest-path rust/crates/pumas-core/Cargo.toml
+  plugins`, and `npm run -w frontend check:types`.
 
 ## Commit Cadence Notes
 

docs/plans/onnx-runtime-embedding-serving/milestones.md

@@ -533,7 +533,7 @@ non-zero token usage without calling raw ONNX provider internals.
 Ollama or llama.cpp profiles.
 
 **Tasks:**
-- [ ] Add `launcher-data/plugins/onnx-runtime.json`.
+- [x] Add `launcher-data/plugins/onnx-runtime.json`.
 - [x] Add `RuntimeProviderId::OnnxRuntime` and
       `RuntimeProviderMode::OnnxServe`.
 - [ ] Add ONNX Runtime to the frontend app registry with a sidebar icon,
@@ -604,9 +604,12 @@ Ollama or llama.cpp profiles.
 `.onnx` executable artifact support, an embedding-only ONNX provider behavior,
 an `in_process_runtime` managed launch target, and contract tests. Frontend
 runtime provider types/descriptors now include `onnx_runtime` and `onnx_serve`
-with focused descriptor tests and typecheck coverage. Plugin/app identity,
-frontend app state, ONNX runtime profile lifecycle, and full schema/fixture
-coverage remain open.
+with focused descriptor tests and typecheck coverage. Plugin metadata now
+includes `onnx-runtime` with an explicit `in-process` installation type,
+`.onnx` compatibility, runtime-profile/model-library panel declarations, no
+version-manager capability, and Rust/TypeScript plugin schema support. Frontend
+app state, Rust `AppId`/version-manager alignment, ONNX runtime profile
+lifecycle, and full schema/fixture coverage remain open.
 
 ### Milestone 4: Serving Validation And Load/Unload
 

frontend/src/types/api-plugins.ts

@@ -13,7 +13,7 @@ export interface PluginConfigResponse {
   description: string;
   icon?: string;
   githubRepo?: string;
-  installationType: 'binary' | 'python-venv' | 'docker';
+  installationType: 'binary' | 'in-process' | 'python-venv' | 'docker';
   capabilities: {
     hasVersionManagement: boolean;
     supportsShortcuts: boolean;

frontend/src/types/plugins.ts

@@ -6,7 +6,7 @@
  */
 
 /** How the app is installed and managed */
-export type InstallationType = 'binary' | 'python-venv' | 'docker';
+export type InstallationType = 'binary' | 'in-process' | 'python-venv' | 'docker';
 
 /** App capabilities that affect available features */
 export interface AppCapabilities {

launcher-data/plugins/README.md

@@ -9,6 +9,12 @@ Each manifest must describe one plugin by stable identifier, display name, execu
 ## Consumer Contract
 Consumers must parse manifests as structured data and reject missing required fields instead of applying ad hoc defaults.
 
+`installationType: "in-process"` means the runtime is supplied by Pumas itself
+and must not be routed through binary, Python, Docker, or version-manager
+installation flows. ONNX Runtime uses this shape because embedding sessions are
+owned by the Rust process and exposed through backend runtime profiles plus the
+Pumas `/v1` gateway.
+
 ## Validation Contract
 Manifest validation should run in launcher or app-manager tests before manifests are packaged for release.
 

launcher-data/plugins/onnx-runtime.json

@@ -0,0 +1,28 @@
+{
+  "id": "onnx-runtime",
+  "displayName": "ONNX Runtime",
+  "description": "In-process Rust ONNX Runtime embedding provider",
+  "icon": "cpu",
+  "installationType": "in-process",
+
+  "capabilities": {
+    "hasVersionManagement": false,
+    "supportsShortcuts": false,
+    "hasDependencies": false,
+    "hasConnectionUrl": false,
+    "hasModelLibrary": true,
+    "hasStats": false
+  },
+
+  "modelCompatibility": {
+    "supportedFormats": ["onnx"]
+  },
+
+  "panelLayout": [
+    {"type": "runtime_profiles", "config": {"provider": "onnx_runtime"}},
+    {"type": "model_library", "config": {"filter": "onnx"}}
+  ],
+
+  "sidebarPriority": 22,
+  "enabledByDefault": true
+}

rust/crates/pumas-core/src/plugins/schema.rs

@@ -11,6 +11,8 @@ use std::collections::HashMap;
 pub enum InstallationType {
     /// Standalone binary download (Ollama, etc.)
     Binary,
+    /// Runtime is provided in-process by Pumas and has no version manager.
+    InProcess,
     /// Python virtual environment (ComfyUI, etc.)
     PythonVenv,
     /// Docker container
@@ -234,6 +236,7 @@ impl PluginConfig {
 #[cfg(test)]
 mod tests {
     use super::*;
+    use std::path::PathBuf;
 
     #[test]
     fn test_deserialize_plugin() {
@@ -327,4 +330,56 @@ mod tests {
         assert!(config.supports_format("safetensors"));
         assert!(!config.supports_format("onnx"));
     }
+
+    #[test]
+    fn test_deserialize_in_process_plugin() {
+        let json = r#"{
+            "id": "onnx-runtime",
+            "displayName": "ONNX Runtime",
+            "description": "In-process Rust ONNX Runtime embedding provider",
+            "installationType": "in-process",
+            "capabilities": {
+                "hasVersionManagement": false,
+                "hasConnectionUrl": false,
+                "hasModelLibrary": true
+            },
+            "modelCompatibility": {
+                "supportedFormats": ["onnx"]
+            },
+            "panelLayout": [
+                {"type": "runtime_profiles", "config": {"provider": "onnx_runtime"}},
+                {"type": "model_library", "config": {"filter": "onnx"}}
+            ],
+            "sidebarPriority": 22
+        }"#;
+
+        let config: PluginConfig = serde_json::from_str(json).unwrap();
+
+        assert_eq!(config.id, "onnx-runtime");
+        assert_eq!(config.installation_type, InstallationType::InProcess);
+        assert!(!config.capabilities.has_version_management);
+        assert!(!config.capabilities.has_connection_url);
+        assert!(config.capabilities.has_model_library);
+        assert!(config.supports_format("onnx"));
+    }
+
+    #[test]
+    fn onnx_runtime_manifest_matches_in_process_contract() {
+        let manifest_path = PathBuf::from(env!("CARGO_MANIFEST_DIR"))
+            .join("../../..")
+            .join("launcher-data/plugins/onnx-runtime.json");
+        let json = std::fs::read_to_string(manifest_path).unwrap();
+        let config: PluginConfig = serde_json::from_str(&json).unwrap();
+
+        assert_eq!(config.id, "onnx-runtime");
+        assert_eq!(config.display_name, "ONNX Runtime");
+        assert_eq!(config.installation_type, InstallationType::InProcess);
+        assert!(!config.capabilities.has_version_management);
+        assert!(!config.capabilities.has_connection_url);
+        assert!(config.supports_format("onnx"));
+        assert!(config
+            .panel_layout
+            .iter()
+            .any(|section| section.section_type == "runtime_profiles"));
+    }
 }