walk-the-recipe-as-target-userlisted

# Walk the Recipe as the Target User ## Problem A documented workflow — README reproduction recipe, onboarding script, install procedure, deploy guide — works perfectly for the developer who wrote it. They have all the credentials, all the SDKs, all the tooling already installed. They wrote the recipe by literally running the steps and confirming each one. They aren't lying about it working. But they wrote it on a privileged-environment machine. Their `ANTHROPIC_API_KEY` is set. Their `KUBECONFIG` points to the cluster. Their `gcloud auth` is current. Their AWS SSO session is fresh. Their `node_modules` is hydrated. Their docker daemon is running. A real user — a T1 reader, a new hire, a contractor, an external evaluator, an open-source maintainer reviewing a PR — has a DIFFERENT environment. Their version of "I cloned and tried to follow the README" is structurally different from the author's "I followed my own README." The differences are invisible to the author because the author cannot reproduce their own absence-of-a-credential. The documented recipe stays accurate as far as the author can see, and the recipe stays broken for the real user. The literal-spec response — "go through the 6-item hardening checklist the planning doc names" — does not catch this failure mode. The 6 items address the author's THEN-CURRENT best guess of friction. Reality friction may have moved, may include items the author never considered (because their own privilege blinded them), or may