Add Tuist support and Example project

[Kyle-Ye]

Summary

• Replace hand-maintained OpenAttributeGraph.xcodeproj with Tuist project generation (Project.swift)
• Add Example/ with minimal macOS commandLine app consuming OpenAttributeGraph via SPM
• Update build_xcframework.sh to auto-run tuist generate before archiving
• Add Tuist docs to README

Details

• Uses defaultSettings: .none so xcconfigs remain the single source of truth for build settings
• Uses Tuist 4.x API (Tuist struct, Tuist/Package.swift)
• Pins tuist 4.156.0 via mise.toml
• Fixes pre-existing missing return in GraphDescription.cpp for non-ObjC path

Verified

• tuist generate + xcodebuild build for macOS: BUILD SUCCEEDED
• Scripts/build_xcframework.sh: xcframework built for macOS, iOS, iOS Simulator
• Example/: tuist install && tuist generate succeeds

Test plan

• tuist generate --no-open && xcodebuild build -project OpenAttributeGraph.xcodeproj -scheme OpenAttributeGraph -destination "generic/platform=macOS" ENABLE_USER_SCRIPT_SANDBOXING=NO
• cd Example && tuist install && tuist generate --no-open
• Scripts/build_xcframework.sh

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 32.10%. Comparing base (2d5c015) to head (22af58d).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...s/OpenAttributeGraphCxx/Graph/GraphDescription.cpp	0.00%	1 Missing ⚠️

❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (70.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #224      +/-   ##
==========================================
+ Coverage   31.20%   32.10%   +0.90%     
==========================================
  Files          71       71              
  Lines        2628     2601      -27     
==========================================
+ Hits          820      835      +15     
+ Misses       1808     1766      -42     

Flag	Coverage Δ
ios	32.11% <0.00%> (+0.90%)	⬆️
macos	10.15% <ø> (ø)
ubuntu	12.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...s/OpenAttributeGraphCxx/Graph/GraphDescription.cpp	0.00% <0.00%> (ø)

... and 9 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[augmentcode]

🤖 Augment PR Summary

Summary: This PR replaces the checked-in Xcode project with Tuist-based project generation, and adds a minimal Example app to consume OpenAttributeGraph via SPM.

Changes:

• Removed the hand-maintained OpenAttributeGraph.xcodeproj from the repo and introduced root Project.swift / Tuist.swift for Tuist generation
• Added Example/ as a Tuist project with a macOS command-line target that imports OpenAttributeGraph
• Updated Scripts/build_xcframework.sh to run tuist generate before archiving for xcframework creation
• Documented Tuist-based Xcode generation/build steps in README.md
• Pinned Tuist (4.156.0) via mise.toml and adjusted .gitignore for generated artifacts
• Fixed a missing return path in GraphDescription.cpp when ObjC Foundation isn’t available

Technical Notes: Tuist generation uses defaultSettings: .none so the existing xcconfigs remain the source of truth for build settings.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

The sources/headers globs here will also match non-build files under these trees (e.g. Sources/OpenAttributeGraphCxx/include/OpenAttributeGraphCxx/Vector/vector.tpp and Sources/Utilities/include/SwiftBridging/README.md), which the previous Xcode project explicitly excluded. Could you confirm Tuist filters these out so they don’t end up in build phases or in the header-processing script’s inputs?

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}