Fix Cursor Cloud setup notes to match the actual profile site

[kapersoft]

Summary

While setting up the development environment, I found the ## Cursor Cloud specific instructions section in AGENTS.md described a completely different application (a "Pinkary proxy" with PINKARY_USERNAME/PINKARY_BASE_URL, HTTP proxying, asset rewriting, and SQLite migrations). This repo is actually a tiny, stateless Laravel personal profile site (kaper.dev): a single GET / route rendering config/profile.php via a Blade view with inline CSS, plus a /up health endpoint. No database, Redis, queue, or Node/Vite is involved.

This PR rewrites that section to accurately reflect the real app.

Environment setup verified

• composer install (deps already vendored)
• php artisan key:generate
• vendor/bin/pint --test — passed
• composer analyse (PHPStan) — 0 errors
• php artisan test --compact — 4 passed / 23 assertions
• php artisan serve — GET / returns 200 with edge cache headers; /up returns 200

Walkthrough

kaper_dev_profile_walkthrough.mp4

Profile page rendered in-browser; scrolled through the Work/Contact link groups and clicked the GitHub link (opens github.com/kapersoft).

Full profile page with links

_{To show artifacts inline, enable in settings.}