bug(wavemachine): terminal-event surface degraded by overlapping bugs — operator visibility silently broken across a happy-path run

[bakeb7j0]

Summary

The /wavemachine skill specifies a "terminal events" surface — Discord embed updates with .status-panel.html attachments at every PASS/FAIL/BLOCKED/INTERRUPT/GATE-PASSED transition — that is degraded in practice because of overlapping bugs in the upstream tooling. None of the terminal events fired their full intended surface during my Plan #74 run, even on the all-green happy path. The cumulative effect is a measurable operator-experience gap distinct from any single underlying bug.

Where the surface degrades

Event	Spec says	Actual in my Plan #74 run
wave_complete per wave	regenerate panel + fire-and-forget Discord embed	panel regen errored on phase['name'] (#617); discord-status-post script not found at expected path; only the plain-text Discord post landed
Kahuna gate-passed	regenerate panel + plain text + Discord embed update	same — panel partial, embed update path silent
Per-wave bus cleanup	call wave-cleanup <wave-root>	rejected on 4-segment GitLab nested namespace path (#618); manual rm -rf required
Wavemachine-complete	terminal Discord post w/ .status-panel.html attached + vox	partial panel HTML attached; vox not invoked; otherwise functional

The plain-text Discord posts and the gauges/state.json transitions all worked. The "live embed update + attachment + panel regen" tier is the part that's broken.

Why a separate issue

Each underlying cause is filed:

• bug(generate-status-panel): KeyError 'name' — generator hard-codes phase['name'] but plans use 'title' #617 — panel KeyError: 'name' blocks regeneration
• bug(wave-cleanup): rejects GitLab nested-namespace wave-root paths (>2 segments) #618 — wave-cleanup rejects nested-namespace paths
• (existing) — discord-status-post script absent / unreachable from the orchestrator's CWD in this project layout

But the cumulative experience — "the entire terminal-event surface that the operator was promised is silently degraded across a successful run" — is a meta-observation that doesn't fit cleanly under any single child bug. This issue is a tracking parent so:

• The operator-facing "did the wavemachine actually communicate completion?" question has one place to land
• The fixes for bug(generate-status-panel): KeyError 'name' — generator hard-codes phase['name'] but plans use 'title' #617/bug(wave-cleanup): rejects GitLab nested-namespace wave-root paths (>2 segments) #618/discord-status-post can be cross-linked here as they merge
• A regression test that exercises the full terminal-event surface end-to-end (against a multi-namespace GitLab fixture) lives somewhere

Severity

severity::minor per individual symptom; cumulatively, the operator's entire visibility surface is degraded for the duration of a wavemachine run. On a happy path that's annoying. On a gate-blocked path where the operator is supposed to triage from the attached panel, it could be confusing.

Acceptance Criteria

• /wavemachine end-to-end test against a multi-segment GitLab namespace fixture exercises every terminal-event surface and asserts:
  • panel regenerates without exception
  • wave-cleanup accepts the wave-root path
  • discord-status-post resolves and runs successfully (or at least fails loudly if the script isn't present)
• Each child bug (bug(generate-status-panel): KeyError 'name' — generator hard-codes phase['name'] but plans use 'title' #617, bug(wave-cleanup): rejects GitLab nested-namespace wave-root paths (>2 segments) #618, the discord-status-post path resolution) closed with reference to this parent.
• /wavemachine skill body's "Status Panel Lifecycle" and "Announcements" sections updated if any contract changes during the fix.

Dependencies

• Blocks: clean operator UX on every /wavemachine run on a GitLab nested-namespace project.
• Blocked-by: bug(generate-status-panel): KeyError 'name' — generator hard-codes phase['name'] but plans use 'title' #617, bug(wave-cleanup): rejects GitLab nested-namespace wave-root paths (>2 segments) #618, and a separate discord-status-post resolution fix.