chore: scrub personal machine/user references from docs + code

[steve-krisjanovs]

Summary

Full sweep for personal identifiers not fitting a public repo — the actual development hostname (cachy / steve-cachyos), full name (Steve Krisjanovs), narrative first-name references, and a personal Mac hostname (Steves-Air) baked into CHANGELOG entries and a couple of design docs.

• CHANGELOG.md: reworded ~10 entries that named the maintainer or a real machine directly ("Steve pushed back", "per Mac's CR", "Verified on cachy", "cachy shows steve-cachyos, mac shows Steves-Air", an internal <NAS>/multiagent-chat/... path citation) to describe the finding/decision generically. Recomputed the sha256(cwd) example with a generic path (/home/user/Repos/myproject) instead of leaving a stale hash next to a scrubbed path.
• V2-SYSTEM-AUTH-DESIGN.md: example wizard/bootstrap username+display-name → alice/Alice Example (matches convention used elsewhere); dropped a machine-name session sign-off.
• A couple of code comments (fix-pty-permissions.mjs, server.ts, credentials.ts, v2/web/README.md) that referenced "cachy"/"Steve's screenshot"/"Steve's primary phone form" as the source of a bug repro or test — reworded to describe the platform/viewport generically.

Left alone: "CachyOS" as a Linux distro name in a portability note — not personal, it's a real public distro.

Scope: current working tree only. Did not rewrite git history — that would need a destructive force-push and break every existing clone/fork's SHAs. Flagging that historical commits still contain some of these references, in case scrubbing history is wanted as a separate, deliberate decision later.

Test plan

• npm run typecheck / npm run build clean
• Exhaustive re-grep for cachy, stevekrisjanovs, taile12f0, Steve Krisjanovs, bare Steve, steve (lowercase identifier), /home/steve*, Steves-Air — all clean except the one legitimate CachyOS distro mention

🤖 Generated with Claude Code

https://claude.ai/code/session_01Au8T9RPCb6wbgiEecQrBfZ