omnibase_infra 0.2.5__py3-none-any.whl → 0.2.7__py3-none-any.whl

omnibase_infra/validation/validation_exemptions.yaml

@@ -89,6 +89,23 @@ skip_directories:
 # These handle method count, parameter count, naming, and style violations
 pattern_exemptions:
   # ==========================================================================
+  # ModelRuntimeContractConfig Exemptions (OMN-1519)
+  # ==========================================================================
+  # Data model with cohesive accessor properties for querying loaded contracts.
+  # All methods serve same purpose: querying contract_results collection.
+  # Properties: all_successful, success_rate, successful_results, failed_results,
+  #             handler_routing_configs, operation_bindings_configs, error_messages
+  # Methods: get_routing_for_contract, get_bindings_for_contract, __bool__, __str__
+  - file_pattern: 'model_runtime_contract_config\.py'
+    class_pattern: "Class 'ModelRuntimeContractConfig'"
+    violation_pattern: 'has \d+ methods'
+    reason: >
+      Cohesive data model with accessor properties that all query the same contract_results collection. Properties provide convenient typed access to loaded configs, success metrics, and error details. Breaking into smaller classes would reduce cohesion without meaningful benefit.
+
+    documentation:
+      - OMN-1519 PR description
+    ticket: OMN-1519
+  # ==========================================================================
   # EventBusKafka Exemptions (OMN-934, OMN-1305)
   # ==========================================================================
   # Event bus pattern requires many methods for lifecycle (start/stop/health),
@@ -1762,10 +1779,185 @@ pattern_exemptions:
       - CLAUDE.md (Type Annotation Conventions)
       - Consul service discovery documentation
     ticket: OMN-1278
