Align package manager artifacts with npm docs and confirm checklist path clarity

[Copilot]

Pull request

Proposed changes

The template currently documents npm-based setup while still carrying a pnpm-lock.yaml, which creates mixed package-manager signals. This change removes the pnpm lockfile and confirms the checklist already uses the explicit .github/ISSUE_TEMPLATE/config.yml path.

• Issue coverage

  • Removed package manager inconsistency by deleting pnpm-lock.yaml.
  • Verified no README change needed for checklist file path: it already points to .github/ISSUE_TEMPLATE/config.yml.

• Repository delta

  • Deleted: pnpm-lock.yaml

• Example (artifact alignment)

  - pnpm-lock.yaml

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

---

🔒 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.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.