Keep the formatters away from the generated XCFramework

[HituziANDO]

Summary

• Move the lint-staged configuration to .lintstagedrc.cjs so staged file lists can be filtered, and drop the lint-staged key from package.json
• Skip any staged path under Framework/SwiftyUpdateKit.xcframework/, and run no command at all when nothing else remains
• Record the constraint in AGENTS.md so the globs are not widened again

Root cause

The globs in package.json matched every .h in the repository, including the generated headers inside Framework/SwiftyUpdateKit.xcframework. Committing a regenerated artifact therefore ran uncrustify over those headers, which realigned their #define directives and reordered their #include lines. Because the rewrite happened after build.sh signed the bundle, codesign --verify then reported the files as modified.

This was hit while preparing 1.5.1: the first release commit contained a corrupted, invalidly signed XCFramework. It was repaired before tagging by restoring the headers from the archive output and re-signing.

Validation

• Staged one badly formatted header inside the XCFramework and an identical one outside it, then ran npx --no-install lint-staged: the first was left byte-identical, the second was formatted
• codesign --verify on Framework/SwiftyUpdateKit.xcframework reports valid on disk and satisfies its Designated Requirement
• No source or test target is affected, so the test suite was not exercised for this change

Notes

The formatters are unchanged; only the file lists they receive are filtered.