Obstacle: Release commit pattern creates noise and suggests fragile triggering

[amaralc]

Obstacle Description

The release commit pattern ([skip-github-pipeline]) combined with repeated release/revert commits clutters the git history. This suggests the release triggering mechanism is fragile and prone to false starts.

Why It Blocks Progress

Noisy commit history and frequent reverts indicate an unreliable release process. Developers cannot trust that merging a PR leads to a clean, predictable release, which undermines confidence in automation.

Suggested Experiments

• Analyze recent release commits to identify the root cause of false starts
• Design a robust trigger mechanism that eliminates the need for skip markers

[linear]

PEE-28