[v2] setup:project should clean darkroom branding from forked projects

[arzafran]

Problem

When someone forks Satus, several darkroom-specific references leak into their project even after running setup:project:

File	Line	What
app/layout.tsx	~74	authors: [{ name: 'darkroom.engineering' }] in metadata
next.config.ts	~104	hostname: 'assets.darkroom.engineering' in remotePatterns
package.json	2-3	"name": "@darkroom.engineering/satus"
components/layout/header/	12	GitHub link to darkroomengineering/satus
components/layout/footer/	16, 23	GitHub + generate links

Proposed Fix

Add a "personalize" step to setup:project that:

1. Prompts for project name → updates package.json name
2. Prompts for author/org name → updates app/layout.tsx metadata
3. Removes assets.darkroom.engineering from next.config.ts remotePatterns (or prompts for replacement CDN hostname)
4. Updates header/footer GitHub links (or removes them)

The marketing page references (app/(marketing)/) are already handled by the existing marketing cleanup step.

Context

Satus is open source. Any darkroom-specific values that survive setup:project create confusion for external teams and make the starter feel less "theirs."

[arzafran]

Moved to darkroomengineering#22