[Bug Backlog] Track defects and regressions across releases

[phamhungptithcm]

Purpose

Use this issue as the rolling backlog for defects, regressions, and unexpected behavior found while implementing or using gig.

What Belongs Here

• CLI behavior bugs
• repository discovery bugs
• Git adapter regressions
• promotion planning defects
• release automation or GitHub Pages failures
• documentation mismatches that cause incorrect usage

Working Rules

• convert concrete defects into dedicated bug issues when they are large enough to track separately
• link the bug to the relevant phase issue
• record reproduction steps, expected behavior, actual behavior, and impacted command or module
• close the checklist item here only after the dedicated fix is merged

Initial Bug Categories

• command parsing and help/usage regressions
• repository discovery false positives or false negatives
• ticket parsing or commit matching bugs
• branch comparison edge cases
• promotion flow safety bugs
• CI, release, or Pages deployment regressions