Inspiration
Suede Shelf is an MIT-licensed storefront for AI shoppers. Payment and merchant-input changes deserve evidence a person can review. For Life After Code, Jason Colapietro of Suede AI / Suede Labs added a supervised GitLab Duo Agent Platform workflow to the existing app.
What it does
The workflow turns an issue into investigated code changes, regression tests, hosted CI and a reviewable merge request. GitLab Duo Developer reads AGENTS.md payment invariants, investigates defects and proposes fixes. Foundational Code Review supplies a second automated review. A person evaluates the outcome and controls release. This is Path B, Bring Your Own, and a supervised workflow.
How we built it
The original source is pinned to GitHub commit 1164355a14b9f49b75c5d9406f7e8a667f52bb53 under the MIT license. The existing Showcase started with a README. Duo could not fetch GitHub through its sandbox proxy, so we attached an archive of the exact tracked public source in the existing GitLab issue and verified its SHA-256 checksum. Recovery Developer session 9792363 imported it, found an IPv4-mapped IPv6 safeFetch bypass, committed a failing regression, fixed the classifier and opened MR !1.
Actual results
The initial hosted RED pipeline 2970277863 had 43 passing tests and one failing IPv6 regression. GREEN pipeline 2970283585 had 44 passing tests, typecheck and production webpack build success. Code Review session 9793063 then identified unsafe product links, stale label-gate semantics and documentation/build gaps. Developer session 9793207 remediated them on the same MR, adding URL and gate regression tests. Final pipeline 2970346843 at commit 2140966 passes 51 tests, typecheck, the shipped Turbopack build, a separate webpack build and the live current-MR-label advisory gate. Code Review session 9793741 confirmed six earlier issues resolved and requested deployment-specific ingress and gate evidence. After the exact inline evidence was supplied, final formal review 9795168 approved the MR. The actual gate trace confirms it ran on refs/merge-requests/1/head, queried current labels and succeeded.
Safety and limits
Cart prices come from the stored catalog; agents cannot provide payment amounts. Customer approval remains required before capture, and idempotency and limits remain intact. No real payment or completed capture was needed for this GitLab demonstration. Product links accept HTTP(S) only. DNS rebinding remains a documented limitation: this is not full SSRF isolation. Client-IP handling assumes trusted Vercel ingress that overwrites X-Forwarded-For; arbitrary appending proxies are unsupported.
The custom Payment Guard flow file is an uncreated, unenabled, unexecuted prototype. The demonstrated automation is the real foundational Developer and Code Review sessions plus hosted CI. The label gate is advisory: absence of a blocked label does not prove a review ran or completed.
What we learned
A passing agent runner is not evidence that application tests passed. We kept actual hosted CI results, failing regressions, review notes and limitations visible, and checked infrastructure claims against official documentation.
What is next
Validate the custom flow separately before enabling it; improve egress/IP-pinned transport before claiming stronger SSRF isolation. Preserve human review of payment-related changes.
Credits and evidence
Built by Jason Colapietro, Suede AI / Suede Labs. Narrated demo uses actual interface captures with disclosed synthetic narration.
- Complete public GitLab source branch
- Source and review history, MR !1
- Final five-job hosted pipeline
- Live gate trace
- Original MIT project
- Live storefront
Submission source and release state
The exact complete source and run instructions are on public branch duo/feature/2-suede-shelf-payment-guard at 214096632b51b5c713145bd3569a02a9b30ad0c6. GitLab detects the unchanged MIT license in the project About section. Duo formally approved MR !1 in final review session 9795168 after finding no remaining correctness or security issues. The MR remains open and unmerged; separate repository integration and production promotion have not occurred. No protection was bypassed. The supplied public storefront is the working in-period production deployment at original source 1164355. Reviewed 2140966 was separately staged in the same Vercel project and passed authenticated storefront/MCP/catalog smoke checks; that staged URL requires Vercel authentication and is not the public judging URL. Production promotion is not claimed.
Built With
- gitlab
- next.js
- node.js
- typescript
- vercel
