chore: rebrand to save-sync (Save Sync) and update references

[Copilot]

Rebrand repository from "Global Save State" (Global-Save-State) to "save-sync" (Save Sync). Updates all user-facing references while preserving compatibility.

Metadata changes

• package.json: name, displayName, description, version (→ 0.0.0), repository, homepage, bugs, engines.vscode (→ ^1.60.0)
• Publisher: VKrishna04 (unchanged per spec)
• Commands/config keys: Internal identifiers (globalSaveState.*) preserved for compatibility

Documentation updates (28 files)

• README.md replaced with simplified version + migration notice
• MIGRATION.md added
• All references updated: index.html, CONTRIBUTING.md, CHANGELOG.md, .github templates, wiki files, docs

Marketplace references

Badge and install URLs still reference VKrishna04.global-save-state (current published extension ID). Update these after republishing under new name.

Suggested repository topics

vscode, vscode-extension, savepoints, snapshots, saves, workspace, developer-tool

---

Note: Old repository path will redirect via GitHub. See MIGRATION.md for details.

Original prompt

Rebrand the repository Life-Experimentalist/Global-Save-State to the new name "save-sync" (display name: "Save Sync"). Create a new branch named rename/save-sync from main, make metadata and documentation updates, and open a pull request titled "chore: rebrand to save-sync (Save Sync) and update references". Commit message: "chore: rebrand to save-sync and update references".

Required changes (apply exactly as specified):

1. Replace README.md with the exact content below. Use a markdown file with the inner code block escaped as shown.

```markdown
# save-sync

save-sync — VS Code extension to create and manage working save points (project snapshots).

Note: This project was formerly named "Global Save State" (repo: Global-Save-State). The old name and repository path will continue to redirect, but this README and package metadata have been updated to reflect the new name "save-sync" (display name: Save Sync).

Quick summary
- Create lightweight project snapshots (save points) inside VS Code so you can return to previous working states quickly.
- Local, fast, and workspace-focused snapshots — useful for experiments, refactors, and risky changes.

Install
- Install from the VS Code Marketplace (when published) or install the .vsix file.

Quick start
1. Open the Command Palette (Ctrl/Cmd+Shift+P).
2. Run "Save Sync: Create save point" to save the current workspace state.
3. Run "Save Sync: Restore save point" to revert to a previously saved snapshot.

Notes for maintainers
- package.json's "name" and "displayName" fields should be updated to "save-sync" and "Save Sync" respectively.
- Ensure repository, bugs, and homepage URLs in package.json point to https://github.com/Life-Experimentalist/save-sync.

Contributing
- Please open issues or pull requests. Use the "enhancement" label for feature proposals.

License
- (Keep existing license; add SPDX identifier here.)
```

2. Update package.json metadata fields in-place (preserve other fields). The following snippet shows the updated metadata that must be applied to package.json while keeping all other keys unchanged (the agent should update fields in-place rather than replace unrelated content):

{
  "name": "save-sync",
  "displayName": "Save Sync",
  "description": "Create and manage lightweight save points (snapshots) for your VS Code workspace.",
  "version": "0.0.0",
  "publisher": "Life-Experimentalist",
  "repository": {
    "type": "git",
    "url": "https://github.com/Life-Experimentalist/save-sync.git"
  },
  "engines": {
    "vscode": "^1.60.0"
  }
}

• If package.json's existing "publisher" is not "Life-Experimentalist", do NOT change it; instead leave the existing publisher value and report it in the PR description.
• Update any homepage and bugs fields to use https://github.com/Life-Experimentalist/save-sync if present.

3. Add a new file MIGRATION.md at repo root with the exact content below (markdown escaped as shown):

```markdown
Migration: Renamed to save-sync

This repository has been renamed from "Global Save State" (Global-Save-State) to "save-sync" (Save Sync).

- Old repo name: Global-Save-State
- New repo name: save-sync

GitHub will keep redirects from the old repository URL, but please update any external links or package metadata that reference the old path.
```

4. Project-wide search-and-replace (docs, HTML, README, markdown, JSON files, meta and badges, and comments/documentation):

• Replace exact user-visible occurrences:
  • "Global Save State" -> "Save Sync"
  • "Global-Save-State" -> "save-sync"
• Apply replacements only to user-visible text (docs, README, HTML title/meta, markdown, JSON docs, comments). Do NOT rename source-code identifiers, variables, function or class names, or any binary files. If the old name appears in comments, update it to the new name.
• Update any README badges or shield URLs that reference the old repository path to point to https://github.com/Life-Experimentalist/save-sync.

5. Update HTML files in the project: replace title, meta tags, visible text and any links pointing to the old repo path to the new name and URL.

6. Update repository topics (via API or include in PR description a list of topics that should be set): ["vscode","vscode-extension","savepoints","snapshots","saves","workspace","developer-tool"]. If direct API access to topics is not performed, list them in the PR for maintainers to apply.

7. Ensure the migration note is visible in README and add MIGRATION.md file as specified.

8. Create the branch rename/save-sync from main and commit all changes. Commit message: "chore: rebrand to save-sync and update references".

9. Open a pull request with the following details:

• Title: "chore: rebrand to save-sync (Save Sync) and update references"
• Body: Short summary explaining the changes and noting the old publisher if different. Use this text as the PR body:

"This PR renames the exten...

This pull request was created as a result of the following prompt from Copilot chat.

