One real connection
A full-stack repo needs your UI to talk to code you wrote on the server side.
For a weekend project, one useful API route is enough. It can list events, save feedback, check a coupon, or return a user profile.
What counts
Do not call only a public API from the browser and call it full-stack. That can be a good feature, but it does not prove you built a backend.
Your own API route should sit inside your repo. The frontend should fetch it. The page should show data that came from that route.