bug(wave-pattern): GitLab wave::N labels and phases-waves.json issue lists can disagree — pick one as authoritative or surface drift

[bakeb7j0]

Summary

GitLab wave::N labels (PM-layer issue labels) and phases-waves.json (wave-status internal source of truth) can drift. Concrete example reported: issue #260 had wave::5 label but appeared in the wave-3 plan in phases-waves.json. There's no enforcement reconciling the two.

Two valid resolutions:

1. Pick one as authoritative. Likely phases-waves.json (since the pipeline reads it). wave::N labels become cosmetic / informational, and a reconciler regenerates them on wave_init / wave_complete.
2. Surface drift loudly. Add a wave_reconcile (or extend the existing one) that compares the two sources and flags mismatches in a structured event before the wave starts.

Severity: low — silent drift; no operational failure, but creates ambiguity for human PMs reading the project board vs operators reading the pipeline.

Origin: Reported by sibling-campaign agent. @Scryer to expand and pick the resolution.

Implementation Steps

TBD — @Scryer to expand.

Test Procedures

TBD.

Acceptance Criteria

• Either: wave::N labels regenerated from phases-waves.json on init/complete (informational, drift impossible), OR drift surfaced via wave_reconcile with structured event + Discord notice
• Documentation: which source is authoritative, what the other source is for

Dependencies

• None hard. Could touch mcp-server-sdlc (wave_reconcile) and/or cc-workflow (skill body).

Metadata

Severity: severity::minor
Origin: sibling-campaign tracker. @Scryer owns expansion.