GitHub reporting and approval

Product failures should first become an internal sanitized draft containing the affected release, reproducible steps, expected and observed behavior, impact, evidence and next safe action.

Every GitHub issue requires explicit owner approval for that specific issue before posting. A general improvement goal, earlier approval, scheduled review or phrase such as “log a ticket” does not authorize another issue. Show the final destination and draft, deduplicate existing drafts or issues, and record approved, denied or posted status.

If GitHub is unavailable or permission is denied, retain the internal draft and continue any unaffected authorized work. Never print or persist tokens in checkpoints, events, lessons or issue bodies.