Verify package-lock.json has no conflict markers; explain dirty merge state in PR #46

[Copilot]

PR #46 (index → main) shows mergeable_state: dirty because both branches independently modified the version field — main at 1.0.7, index at 1.0.9. The comment showed what that conflict would look like if resolved manually.

Findings

• package-lock.json and package.json on copilot/sub-pr-46 and index are already clean — no conflict markers, version 1.0.9
• The conflict is a Git merge conflict at the branch level, not literal <<<<<<< markers inside any file
• bin/index.js already has the spinner fix (if (spinner) spinner.stop() before error output in the child.on("error") handler)

Resolution Required

The index → main conflict must be resolved by rebasing index onto main (or a manual merge commit), keeping 1.0.9 as the authoritative version. No file-level changes are needed in this PR.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.