# Swift Assist — Debug and SQL evidence Pass one `SQLExecutionEvidenceStore` to the trusted `UserContext` as its telemetry sink. Application diagnostics should use `safeSQLEvidence`, which exposes parameterized SQL and parameter count but never raw parameter values. ```swift import TeaQLCore public struct SafeSQLEvidence: Sendable, Equatable { public let operation: String public let parameterizedSQL: String public let parameterCount: Int public let elapsedMicros: UInt64 public let resultCount: Int? public let affectedRows: Int? public let resultSummary: String } public func safeSQLEvidence( from store: SQLExecutionEvidenceStore ) async -> [SafeSQLEvidence] { await store.snapshot().map { SafeSQLEvidence( operation: $0.operation.rawValue, parameterizedSQL: $0.parameterizedSQL, parameterCount: $0.parameters.count, elapsedMicros: $0.elapsedMicros, resultCount: $0.resultCount, affectedRows: $0.affectedRows, resultSummary: $0.resultSummary) } } ``` Use `enableAll()`, `enableSelect()`, `enableMutation()`, and `disable()` on the evidence store. Mode changes clear previous entries. Raw `SQLExecutionMetadata.parameters` remain trusted-boundary data. Every generated query still requires non-empty `comment(...)` and `purpose(...)`; every mutation requires `auditAs(...)`. Preserve not-found, checker, optimistic-conflict, and provider failures. Query and mutation logs and `TextDiagnosticSQLLogSink` are enabled by default. The sink is available as the trusted context's `diagnosticSQLLogSink`. Set `context.querySQLLogEnabled` and `context.mutationSQLLogEnabled` independently. Each metadata entry retains structured comment, purpose, audit reason, typed multi-level trace, parameterized SQL, copy-paste `debugSQL`, elapsed time, result count, and affected rows. Never attach rendered SQL to ordinary telemetry or responses. --- ## TeaQL seven-language assist contract Apply the verified Rust semantic ceiling while using only the exact SWIFT generated and runtime APIs. Discover APIs through the generated application AGENTS.md and progressive model-aware Assist. Do not inspect generated domain-library source. - Do not create plurals by appending `s` or `es`; use the centralized generated plural. - Human and non-human entities use different generated predicate vocabularies. Preserve forms such as “who are active” and “whose email is”; never infer them from English. - Configure filters, projection, paging, and other query options before `purpose(...)`. Comment may appear anywhere in the chain. Purpose enters the executable stage; execution requires both values, but comment does not have to immediately precede purpose. - Every execute/list/stream and every save accepts exactly one context argument: `UserContext`. Name that argument `context`, never `runtime`; data services and global policy are injected when the context is built. Reserve `runtime` for process-level runtime ownership, provider/pool setup, and module assembly. - Tenant, merchant, identity, permissions, request policy, purpose policy, hard limit, and continuous-page cursor policy come only from trusted context, never dynamic JSON or TFP. - If the required operation is absent after current entity/action and required field Assist, stop that path and report MISSING_ASSIST. Do not guess an API or search the generated library as a fallback. - Create each application-owned source file once. After its first compile attempt, repair only the smallest block identified by the exact compiler or test diagnostic. Preserve unrelated code; do not rewrite the complete file as an error-recovery loop. - Before a repair that would replace more than 25% of an existing application file, stop and report LARGE_REWRITE_REQUEST with the file, exact diagnostic, reason, and estimated scope. Initial creation and model-driven regeneration are not repairs. Capability: `debug`. - Capture purpose, comment, trace/correlation id, parameterized SQL summary, duration, row count, provider, and the runtime's native response when available. - Preserve the immutable row audit event and the customizable App Audit Sink as separate paths. Redact credentials, tokens, connection strings, and customer data. - Document only switches and hooks present in the selected runtime source.