Copilot/clean up app features

[markcoleman]

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Maintenance/Refactoring
• 🔒 Security fix
• ⚡ Performance improvement
• 🧪 Test coverage improvement
• ♿ Accessibility improvement

Related Issues

Fixes #(issue)
Relates to #(issue)

Motivation and Context

Changes Made

How Has This Been Tested?

Test Configuration:

• Xcode Version:
• macOS Version:
• Device/Simulator:

Tests Run:

• Unit tests pass locally (swift test)
• UI tests pass (if applicable)
• SwiftLint passes without warnings (swiftlint)
• Code builds without warnings (swift build)
• Manual testing completed

Test Details:

Screenshots (if appropriate)

Checklist

Code Quality

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have checked my code and corrected any misspellings

Documentation

• I have made corresponding changes to the documentation
• I have updated the CHANGELOG.md (if applicable)
• I have added/updated API documentation comments

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Accessibility (if UI changes)

• VoiceOver labels are present and descriptive
• Dynamic Type is supported
• Color contrast meets WCAG AA standards
• Keyboard navigation works (macOS)

Security Considerations

• No security implications
• Security implications reviewed and addressed

Details (if applicable):

Breaking Changes

• No breaking changes
• Breaking changes documented below

Migration Guide (if needed):

Performance Impact

• No performance impact
• Performance improved
• Performance impact analyzed and acceptable

Details (if applicable):

Additional Notes

---

For Reviewers:

• Code reviewed
• Tests verified
• Documentation checked
• Security considerations reviewed
• Approved for merge

[github-actions]

⚠️ This PR is very large. Consider breaking it into smaller PRs for easier review.

PR Stats:

• Lines added: 1115
• Lines deleted: 2853
• Files changed: 27

Tips for large PRs:

• Break into smaller, focused PRs
• Ensure comprehensive test coverage
• Add detailed descriptions for each change

[github-actions]

⏱️ Build Performance Report

Metric	Time
Build	26s
Test	43s
Total	69s

Measured with SPM caching enabled.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b3106a50e1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Increase search depth beyond 14 moves

The new default search config caps bidirectional search at maxDepthPerSide: 7, so the solver can only prove solutions up to 14 moves, but many valid Rubik's Cube states require more (the known worst case is 20 moves). In practice this causes legitimate cubes to fail with noSolutionFound/searchLimitReached instead of returning a solution, which breaks normal solve flows for sufficiently scrambled inputs.

Useful? React with 👍 / 👎.