chore(gha): add linear-merge-master.yml GitHub workflow

[ms-bot]

Why is this needed?

This pull request has been created by a robot to add the linear-merge-master.yml GitHub workflow.

[Copilot]

Pull request overview

Adds a new GitHub Actions workflow intended to run on pushes to master and update Linear issue state after merges, aligning with this repo’s mobsuccessbot-managed policy workflow setup.

Changes:

• Introduces .github/workflows/linear-merge-master.yml to trigger on push to master.
• Adds a single job that runs mobsuccess-devops/github-actions-linear with Linear/GitHub credentials.
• Configures concurrency/cancellation behavior for the job.

---

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

[maximus-agents]

Auto-Approved ✅

Change Summary

Automated GitHub Actions workflow sync adding linear-merge-master.yml; generated PR was left unchanged in response to Copilot policy comments, which were explained and resolved as upstream-policy work.

CI Checks

All required non-Linear checks passed.

Breaking Changes

None detected.

Linear Ticket

No Linear check is present on this repository/PR.

[maximus-agents]

🤖 fix-approve-merge report

Outcome: MERGED ✅
PR type: BOT_PR
Head commit: b52488f

What was done

• Reviewed the generated workflow-sync PR without editing its generated files.
• Replied to and resolved both Copilot review threads; the requested policy changes were identified as upstream-policy work.
• Verified all required non-Linear checks passed.
• Approved the PR.
• Merged the PR (squash) — merge commit 1447f52790ab6e55b2a4431429d3c9b4f1779cb3.

CI

All required non-Linear checks passed before merge (Eslint, Mobsuccess PR Compliance, PackageJsonLint, Prettier, Sort Package Json, Test, Validate YAML files).

Linear

No Linear check was present on this repository/PR; no ticket was linked in the title.

Why it stopped here

Completed successfully.