Enhance Cursor setup and improve npm publishing workflow

[Fafoooo]

This pull request extends and improves the backup and restore support for the Cursor editor, making user-level settings, keybindings, and snippets portable across machines, and clarifies documentation and logic for all supported tools. The changes also update the npm publishing workflow and improve documentation for users.

Cursor Editor Backup/Restore Enhancements:

• Added support for capturing and restoring Cursor's application User data (settings, keybindings, snippets) by introducing a new cursor/user root in the backup repo, and updated the path logic and documentation accordingly. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Updated the backup manifest and README generation to document the new Cursor User data directory, and improved the .gitignore logic to scope denylisted patterns under all owned data roots. [1] [2] [3]
• Changed the restore logic to read all frozen roots for a tool (not just <tool>/files), ensuring Cursor User data is restored alongside other config. [1] [2] [3] [4]

Documentation & Usability Improvements:

• Updated the README to clarify what is captured for Cursor, how shared instructions are handled, and what is excluded from backups.
• Clarified and simplified the tool selection logic for restore: now, all tools present in the repo are restored by default unless narrowed with --tools. [1] [2]

Build & Publishing Workflow:

• Updated the npm publish workflow to use the latest npm version and to publish with provenance for improved supply chain security. [1] [2]

Internal Codebase Improvements:

• The backup command now reads the package version dynamically, ensuring metadata is always in sync.
• Refactored tool wiring and planActions logic to treat Cursor uniformly with other adapters, improving code maintainability. [1] [2] [3]

These changes make the backup and restore process more robust, especially for Cursor users, and improve clarity for both users and developers.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bbc55cbf5c

ℹ️ 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".