feat: implement device log capture support

[codegen-sh]

Summary

This PR implements device log capture support for iOS devices connected via USB, addressing the feature request from issue #54.

Changes Made

New Device Log Module (src/tools/device_log.ts)

• startDeviceLogCapture: Launches apps on iOS devices with console output capture using xcrun devicectl device process launch --console
• stopDeviceLogCapture: Stops log capture sessions and retrieves captured logs
• registerListDevicesTool: Lists available iOS devices with UUIDs and connection information
• Log file management: Automatic cleanup of old log files with 3-day retention policy

Tool Registration

• Added device log tools to IOS_DEVICE_WORKFLOW and DIAGNOSTICS tool groups
• Registered three new tools:
  • list_devices: Lists connected iOS devices with UUIDs
  • start_device_log_cap: Starts device log capture by launching app with console output
  • stop_device_log_cap: Stops capture and returns logs

Technical Implementation

The implementation uses the xcrun devicectl device process launch --console --device UUID bundleId command that was discovered by the user in issue #54. This approach:

• Launches the app on the device with console output capture enabled
• Streams both stdout and stderr to log files
• Provides session-based management similar to simulator log capture
• Includes proper error handling and cleanup

Usage Example

// 1. List available devices
await listDevices()

// 2. Start log capture (launches app with console output)
const session = await startDeviceLogCapture({
  deviceUuid: "723AD663-26E8-5EA8-8342-77E32B826F27",
  bundleId: "com.example.myapp"
})

// 3. Interact with the app on device

// 4. Stop capture and get logs
const logs = await stopDeviceLogCapture(session.sessionId)

Resolves

• Closes [Feature]: is it possible to run on the build on hardware devices like i can do it from xcode via wifi? #54 - Device log capture functionality for USB-connected iOS devices

Testing

• ✅ TypeScript compilation passes
• ✅ Build process completes successfully
• ✅ Tool registration follows existing patterns
• ✅ Error handling and validation implemented

---

💻 View my work • About Codegen

[codegen-sh]

I see a check failed - I'm on it! 🫡

💻 View my work

[codegen-sh]

✅ Fixed failing CI check in this commit

The issue was prettier formatting violations in the newly added src/tools/device_log.ts file. The CI was failing on the linting step because:

1. Inconsistent string formatting - Long template literals needed proper line breaks
2. Inconsistent spacing - Function parameters and object properties needed consistent formatting
3. Missing line breaks - Several long lines exceeded the prettier line length limits

Fix applied:

• Ran npm run lint:fix to automatically resolve ESLint/Prettier formatting issues
• Ran npm run format to ensure consistent code formatting
• Verified all checks pass: ✅ Build ✅ Lint ✅ Format check

The device log capture functionality remains fully intact - this was purely a code formatting fix to meet the project's style guidelines.

💻 View my work • React 👍 or 👎

[cameroncooke]

Fixed in #62

Got it, the fix is in PR #62! 👍

💻 View my work