fix: sync standards from v2, not main

[jcant0n]

.github/workflows/sync-standards.yml held two defaults for the same value, and they disagreed:

	value	who uses it
workflow_dispatch.inputs.ref.default	"v2"	manual runs from the UI
with: ref: ${{ github.event.inputs.ref || 'main' }}	'main'	schedule runs — cron supplies no inputs

So a manual sync read evergine-standards@v2 and the monthly cron read @main, and this repository ended up with whichever branch had spoken last. That is what flipped LICENSE between Copyright (c) 2026 and Copyright (c) 2025 month after month — the copyright year was the visible symptom, not the bug.

main in evergine-standards has not moved since 2026-03-19; v2 is twenty commits ahead and is the branch this workflow already pins for the reusable itself (_sync-standards-reusable.yml@v2). Reading v2 is what the dispatch default already intended.

Upstream companions: EvergineTeam/evergine-standards#4 fixes the same line in the template, EvergineTeam/evergine-standards#3 aligns main's licence year so neither branch can reintroduce the flip. This edit is needed here separately because sync-standards.yml is not listed in sync-manifest.json — the sync never rewrites a consumer's own workflow.

🤖 Generated with Claude Code

[github-actions]

API gate: additive

Every symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.

Target framework	Added	Removed
net10.0	+0	-0

_{Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal.}