[hamedtkd]

Summary

• Set the source, lockfile and Chrome MV3 manifest to v1.6.0 (no new permissions).
• Add v1.6.0 changelog, update README/source-release status and stale SESSION-HANDOFF version, and document browser/Jira acceptance gates.
• Extend the existing CI workflow for release/** branches: after all checks pass, archive contents of dist/, upload a QueueMint-release-candidate ZIP for clean-install testing.
• This release contains merged PR feat(worklog): export Jira descriptions and optional embedded screenshots #34 (full descriptions and opt-in image export) and feat: multi-issue Jira status moves, clearer five-column Worklog board, rich exports in Manage Jira #35 (bulk Jira status moves, Manage Jira export, selected-card drag, improved five-column board UX).

Validation

• Must pass: architecture cap, TypeScript typecheck, tests, Vite build, release audit and production dependency audit.
• Verify release-candidate artifact contains manifest.json at ZIP root and version is 1.6.0.
• Manual gate not yet satisfied: clean Chrome/Edge install, upgrade from v1.5.1, Jira-connected Worklog/Manage Jira move/export tests, and Capture regression checks. Record results before final release.

Release safety

• This PR prepares the source and QA artifact. It does NOT create or push v1.6.0 tag, publish a GitHub Release, or publish to Chrome Web Store.
• The existing tag workflow will publish a GitHub Release only after manual QA is approved and the version tag is created.
• Latest published version remains v1.5.1 until the release workflow completes.

Owner requested versioning and release preparation after authorizing PR merges.