Add workflow_dispatch to CI workflows for manual fork triggering

[Copilot]

CI workflows could not be manually triggered from forked branches — test.yml and playwright.yml only fired on push/pull_request events scoped to upstream branches, with no workflow_dispatch hook.

Changes

• .github/workflows/test.yml — added workflow_dispatch: trigger
• .github/workflows/playwright.yml — added workflow_dispatch: trigger

Fork owners can now go to Actions → (workflow) → Run workflow and manually execute either pipeline against any branch in their fork.

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

workflow_dispatch was absent from both CI workflows. Without it, there is no way to manually invoke them — only automated push/pull_request events on upstream-tracked branches would fire them.

Impact of Change

• Users: Fork contributors can now manually trigger CI without opening a PR to upstream.
• Developers: No API or code changes.
• System: workflow_dispatch requires write access to the repo (or fork owner in their own fork) — no secrets exposure risk.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Contributors

Screenshots/Videos

---

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