chore: untrack generated example targets and align swiftlint paths

- ignore apps/example/targets as generated prebuild output to reduce churn
- remove tracked example target artifacts from version control
- point VS Code and pre-push lint command to TestHarness SwiftLint binary
- document one-time pod install setup in CONTRIBUTING

Author: thisislvca

.gitignore

@@ -39,6 +39,7 @@ android.iml
 # Example native output (CNG)
 apps/example/ios/
 apps/example/android/
+apps/example/targets/
 
 # Cocoapods
 #

.vscode/settings.json

@@ -1,5 +1,5 @@
 {
   "cSpell.words": ["Triggerable"],
-  "swiftlint.path": "apps/example/ios/Pods/SwiftLint/swiftlint",
+  "swiftlint.path": "packages/react-native-device-activity/ios/TestHarness/Pods/SwiftLint/swiftlint",
   "swift.SDK": "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.2.sdk"
 }

CONTRIBUTING.md

@@ -22,6 +22,7 @@ If these variables are missing, `app.config.ts` falls back to stable defaults fo
 ## Example app follows CNG
 
 The example app no longer tracks `apps/example/ios` and `apps/example/android`.
+The example target folder `apps/example/targets` is also generated during prebuild and should not be committed.
 
 Regenerate native folders when needed:
 
@@ -43,6 +44,25 @@ The iOS test runner lives in:
 
 - `packages/react-native-device-activity/ios/TestHarness`
 
+## SwiftLint setup
+
+The repository runs SwiftLint from the iOS test harness CocoaPods installation:
+
+- `packages/react-native-device-activity/ios/TestHarness/Pods/SwiftLint/swiftlint`
+
+Run this once after cloning (and again if Pod dependencies are cleaned):
+
+```bash
+cd packages/react-native-device-activity/ios/TestHarness
+pod install
+```
+
+Then run repository checks from the root:
+
+```bash
+bun run pre-push
+```
+
 ## Plugin testing
 
 In addition to app/prebuild validation, config plugin regression tests are defined under: