v2.1.0: Replace FDA with Bookmark permissions, fix issues #128 & #129, simplify localization

.claude/settings.local.json

@@ -29,7 +29,8 @@
       "Bash(/usr/bin/log show *)",
       "Bash(xcodebuild -project RClick.xcodeproj -scheme RClick -destination 'platform=macOS' build)",
       "WebSearch",
-      "WebFetch(domain:stackoverflow.com)"
+      "WebFetch(domain:stackoverflow.com)",
+      "Bash(pluginkit *)"
     ]
   }
 }

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,42 @@
+---
+name: Bug Report
+about: Report a bug to help us improve RClick
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Describe the Bug
+
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+
+1. Open Finder, right-click on ...
+2. Click on '...'
+3. Observe '...'
+
+## Expected Behavior
+
+A clear description of what you expected to happen.
+
+## Screenshots
+
+If applicable, add screenshots to help explain the problem.
+
+## Environment
+
+| Detail | Value |
+|--------|-------|
+| **RClick Version** | [e.g. 2.0.4] |
+| **macOS Version** | [e.g. 15.6] |
+| **Mac Model** | [e.g. MacBook Pro M3] |
+| **Installation Method** | [DMG / Built from Source] |
+
+## Additional Context
+
+- Does the issue persist after restarting the app?
+- Does the issue persist after a system restart?
+- Does the issue occur with specific file types or in specific folders?
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,35 @@
+---
+name: Feature Request
+about: Suggest a new feature or enhancement for RClick
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Problem Statement
+
+A clear description of the problem you want to solve.
+*e.g., "I often need to convert images to PNG format, and going through Preview each time is cumbersome."*
+
+## Proposed Solution
+
+Describe the feature or enhancement you'd like to see.
+*e.g., "Add a right-click action to convert selected images to PNG directly in Finder."*
+
+## Alternatives Considered
+
+Have you considered any workarounds or alternative solutions?
+
+## macOS Integration
+
+How should this feature integrate with macOS?
+- Finder context menu only?
+- Menu bar interaction?
+- Keyboard shortcut?
+- Settings configuration?
+
+## Additional Context
+
+- Would this feature require new permissions? (e.g., Accessibility, Full Disk Access)
+- Are there existing macOS APIs that could support this?
+- Add any other context, mockups, or references here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,57 @@
+## Summary
+
+<!-- Briefly describe what this PR does and why -->
+
+## Type of Change
+
+- [ ] 🐛 Bug fix
+- [ ] ✨ New feature
+- [ ] 📝 Documentation update
+- [ ] ♻️ Refactoring
+- [ ] ⚡ Performance improvement
+- [ ] 🔧 Build/CI change
+- [ ] 🧪 Test addition/update
+
+## Related Issue
+
+<!-- Link to the issue this PR addresses, e.g., "Closes #123" -->
+
+## Screenshots
+
+<!-- If your change affects the UI, include before/after screenshots -->
+
+| Before | After |
+|--------|-------|
+|        |       |
+
+## Testing
+
+### Manual Testing
+
+<!-- Describe the steps you followed to verify your changes -->
+
+- [ ] App launches and appears in menu bar
+- [ ] Right-click menu works correctly in Finder
+- [ ] Dark mode looks correct
+- [ ] Settings persist across restarts
+- [ ] FinderSync extension loads properly
+
+### Build Verification
+
+```bash
+# Paste the output of:
+xcodebuild -project RClick.xcodeproj -scheme RClick -destination 'platform=macOS'
+```
+
+## Checklist
+
+- [ ] My code follows the project's Swift 6.2 conventions (see [CONTRIBUTING.md](CONTRIBUTING.md))
+- [ ] All UI is SwiftUI (no AppKit UI components)
+- [ ] I have tested on macOS 15.6+
+- [ ] I have tested with both light and dark mode
+- [ ] I have updated documentation if needed
+- [ ] My branch is up-to-date with `dev`
+
+## Additional Notes
+
+<!-- Any other context the reviewer should know -->

CHANGELOG.md

@@ -0,0 +1,103 @@
+# Changelog
+
+All notable changes to RClick are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/).
+
+## [2.1.0] - 2026-07-12
+
+### Changed
+- Replace Full Disk Access (FDA) with Security-Scoped Bookmark permission model
+- File operations (delete, create, hide, unhide, AirDrop) now prompt for per-folder authorization
+- Settings: "Full Disk Access" row replaced with "Folder Permissions" management
+
+### Removed
+- Full Disk Access detection, guide alert, and settings UI
+- `PermissionChecker.hasFullDiskAccess()` and related FDA methods
+
+## [2.0.4] - 2026-07-05
+
+### Fixed
+- Add sandbox entitlement for FinderSyncExt to fix menu rendering in protected directories
+- Set proper icons for collapsed parent menus in FinderSync
+- Isolate DMG and ZIP staging into separate subdirectories to prevent artifact corruption
+- Prevent nested `.app` in release ZIP caused by stale DMG temp copy
+
+### Changed
+- Bump `actions/checkout` from v4 to v5 in CI workflows
+
+## [2.0.3] - 2026-07-04
+
+### Fixed
+- Preserve `.app` bundle structure in release ZIP archive
+- Use `cp` + `ditto` + `keepParent` for correct `.app` ZIP packaging
+- Avoid nested `.app` in release ZIP and DMG artifacts
+- Remove stale "Create Blank File" menu item; add missing localization entries
+
+### Added
+- CI: GitHub Actions workflows for PR build verification and tag-triggered release
+
+### Changed
+- Select latest available Xcode version on CI runner
+- Lower `objectVersion` for Xcode 26.0.1 CI compatibility
+
+## [2.0.1] - 2026-06-28
+
+### Added
+- Trilingual localization with String Catalogs (zh-Hans, en, ja)
+- Editable blank file creation from templates
+- Draggable settings menu ordering for customizing menu appearance
+- Quick-access folders master toggle (default off)
+- CI: Add GitHub Actions workflows for PR build and tag release
+
+### Fixed
+- FinderSync menu click unresponsiveness after localization refactor
+- Sandbox permission issues for FinderSync Extension
+- VS Code detection with percent-encoded path double-encoding
+- Toolbar icons disappearing after settings refactor
+- Heartbeat monitoring logic for extension health checks
+- Menu item default values and collapse toggle not applying correctly
+- Chinese menu title truncation in Finder context menu
+- Common folders icon not matching system directory appearance
+- Dark mode icon adaptation for SF Symbols using `paletteColors`
+- File type icon three-level fallback strategy
+- `onChange(of:)` deprecation warning on macOS 14+
+
+### Changed
+- Swift 5 → Swift 6.2 migration with full concurrency checking
+- Settings UI refactored to unified `Form` layout
+- macOS 15.6 + Xcode 16.4 compatibility as minimum requirement
+- Menu icon loading now uses memory cache for instant display
+- New file icons prioritize system app icons when available
+- FDA (Full Disk Access) permission guidance and detection
+
+### Performance
+- Menu icon loading now uses memory cache for instant display on subsequent right-clicks
+
+## [1.7.2] - 2025-09-27
+
+### Changed
+- Code signing and entitlements configuration for FinderSync Extension
+- Improved extension loading reliability
+
+## [1.7.0] - 2025-09-27
+
+### Added
+- Initial stable release with core Finder context menu features
+- Open with External App support
+- Copy Path functionality
+- Delete Directly (bypass Trash)
+- Hide / Unhide file toggle
+- AirDrop sharing
+- Create New Files from templates
+- Quick Access Folders
+- Dark Mode support
+
+---
+
+[2.0.4]: https://github.com/wflixu/RClick/releases/tag/v2.0.4
+[2.0.3]: https://github.com/wflixu/RClick/releases/tag/v2.0.3
+[2.0.1]: https://github.com/wflixu/RClick/releases/tag/v2.0.1
+[1.7.2]: https://github.com/wflixu/RClick/releases/tag/v1.7.2
+[1.7.0]: https://github.com/wflixu/RClick/releases/tag/v1.7.0

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at the GitHub
+repository via private message to the maintainers.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations