omnibase_infra 0.2.1__py3-none-any.whl → 0.2.3__py3-none-any.whl

omnibase_infra/validation/validation_exemptions.yaml

@@ -486,6 +486,47 @@ pattern_exemptions:
       - CLAUDE.md (Registry Naming Conventions)
     ticket: OMN-953
   # ==========================================================================
+  # TransitionNotificationPublisher publisher_id Exemption (OMN-1139)
+  # ==========================================================================
+  # publisher_id is a human-readable semantic identifier similar to scheduler_id.
+  # It identifies the publisher instance and may be auto-generated or user-specified.
+  - file_pattern: 'model_transition_notification_publisher_metrics\.py'
+    violation_pattern: "Field 'publisher_id' should use UUID"
+    reason: >
+      publisher_id is a human-readable semantic identifier (e.g., "transition-publisher-<uuid>") that identifies the publisher instance. Follows the same pattern as scheduler_id.
+
+    documentation:
+      - CLAUDE.md (Registry Naming Conventions)
+    ticket: OMN-1139
+  # ==========================================================================
+  # ModelTransitionNotificationOutboxMetrics table_name Exemption (OMN-1139)
+  # ==========================================================================
+  # table_name is the database table name string, not an entity reference.
+  - file_pattern: 'model_transition_notification_outbox_metrics\.py'
+    violation_pattern: "Field 'table_name' might reference an entity"
+    reason: >
+      table_name is the database table name string (e.g., "transition_notification_outbox"), not an entity reference. It identifies the outbox table for metrics reporting and does not require ID + display_name pattern.
+
+    documentation:
+      - CLAUDE.md (Registry Naming Conventions)
+    ticket: OMN-1139
+  # ==========================================================================
+  # TransitionNotificationOutbox Method Count Exemption (OMN-1139)
+  # ==========================================================================
+  # Outbox pattern requires lifecycle (start/stop), storage (store/cleanup),
+  # processing (process_pending), and multiple config properties for observability.
+  # NOTE: Pattern anchored with src/omnibase_infra/runtime/ prefix to match only
+  # the production file, not test files.
+  - file_pattern: 'src/omnibase_infra/runtime/transition_notification_outbox\.py'
+    class_pattern: "Class 'TransitionNotificationOutbox'"
+    violation_pattern: 'has \d+ methods'
+    reason: >
+      Transactional outbox pattern inherently requires: lifecycle methods (start/stop), storage operations (store/cleanup_processed), processing (process_pending), background loop (_processor_loop), metrics (get_metrics), and configuration properties (table_name, batch_size, poll_interval, is_running, shutdown_timeout, notifications_stored/processed/failed, strict_transaction_mode). Method count is driven by pattern requirements, not poor design.
+
+    documentation:
+      - src/omnibase_infra/schemas/schema_transition_notification_outbox.sql
+    ticket: OMN-1139
+  # ==========================================================================
   # ServiceTimeoutEmitter/Scanner Naming Exemptions (OMN-1055)
   # ==========================================================================
   # These service classes follow the CLAUDE.md Service<Name> naming convention.
@@ -1032,6 +1073,54 @@ pattern_exemptions:
       - CLAUDE.md (ONEX Architecture - Handler Types)
     ticket: OMN-1097
   # ==========================================================================
