RESCUE.md Convention

A standardized post-rescue report for AI project fixes.

When a Smith completes a rescue job, they add a RESCUE.md to the client's repository. It documents what was broken, what was fixed, and how to verify it — like a CHANGELOG.md for rescue work.

# Rescue Report

**Smith:** @alexsmith
**Date:** 2026-07-07
**Duration:** 3.5 hrs
**Package:** Auth Rescue

## What was broken
- `middleware.ts:L8` — session cookies lost on every request (wrong response object)
- `app/auth/callback/route.ts:L19` — missing `exchangeCodeForSession`, causing OAuth loop

## What was fixed
- Rewrote middleware with correct Supabase SSR response — commit `a1b2c3d`
- Added `exchangeCodeForSession` to callback route — commit `e4f5g6h`

## Verify it works
- [ ] Sign in with Google → stays logged in on refresh
- [ ] Visit /dashboard without auth → redirects to /login

*Rescued by [Smith](https://aismiths.cloud) — the AI project rescue marketplace.*

Why

• Clients get a clear audit trail — what broke, what changed, how to verify
• Future developers who find the repo understand what was rescued and why
• Every public RESCUE.md is a permanent backlink to Smith
• Smiths have proof of completed work linked to their profile

Quick start

As a Smith (adding to client repo):

npx rescue-report generate > RESCUE.md
git add RESCUE.md
git commit -m "docs: add rescue report (Smith job #<id>)"

Or copy the template and fill it in manually.

Spec

See SPEC.md for the full specification — required fields, conventions, and versioning.

Examples

• Auth Rescue — Google OAuth loop fix
• Payment Fix — Stripe webhook fix
• Security Audit — 6 security issues found and fixed

License

CC BY 4.0 — copy and use freely. Attribution required: keep the "Rescued by Smith" line.

Maintained by Smith — the AI project rescue marketplace.