ONE BUG. A VISIBLE CHAIN OF EVIDENCE.
A fix you can
trace and review.
Replay a real output bug, compare the genuine GitLab Duo fix, and follow its issue, draft review, passing CI and approved merge.
- 01 Reproduce
- 02 Duo fix
- 03 Regression + CI
- 04 Human review
01 / REPRODUCIBLE REPORT
One character.
Broken across two pages.
The original algorithm could split an emoji across pages. Replay that historical behavior, then switch to the actual Duo-fixed production code. Both process your sample locally.
Text stays in this browser. Use a public example; downloaded reports include the entered text.
02 / GITLAB DUO
The agent does the fix.
An authorized maintainer started Developer Flow from issue #2. The genuine Duo session inspected the source and changed only pagination logic.
MR !2 was opened as Draft with auto-merge off. All 51 original tests passed at fix HEAD 010b79fb. After explicit user approval, the fix and audited foundation were manually merged. The first main verification and Pages deployment passed.
Prepare another reviewed issue in GitLab ↗
Opens GitLab with the report text. Review and submit there using your own authorized account. This does not start an agent.
Open public source and CI history ↗03–04 / EVIDENCE GATE
Check a future draft.
The historical run above is complete. For another run, import an exact-HEAD snapshot from the read-only collector while its MR is still Draft. This local checklist does not approve a merged MR. The file is not uploaded.
Duo provenance and code review require explicit human attestations. The review desk cannot merge.