Checklist:

• I have read and followed the contribution guidelines.
• I have read and followed the how to open a pull request guide.
• My pull request targets the main branch of freeCodeCamp.
• I have tested these changes either locally on my machine, or GitHub Codespaces.

Same class of problem as #69574. The fetch stub in this lab fails camper code that passes against the live endpoint on production.

The object it resolved to only had a json method:

window.fetch = () => Promise.resolve({ json: () => Promise.resolve('Cats sleep for around 13 to 16 hours a day.') });

So a solution guarding the response, which is what campers are normally taught to write, always takes the error path because response.ok is undefined. The stub now resolves to something closer to a Response, with ok, status, statusText and text alongside json, and the fact itself moved to a variable so json and text cannot drift apart.

Unlike #69574, the resolution stays in a microtask here on purpose: __FakeTimers.install() runs in the same --before-all-- block, before the camper's code, so a stub resolving from a setTimeout would never settle unless a hint advanced the clock.

Verified locally with FCC_BLOCK=lab-digital-pet-game pnpm run test-curriculum-content.