+  # Handler Bootstrap Source Exemptions (OMN-1087)
+  # ==========================================================================
+  # HandlerBootstrapSource provides hardcoded handler descriptors for core
+  # infrastructure handlers. The "Handler" in the name refers to ONEX handler
+  # concepts, consistent with HandlerContractSource and HandlerPluginLoader.
+  #
+  # Pattern specificity note: Uses separate class_pattern + violation_pattern
+  # (not combined "Class name .* contains...") for precise targeting. All three
+  # patterns must match: exact filename, exact class name, and violation type.
+  # This is consistent with HandlerContractSource/HandlerPluginLoader exemptions.
+  - file_pattern: 'handler_bootstrap_source\.py'
+    class_pattern: "Class name 'HandlerBootstrapSource'"
+    violation_pattern: "contains anti-pattern 'Handler'"
+    reason: >
+      HandlerBootstrapSource centralizes hardcoded handler registration for core infrastructure handlers (Consul, DB, HTTP, Vault). The "Handler" refers to ONEX handler concepts, consistent with HandlerContractSource. This is legitimate handler infrastructure code per OMN-1087.
+
+    documentation:
+      - docs/architecture/HANDLER_PROTOCOL_DRIVEN_ARCHITECTURE.md
+      - CLAUDE.md (ONEX Architecture - Handler Types)
+    ticket: OMN-1087
+  # ==========================================================================
+  # Handler Source Mode Exemptions (OMN-1095)
+  # ==========================================================================
+  # EnumHandlerSourceMode and HandlerSourceResolver are part of the handler
+  # source mode feature flag implementation. The "Handler" in the names refers
+  # to ONEX handler concepts (how handlers are discovered/loaded), consistent
+  # with HandlerBootstrapSource and HandlerContractSource.
+  - file_pattern: 'enum_handler_source_mode\.py'
+    class_pattern: "Class name 'EnumHandlerSourceMode'"
+    violation_pattern: "contains anti-pattern 'Handler'"
+    reason: >
+      EnumHandlerSourceMode defines handler loading modes (BOOTSTRAP, CONTRACT, HYBRID). The "Handler" refers to ONEX handler concepts - how handlers are discovered and loaded at runtime. Consistent with HandlerBootstrapSource and HandlerContractSource naming.
+
+    documentation:
+      - docs/architecture/HANDLER_PROTOCOL_DRIVEN_ARCHITECTURE.md
+      - CLAUDE.md (ONEX Architecture - Handler Types)
+    ticket: OMN-1095
+  - file_pattern: 'handler_source_resolver\.py'
+    class_pattern: "Class name 'HandlerSourceResolver'"
+    violation_pattern: "contains anti-pattern 'Handler'"
+    reason: >
+      HandlerSourceResolver implements per-handler identity resolution between bootstrap and contract sources. The "Handler" refers to ONEX handler concepts - resolving which handler source takes precedence. Consistent with HandlerBootstrapSource and HandlerContractSource naming.
+
+    documentation:
+      - docs/architecture/HANDLER_PROTOCOL_DRIVEN_ARCHITECTURE.md
+      - CLAUDE.md (ONEX Architecture - Handler Types)
+    ticket: OMN-1095
+  # ==========================================================================
   # Handler Plugin Loader Exemptions (OMN-1132)
   # ==========================================================================
   # HandlerPluginLoader discovers and loads ONEX handlers from contract YAML files.
@@ -1456,16 +1545,17 @@ pattern_exemptions:
   # ProjectorShell Exemptions (OMN-1169)
   # ==========================================================================
   # ProjectorShell implements ProtocolEventProjector protocol which requires:
-  # - Protocol properties (projector_id, aggregate_type, consumed_events, is_placeholder)
-  # - Core methods (project, get_state)
-  # - SQL execution modes (_upsert, _insert, _append, _execute_projection)
-  # - Value extraction (_extract_values, _resolve_path, _get_event_type)
-  # - Utility (_parse_row_count)
-  # Total: 11 methods, all cohesive to the projector contract pattern.
-  # NOTE: Pattern anchored with omnibase_infra/runtime/ prefix and $ suffix to
-  # match only the production file at src/omnibase_infra/runtime/projector_shell.py.
+  # - Protocol properties (projector_id, aggregate_type, consumed_events, contract, is_placeholder)
+  # - Core methods (project, get_state, get_states, partial_update, upsert_partial)
+  # - SQL execution modes handled by MixinProjectorSqlOperations
+  # - Value extraction (_extract_values, _resolve_path, _get_event_type, _execute_projection)
+  # - Notification integration (via MixinProjectorNotificationPublishing)
+  # Total: 11 methods, all cohesive to the contract-driven projector pattern.
+  # OMN-1139: Added notification publishing support via mixin composition.
+  # NOTE: Pattern anchored with src/omnibase_infra/runtime/ prefix to match only
+  # the production file at src/omnibase_infra/runtime/projector_shell.py.
   # This prevents matching test files in tests/unit/runtime/ or tests/integration/runtime/.
-  - file_pattern: 'omnibase_infra/runtime/projector_shell\.py$'
+  - file_pattern: 'src/omnibase_infra/runtime/projector_shell\.py'
     class_pattern: "Class 'ProjectorShell'"
     violation_pattern: 'has \d+ methods'
     reason: >
