1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
// Some ai_response helpers are themselves deprecated in favor of
// mockforge-template-expansion; internal tests still reference them.
//! AI-powered intelligence for MockForge
//!
//! This crate contains modules extracted from `mockforge-core` related to
//! intelligent behavior, AI response generation, and behavioral cloning.
//!
//! Currently migrated:
//! - `ai_response`: Typed AI response generation helpers
//! - `behavioral_cloning`: Probability models, sequence learning, edge amplification
//! - `pr_generation`: GitHub/GitLab PR generation client (Issue #562 phase 1 —
//! moved out of `mockforge-core` because it only depends on
//! `mockforge_foundation::Error`, no other core internals)
//! - `intelligent_behavior`: LLM-driven behavior model, persona-aware response
//! generation, OpenAPI-backed example/rule generation (Issue #562 phase 2 —
//! the AI cluster's leaf module, depends only on `mockforge-openapi` and
//! `mockforge-foundation`)
//! - `threat_modeling`: LLM-driven security analyzer (DoS / PII / schema /
//! error / threat / remediation generators) for the contract-drift pillar
//! (Issue #562 phase 3). Depends only on sibling `intelligent_behavior` +
//! `mockforge-openapi` + `mockforge-foundation`.
//! - `ai_contract_diff`: LLM-assisted OpenAPI diff with semantic analysis,
//! confidence scoring, recommendations, and correction proposals (Issue #562
//! phase 4). Records `ai_generation` pillar usage via the now-foundation
//! `pillar_tracking` global, so the analytics dashboard keeps reflecting
//! contract-diff activity unchanged.
//! - `contract_validation`: OpenAPI-spec-to-response contract validator (Issue
//! #562 phase 5). Single file; depends only on `serde` + `mockforge-openapi`
//! + `mockforge-foundation::pillar_tracking`.
//! - `failure_analysis`: LLM-driven failure context + narrative generator
//! (Issue #562 phase 5). Depends only on sibling `intelligent_behavior`.
//! - `behavioral_economics`: Declarative + scriptable rule engine that makes
//! mocks react to pressure, load, pricing, fraud, and customer segments
//! (Issue #562 phase 8). Self-contained — the only core-side dep was
//! `crate::Result`, now sourced from `mockforge-foundation` directly.
//! - `incidents`: AI-coupled pieces of drift-incident management — semantic
//! incident manager (built on `ai_contract_diff::semantic_analyzer`) and
//! Jira/Slack/webhook integrations (Issue #562 phase 9). The structural
//! `IncidentManager` and in-memory `IncidentStore` stay in `mockforge-core`;
//! the shared types (`DriftIncident`, `IncidentSeverity`, ...) live in
//! `mockforge_foundation::incidents_types`. Core re-exports this module so
//! the legacy `mockforge_core::incidents::{semantic_manager, integrations,
//! slack_formatter, jira_formatter}` paths keep resolving.
/// HTTP-side AI response handler combining `IntelligentMockGenerator`
/// + `DataDriftEngine` (#656 — post-#555 follow-up). Moved from
/// `mockforge_http::ai_handler`; original `mockforge_core::{Result,
/// Error}` imports now resolve directly to `mockforge_foundation`, so
/// the move is cycle-safe.
/// Cross-protocol consistency engine (#555 phase 7 — moved from
/// `mockforge_core::consistency` because its only foreign-to-core deps
/// (`Protocol`, `RealityLevel`, `mockforge-data` persona types) were
/// all available from foundation / intelligence / data, and the
/// consistency HTTP handler needed to follow into intelligence under
/// the #555 bucket plan).
/// Postgres pool wrapper used by HTTP handlers that persist drift
/// budgets / incidents / consumer contracts. Moved here from
/// `mockforge_http::database` under #555 (prereq for handler moves —
/// once handlers leave `mockforge-http`, they pick up this dep without
/// re-introducing a cycle). Gated by the `database` feature.
/// Deceptive-canary endpoint configuration types (#555 phase 6 — moved
/// out of `mockforge-core` because its only callers are the (still in
/// http) middleware + the deceptive_canary HTTP handler, and keeping
/// the module here lets the eventual handler move follow). Self-contained.
/// Mock-quality fidelity scoring (#555 phase 6 — moved out of
/// `mockforge-core`). Self-contained pure-Rust scoring with no foreign
/// deps.
/// HTTP handlers for AI-coupled features. New in #555 phase 2 — see
/// `handlers/mod.rs` for migration progress.
/// RAG-based `AiGenerator` implementation (#555 phase 10 — moved from
/// `mockforge_http::rag_ai_generator`). Both foreign deps
/// (`AiResponseConfig`, `AiGenerator` trait) were promoted out of
/// `mockforge-core` to `mockforge-foundation` and `mockforge-openapi`
/// respectively, so this move stays cycle-safe with the Issue #562
/// cycle-break.
/// Scenario Studio — visual editor for co-editing business flows
/// (#555 phase 7 — moved out of `mockforge-core`; only foreign ref was
/// `crate::error::{Error, Result}` which is already a re-export of
/// `mockforge_foundation::error`).