+    # ==========================================================================
+  # ==========================================================================
+  # OperationBindingResolver.resolve() requires multiple parameters for binding
+  # resolution: operation, bindings_subcontract, envelope, context, correlation_id.
+  # These are distinct inputs required for the resolution process.
+  - file_pattern: 'binding_resolver\.py'
+    # Declarative Operation Bindings Exemptions (OMN-1518)
+
+    method_pattern: "Function 'resolve'"
+    violation_pattern: 'has \d+ parameters'
+    reason: >
+      resolve() requires distinct parameters for binding resolution: operation name, bindings subcontract, envelope data, optional context, and correlation_id for error context. Breaking into multiple calls would require intermediate state or complex configuration objects that reduce API clarity.
+
+    documentation:
+      - docs/decisions/adr-declarative-operation-bindings.md
+    ticket: OMN-1518
+  # parameter_name in binding models is the handler parameter name being bound,
+  # NOT an entity reference. It's a simple string identifier for the target parameter.
+  - file_pattern: 'model_operation_binding\.py'
+    violation_pattern: "Field 'parameter_name' might reference an entity"
+    reason: >
+      parameter_name is the target handler input field name (e.g., "correlation_id", "sql"). This is a Python function parameter name, NOT an entity reference. It maps to the handler's function signature parameter.
+
+    documentation:
+      - docs/decisions/adr-declarative-operation-bindings.md
+    ticket: OMN-1518
+  - file_pattern: 'model_parsed_binding\.py'
+    violation_pattern: "Field 'parameter_name' might reference an entity"
+    reason: >
+      parameter_name is the target handler input field name (e.g., "correlation_id", "sql"). This is a Python function parameter name, NOT an entity reference. It maps to the handler's function signature parameter.
+
+    documentation:
+      - docs/decisions/adr-declarative-operation-bindings.md
+    ticket: OMN-1518
+  # operation_name in ModelBindingResolutionResult is the operation that was
+  # resolved (e.g., "db.query"), NOT an entity reference. It's a dispatch key.
+  - file_pattern: 'model_binding_resolution_result\.py'
+    violation_pattern: "Field 'operation_name' might reference an entity"
+    reason: >
+      operation_name is the dispatch operation key that was resolved (e.g., "db.query", "consul.register"). This is a routing identifier, NOT an entity reference. It identifies which operation's bindings were resolved.
+
+    documentation:
+      - docs/decisions/adr-declarative-operation-bindings.md
+    ticket: OMN-1518
+  # ==========================================================================
+  # ModelNodeIdentity node_name Exemption (OMN-1602)
+  # ==========================================================================
+  # node_name in ModelNodeIdentity is a canonical identifier for the node within
+  # the ONEX infrastructure, NOT a foreign key reference to another entity.
+  # It is one of the four dimensions (env, service, node_name, version) that
+  # uniquely identify a node instance.
+  - file_pattern: 'model_node_identity\.py'
+    violation_pattern: "Field 'node_name' might reference an entity"
+    reason: >
+      node_name is a canonical identifier (e.g., "claude_hook_event_effect") that uniquely identifies a node within its service. It is NOT a foreign key reference - it is the node's own name from its contract. Combined with env, service, and version, it forms the node's identity.
+
+    documentation:
+      - docs/architecture/REGISTRATION_ORCHESTRATOR_ARCHITECTURE.md
+    ticket: OMN-1602
+  # ==========================================================================
+  # Emit Daemon Field Type Exemptions (OMN-1610)
+  # ==========================================================================
+  # Fields that are intentionally str instead of UUID for specific reasons
+  - file_pattern: 'emit_daemon/queue\.py'
+    violation_pattern: "Field 'event_id' should use UUID type instead of str"
+    reason: event_id is a string representation of a UUID for JSON serialization compatibility.
+    documentation:
+      - src/omnibase_infra/runtime/emit_daemon/queue.py
+    ticket: OMN-1610
+  - file_pattern: 'emit_daemon/model_daemon_response\.py'
+    violation_pattern: "Field 'event_id' should use UUID type instead of str"
+    reason: event_id is returned as a string in the daemon protocol for JSON serialization compatibility. Matches queue.py event_id.
+    documentation:
+      - src/omnibase_infra/runtime/emit_daemon/model_daemon_response.py
+    ticket: OMN-1610
+  - file_pattern: 'emit_daemon/config\.py'
+    violation_pattern: "Field 'kafka_client_id' should use UUID type instead of str"
+    reason: kafka_client_id is a Kafka client identifier string, not a UUID.
+    documentation:
+      - Kafka client.id documentation
+    ticket: OMN-1610
+  # ==========================================================================
+  # Contract Registry Reducer Handler Exemptions (OMN-1653)
+  # ==========================================================================
+  # Pure reducer handlers follow the pattern: (self, state, event, topic, partition, offset)
+  # This 6-parameter signature is standard for event-sourced reducers that need:
+  # - state: immutable input state
+  # - event: typed domain event
+  # - topic/partition/offset: Kafka position for idempotency tracking
+  - file_pattern: 'nodes/contract_registry_reducer/reducer\.py'
+    method_pattern: '_on_contract_registered'
+    violation_pattern: 'has 6 parameters'
+    reason: >
+      Standard reducer handler signature for event-sourced reducers. The 6 parameters provide: self, state (immutable input), event (typed domain event), and Kafka position (topic/partition/offset) for idempotency tracking. This is the canonical pattern for ONEX reducers.
+
+    documentation:
+      - CLAUDE.md (Node Archetypes - NodeReducer)
+      - docs/patterns/reducer_pattern.md
+    ticket: OMN-1653
+  - file_pattern: 'nodes/contract_registry_reducer/reducer\.py'
+    method_pattern: '_on_contract_deregistered'
+    violation_pattern: 'has 6 parameters'
+    reason: Same as _on_contract_registered - standard reducer handler signature.
+    documentation:
+      - CLAUDE.md (Node Archetypes - NodeReducer)
+    ticket: OMN-1653
+  - file_pattern: 'nodes/contract_registry_reducer/reducer\.py'
+    method_pattern: '_on_heartbeat'
+    violation_pattern: 'has 6 parameters'
+    reason: Same as _on_contract_registered - standard reducer handler signature.
+    documentation:
+      - CLAUDE.md (Node Archetypes - NodeReducer)
+    ticket: OMN-1653
+  - file_pattern: 'nodes/contract_registry_reducer/reducer\.py'
+    method_pattern: '_on_runtime_tick'
+    violation_pattern: 'has 6 parameters'
+    reason: Same as _on_contract_registered - standard reducer handler signature.
+    documentation:
+      - CLAUDE.md (Node Archetypes - NodeReducer)
+    ticket: OMN-1653
+  # Contract ID is a derived natural key (node_name:major.minor.patch), not a UUID.
+  # This is intentional per the contract registry design where contracts are identified
+  # by their name and version, enabling human-readable queries and deduplication.
+  - file_pattern: 'nodes/contract_registry_reducer/models/model_payload_.*\.py'
+    violation_pattern: "Field 'contract_id' should use UUID"
+    reason: >
+      contract_id is a derived natural key (node_name:major.minor.patch), not a UUID. This design enables human-readable queries, version-based deduplication, and matches the contract.yaml identification pattern used throughout ONEX.
+
+    documentation:
+      - CLAUDE.md (Intent Model Architecture - Contract Identity)
+    ticket: OMN-1653
+  # node_name is the contract's semantic name, not an entity reference requiring ID + display_name.
+  - file_pattern: 'nodes/contract_registry_reducer/models/model_payload_.*\.py'
+    violation_pattern: "Field 'node_name' might reference an entity"
+    reason: >
+      node_name is the contract's semantic identifier from contract.yaml, not a reference to a separate entity. Contracts are identified by name, making this a primary attribute not a foreign key.
+
+    documentation:
+      - CLAUDE.md (Contract-Driven - node_name conventions)
+    ticket: OMN-1653
 # Architecture validator exemptions
 # These handle one-model-per-file violations for domain-grouped protocols
 architecture_exemptions:
   # ==========================================================================
