[codex] Bump package version to 0.6.1 after #61

[satvik007]

Summary

This is a small follow-up to #61, which merged the Playwright upload mapping fixes into main on April 6, 2026.

This PR bumps the package version to 0.6.1 and aligns the root package metadata in package-lock.json with the published package version.

Why this follow-up is needed

PR #61 delivered the functional fixes, but the repository version metadata was still left at 0.6.0 in package.json, and the root metadata in package-lock.json was even older at 0.4.6.

Leaving that state in place would make the next publish ambiguous and could cause the release metadata to misrepresent what is actually on main.

What changed

• Bumped package.json from 0.6.0 to 0.6.1
• Updated the root package-lock.json package version fields from 0.4.6 to 0.6.1
• Kept the change set intentionally narrow: no source, parser, uploader, or test logic changes

User and release impact

• The next npm release can be cut as 0.6.1, clearly marking it as the follow-up release that includes the fixes merged in Fix incorrect Playwright upload mapping to QA Sphere runs #61
• package.json and package-lock.json will now agree on the package version at the repository root
• There is no runtime behavior change in this PR by itself

Validation

• npm run check

Notes

• Base branch: main
• Follow-up to: Fix incorrect Playwright upload mapping to QA Sphere runs #61

[claude]

Claude finished @satvik007's task in 1m 22s —— View job

---

Review complete

Approved — clean version bump with no issues. package.json (0.6.0 → 0.6.1) and package-lock.json (0.4.6 → 0.6.1) are now aligned.

[claude]

LGTM. Clean version bump — package.json (0.6.0 → 0.6.1) and package-lock.json (0.4.6 → 0.6.1) are now aligned. No code changes, no issues.

[gemini-code-assist]

Code Review

This pull request updates the version of the qas-cli package to 0.6.1 in both package.json and package-lock.json. I have no feedback to provide.