ios-runtime-forensics-workflowlisted

# iOS Runtime Forensics Workflow ## Purpose Provide two explicit evidence modes for a reproducible iOS Simulator issue: `performance-trace` for focused ETTrace/symbolicated latency or CPU work, and `memory-graph` for retained-object and leak ownership analysis. This skill owns evidence shape, not normal app build, launch, or UI driving. ## When To Use - Use `performance-trace` for launch/runtime latency, CPU-heavy stacks, or comparison traces. - Use `memory-graph` for leaks, retain cycles, memory growth, or objects that should release after a known interaction. - Route simulator discovery, build, install, launch, logs, screenshots, and UI driving to `xcode-build-run-workflow`. ## Single-Path Workflow 1. Apply the Apple docs gate through `explore-apple-swift-docs`. Confirm the current Xcode/Simulator evidence mechanism before acting. 2. Define one reproduction, start/stop boundary, target app build, simulator UDID, OS, Xcode version, and expected release or latency behavior. 3. Select exactly one mode: `performance-trace` or `memory-graph`. Do not mix CPU and ownership conclusions in one unsupported capture. 4. For `performance-trace`, read `references/performance-trace-evidence.md`, capture a focused trace with matching symbols, and identify hot stacks only after symbolication. 5. For `memory-graph`, read `references/memory-graph-evidence.md`, drive the release-producing flow, capture a memgraph, inspect app-owned retained types, and follow ownership evidence to the ret