Rebrand the repository Life-Experimentalist/Global-Save-State to the new name "save-sync" (display name: "Save Sync"). Create a new branch named rename/save-sync from main, make metadata and documentation updates, and open a pull request titled "chore: rebrand to save-sync (Save Sync) and update references". Commit message: "chore: rebrand to save-sync and update references".

Required changes (apply exactly as specified):

1. Replace README.md with the exact content below. Use a markdown file with the inner code block escaped as shown.

```markdown
# save-sync

save-sync — VS Code extension to create and manage working save points (project snapshots).

Note: This project was formerly named "Global Save State" (repo: Global-Save-State). The old name and repository path will continue to redirect, but this README and package metadata have been updated to reflect the new name "save-sync" (display name: Save Sync).

Quick summary
- Create lightweight project snapshots (save points) inside VS Code so you can return to previous working states quickly.
- Local, fast, and workspace-focused snapshots — useful for experiments, refactors, and risky changes.

Install
- Install from the VS Code Marketplace (when published) or install the .vsix file.

Quick start
1. Open the Command Palette (Ctrl/Cmd+Shift+P).
2. Run "Save Sync: Create save point" to save the current workspace state.
3. Run "Save Sync: Restore save point" to revert to a previously saved snapshot.

Notes for maintainers
- package.json's "name" and "displayName" fields should be updated to "save-sync" and "Save Sync" respectively.
- Ensure repository, bugs, and homepage URLs in package.json point to https://github.com/Life-Experimentalist/save-sync.

Contributing
- Please open issues or pull requests. Use the "enhancement" label for feature proposals.

License
- (Keep existing license; add SPDX identifier here.)
```

2. Update package.json metadata fields in-place (preserve other fields). The following snippet shows the updated metadata that must be applied to package.json while keeping all other keys unchanged (the agent should update fields in-place rather than replace unrelated content):

{
  "name": "save-sync",
  "displayName": "Save Sync",
  "description": "Create and manage lightweight save points (snapshots) for your VS Code workspace.",
  "version": "0.0.0",
  "publisher": "Life-Experimentalist",
  "repository": {
    "type": "git",
    "url": "https://github.com/Life-Experimentalist/save-sync.git"
  },
  "engines": {
    "vscode": "^1.60.0"
  }
}

• If package.json's existing "publisher" is not "Life-Experimentalist", do NOT change it; instead leave the existing publisher value and report it in the PR description.
• Update any homepage and bugs fields to use https://github.com/Life-Experimentalist/save-sync if present.

3. Add a new file MIGRATION.md at repo root with the exact content below (markdown escaped as shown):

```markdown
Migration: Renamed to save-sync

This repository has been renamed from "Global Save State" (Global-Save-State) to "save-sync" (Save Sync).

- Old repo name: Global-Save-State
- New repo name: save-sync

GitHub will keep redirects from the old repository URL, but please update any external links or package metadata that reference the old path.
```

4. Project-wide search-and-replace (docs, HTML, README, markdown, JSON files, meta and badges, and comments/documentation):

• Replace exact user-visible occurrences:
  • "Global Save State" -> "Save Sync"
  • "Global-Save-State" -> "save-sync"
• Apply replacements only to user-visible text (docs, README, HTML title/meta, markdown, JSON docs, comments). Do NOT rename source-code identifiers, variables, function or class names, or any binary files. If the old name appears in comments, update it to the new name.
• Update any README badges or shield URLs that reference the old repository path to point to https://github.com/Life-Experimentalist/save-sync.

5. Update HTML files in the project: replace title, meta tags, visible text and any links pointing to the old repo path to the new name and URL.

6. Update repository topics (via API or include in PR description a list of topics that should be set): ["vscode","vscode-extension","savepoints","snapshots","saves","workspace","developer-tool"]. If direct API access to topics is not performed, list them in the PR for maintainers to apply.

7. Ensure the migration note is visible in README and add MIGRATION.md file as specified.

8. Create the branch rename/save-sync from main and commit all changes. Commit message: "chore: rebrand to save-sync and update references".

9. Open a pull request with the following details:

• Title: "chore: rebrand to save-sync (Save Sync) and update references"
• Body: Short summary explaining the changes and noting the old publisher if different. Use this text as the PR body:

"This PR renames the extension to save-sync (Save Sync), updates package.json metadata, replaces user-visible occurrences of the old name, updates README and badges, and adds MIGRATION.md.

This project was formerly named Global Save State / Global-Save-State. GitHub will redirect the old repository path to the new one. Please verify package/publisher identifiers before publishing to the Marketplace. Repository topics suggested: [vscode, vscode-extension, savepoints, snapshots, saves, workspace, developer-tool]."

10. In the PR, include a short list of files changed and report any instances where the publisher in package.json was not "Life-Experimentalist" (if so, report the original value). Also report if any occurrences of the old name were found in source code identifiers that were intentionally not renamed.

Constraints and notes:

• Preserve other content in package.json; only change the specified metadata fields in-place.
• Do NOT change the extension publisher string. Do NOT change the extension identifier without confirmation.
• Only modify code identifiers if they are in comments or documentation; do not refactor source identifiers.

Deliverables:

• Branch rename/save-sync with the changes committed.
• A pull request opened against main with the title and body above.
• Files changed: README.md (replaced), package.json (metadata fields updated), MIGRATION.md (added), plus any other docs/HTML/markdown/JSON files updated to replace repository/name references.

If any step cannot be completed due to permission or other errors, report the exact error message and which step failed.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.