@@ -1631,6 +1721,47 @@ pattern_exemptions:
     documentation:
       - docs/patterns/binding_config_resolver.md
     ticket: OMN-765
+  # ==========================================================================
+  # HandlerMCP Method Count Exemption (OMN-1282)
+  # ==========================================================================
+  # MCP handler is a complex infrastructure component requiring many methods:
+  # - 4 ProtocolHandler methods (initialize, shutdown, execute, health_check)
+  # - 2 factory methods for route handlers (_create_health_endpoint, _create_tools_list_endpoint)
+  # - 2 server lifecycle methods (_start_http_server, _stop_http_server)
+  # - 3 execution/operation methods (_run_server, _execute_tool_operation, _execute_describe)
+  # Complexity is inherent to MCP protocol requirements and uvicorn server management.
+  - file_pattern: 'handler_mcp\.py'
+    class_pattern: "Class 'HandlerMCP'"
+    violation_pattern: 'has \d+ methods'
+    reason: >
+      HandlerMCP is a complex infrastructure handler implementing MCP protocol with internal uvicorn server lifecycle. The 11 methods are cohesive: 4 ProtocolHandler interface methods, 2 factory methods for Starlette route handlers (explicit closure capture), 2 server lifecycle methods (start/stop), and 3 operation methods. Splitting would fragment the unified MCP server abstraction.
+
+    documentation:
+      - CLAUDE.md (Handler Plugin Loader Patterns)
+    ticket: OMN-1282
+  # ==========================================================================
+  # Registry API Models - service_name Exemptions (OMN-1278)
+  # ==========================================================================
+  # service_name in registry API models is the Consul service name for discovery,
+  # NOT an entity reference. It's an external Consul identifier.
+  - file_pattern: 'services/registry_api/models/model_registry_node_view\.py'
+    violation_pattern: "Field 'service_name' might reference an entity"
+    reason: >
+      service_name is the Consul service name for service discovery (e.g., "onex-effect-abc123"). This is an external Consul identifier, NOT an ONEX entity reference. The node_id field provides the UUID identifier; service_name is how the node appears in Consul's catalog.
+
+    documentation:
+      - CLAUDE.md (Type Annotation Conventions)
+      - Consul service discovery documentation
+    ticket: OMN-1278
+  - file_pattern: 'services/registry_api/models/model_registry_instance_view\.py'
+    violation_pattern: "Field 'service_name' might reference an entity"
+    reason: >
+      service_name is the Consul service name for live instance discovery (e.g., "my-service"). This is an external Consul identifier, NOT an ONEX entity reference. The node_id and service_id fields provide UUID identifiers; service_name is the Consul catalog name.
+
+    documentation:
+      - CLAUDE.md (Type Annotation Conventions)
+      - Consul service discovery documentation
+    ticket: OMN-1278
 # Architecture validator exemptions
 # These handle one-model-per-file violations for domain-grouped protocols
 architecture_exemptions:

omnibase_infra/validation/validator_chain_propagation.py

@@ -183,7 +183,7 @@ def get_message_id(envelope: ModelEventEnvelope[object]) -> UUID:
     """
     # envelope_id is typed as UUID in ModelEventEnvelope, but mypy sees it as Any
     # due to the generic type parameter. Cast is required for type safety.
-    return cast(UUID, envelope.envelope_id)
+    return cast("UUID", envelope.envelope_id)
 
 
 def get_correlation_id(envelope: ModelEventEnvelope[object]) -> UUID | None:
@@ -200,7 +200,7 @@ def get_correlation_id(envelope: ModelEventEnvelope[object]) -> UUID | None:
     correlation_id = envelope.correlation_id
     if correlation_id is None:
         return None
-    return cast(UUID, correlation_id)
+    return cast("UUID", correlation_id)
 
 
 def get_causation_id(envelope: ModelEventEnvelope[object]) -> UUID | None:

omnibase_infra/validation/validator_runtime_shape.py

@@ -893,7 +893,7 @@ def enforce_execution_shape(node_archetype: EnumNodeArchetype) -> Callable[[F],
 
         # Cast wrapper to F - functools.wraps preserves the signature at runtime,
         # and mypy cannot prove the equivalence, so we use an explicit cast.
-        return cast(F, wrapper)
+        return cast("F", wrapper)
 
     return decorator