+  # Emit Daemon Config Input Model Exemption (OMN-1610)
+  # ==========================================================================
+  # config.py contains ModelEmitDaemonConfigInput (intermediate input model)
+  # and ModelEmitDaemonConfig (final validated config). The input model is
+  # tightly coupled and only used internally by with_env_overrides() factory.
+  - file_pattern: 'emit_daemon/config\.py'
+    violation_pattern: '\d+ models in one file'
+    reason: >
+      ModelEmitDaemonConfigInput is an intermediate input model used only by ModelEmitDaemonConfig.with_env_overrides() factory method. It provides early validation for environment variable parsing and is tightly coupled with the main config model. Separating would add complexity without benefit.
+
+    documentation:
+      - CLAUDE.md (Protocol File Naming - domain-grouping convention)
+    ticket: OMN-1610
+  # ==========================================================================
+  # Emit Daemon Protocol Models Exemption (OMN-1610)
+  # ==========================================================================
+  # Request and response models form discriminated unions that are always used
+  # together. Separating into individual files would break the cohesive API.
+  - file_pattern: 'emit_daemon/model_daemon_request\.py'
+    violation_pattern: '\d+ models in one file'
+    reason: >
+      ModelDaemonPingRequest and ModelDaemonEmitRequest form a discriminated union (ModelDaemonRequest) for the daemon protocol. These request types are always parsed together via parse_daemon_request(). Per CLAUDE.md domain-grouping convention for protocol messages.
+
+    documentation:
+      - CLAUDE.md (Protocol File Naming - domain-grouping convention)
+    ticket: OMN-1610
+  - file_pattern: 'emit_daemon/model_daemon_response\.py'
+    violation_pattern: '\d+ models in one file'
+    reason: >
+      ModelDaemonPingResponse, ModelDaemonQueuedResponse, and ModelDaemonErrorResponse form a discriminated union (ModelDaemonResponse) for the daemon protocol. These response types are always parsed together via parse_daemon_response(). Per CLAUDE.md domain-grouping convention for protocol messages.
+
+    documentation:
+      - CLAUDE.md (Protocol File Naming - domain-grouping convention)
+    ticket: OMN-1610
+  # ==========================================================================
   # Contract Linter Models Exemption (PR #57)
   # ==========================================================================
   # linter_contract.py contains domain-grouped validation models and enums

{omnibase_infra-0.2.5.dist-info → omnibase_infra-0.2.7.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: omnibase_infra
-Version: 0.2.5
+Version: 0.2.7
 Summary: ONEX Infrastructure - Service integration and database infrastructure tools
 License: MIT
 License-File: LICENSE
@@ -28,8 +28,8 @@ Requires-Dist: jinja2 (>=3.1.6,<4.0.0)
 Requires-Dist: jsonschema (>=4.20.0,<5.0.0)
 Requires-Dist: mcp (>=1.25.0,<2.0.0)
 Requires-Dist: neo4j (>=5.15.0,<6.0.0)
-Requires-Dist: omnibase-core (>=0.9.6,<0.10.0)
-Requires-Dist: omnibase-spi (>=0.6.1,<0.7.0)
+Requires-Dist: omnibase-core (>=0.9.10,<0.10.0)
+Requires-Dist: omnibase-spi (>=0.6.3,<0.7.0)
 Requires-Dist: opentelemetry-api (>=1.27.0,<2.0.0)
 Requires-Dist: opentelemetry-exporter-otlp (>=1.27.0,<2.0.0)
 Requires-Dist: opentelemetry-instrumentation (>=0.48b0,<0.49)