Nomad changes

.ai-rulez/domains/plugin-system/rules/plugin-extensibility.md

@@ -0,0 +1,10 @@
+---
+priority: medium
+---
+
+- API stability: plugin interfaces are versioned, breaking changes require major version bump
+- Plugin discovery: support both static (compile-time) and dynamic (runtime) registration
+- Plugin validation: check capabilities, supported formats, and version compatibility before registration
+- Plugin chaining: post-processors can be composed in sequence
+- Configuration: plugins accept typed configuration, validated at registration time
+- Documentation: every plugin type must have a development guide with examples

.ai-rulez/domains/plugin-system/rules/plugin-interface-contract.md

@@ -0,0 +1,10 @@
+---
+priority: critical
+---
+
+- All plugins must implement the base Plugin trait: Send + Sync + 'static required
+- Plugin types: DocumentExtractor, OcrBackend, PostProcessor, Validator
+- Async execution: use async trait methods for non-blocking operations
+- Lifecycle: init() -> process() -> cleanup(). Init must validate all requirements.
+- Never panic in plugin code — all errors must be returned as Result
+- Consistent result format: all extractors return ExtractionResult with text, metadata, and confidence

.ai-rulez/domains/plugin-system/rules/plugin-registry-and-selection.md

@@ -0,0 +1,12 @@
+---
+priority: critical
+---
+
+- Separate typed registry per plugin type (ExtractorRegistry, OcrRegistry, etc.)
+- Thread safety: Arc<RwLock<>> for all registries
+- Priority system: 0-255, default 50, custom > 50, fallback < 50
+- Selection: highest priority plugin matching the MIME type wins
+- MIME type indexing for O(log n) lookup
+- Conflict resolution: if equal priority, prefer Rust-native over FFI plugins
+- Dynamic registration: plugins can be added/removed at runtime
+- Validate plugin before registration (check trait compliance, supported formats)

.ai-rulez/domains/plugin-system/rules/plugin-testing.md

@@ -0,0 +1,10 @@
+---
+priority: high
+---
+
+- Mock plugin testing: create test doubles for unit tests
+- Real plugin testing: integration tests with actual backends
+- Thread safety tests: run concurrent plugin operations to detect race conditions
+- Performance baselines: measure and track plugin overhead vs direct calls
+- Test all error paths: invalid input, backend failure, timeout, resource exhaustion
+- Test plugin lifecycle: register, use, unregister, verify cleanup

.ai-rulez/domains/plugin-system/rules/python-ffi-plugins.md

@@ -0,0 +1,11 @@
+---
+priority: high
+---
+
+- GIL management: use py.allow_threads() for expensive Rust operations
+- Cache frequently-accessed Python data in Rust fields to minimize GIL acquisitions
+- Use tokio::task::spawn_blocking for async calls to Python backends
+- Python exception translation: convert Python exceptions to Rust errors with full context
+- Data type mapping: Python str <-> Rust String, Python bytes <-> Rust Vec<u8>, Python dict <-> Rust HashMap
+- Validate Python plugin protocol compliance on registration
+- Target GIL overhead: 5-55us per acquisition