Swift story
Swift surface discovery names the places teams usually ask about.
TraceMap can describe supported HTTP/API client surfaces, SwiftUI/UIKit-ish surfaces, package/dependency surfaces, and dynamic composition gaps as static evidence.
Public claim level: demo. Shipped capability anchor: PR #425. Demo-level rows need checked-in public-safe generated summaries before they become demo proof.
Use
Surface discovery is a review map, not observed behavior.
Network-adjacent codeHTTP/API client surfaces can help reviewers find static request-building or client-use evidence.
Public smoke proofThe real-world smoke proof names pinned public API-client samples and sanitized generated summaries.
UI-adjacent codeSwiftUI/UIKit-ish surfaces can show supported static UI declarations and labels without claiming rendered UI.
DependenciesPackage/dependency surfaces can name static package evidence without claiming vulnerability, license, freshness, or build compatibility analysis.
Boundary
Static surfaces are not runtime network or UI proof.
- Swift surface discovery is not runtime network reachability, rendered UI, complete navigation, user action proof, production traffic, endpoint performance, build success, deployment state, or release safety.
- TraceMap core scanning and reduction do not use AI impact analysis, LLM analysis, prompt-based classification, embeddings, or vector database analysis.
- Public pages must not publish raw source snippets, raw SQL, secrets, local absolute paths, raw remotes, credentials, stored values, private scan artifacts, or hidden validation details.
Proof path