Route iOS haptics across SwiftUI and UIKit

[sreejithraman]

What changed

• Keep ios-haptics as the shared tactile-feedback specialist and route both SwiftUI and UIKit iOS work to it.
• Replace its SwiftUI/iOS 26-only trigger with API-availability guidance for supported deployment targets.
• Rename the standard-feedback reference to cover both frameworks. Preserve the design, Core Haptics, and device-tuning guidance.

Why

The skill already taught UIKit generators and Core Haptics, but its description and SwiftUI routing excluded UIKit and apps targeting earlier iOS versions. That hid useful guidance and could prompt an unnecessary deployment-target change.

Effect

Agents can choose SwiftUI feedback, UIKit generators, or Core Haptics according to the app's target and the event, while animate continues to own visual motion.

Verification

• quick_validate.py passed for ios-haptics, swiftui, and uikit; git diff --check passed.
• The SwiftUI example typechecked with Xcode 27's iOS SDK targeting iOS 16.
• Final independent native and Gemini reviews found no substantive issues.
• No physical-device feel test was run; this PR changes agent instructions, not an app.