By: syd <syd@kronor.io>
Replace the precondition checks with commands actually run The checklist is the thing the user will act on when they get the real repository, and several of its commands had never been executed. Two were wrong. `pnpm config get node-linker` prints `undefined` when the setting is absent, which is the normal passing case, so the checklist told the reader to expect `isolated` and the real answer looks like an error while saying nothing about the tree that got installed. Replaced with the behavioural test that measures the property the recipe actually needs: ask Node to resolve a workspace package a manifest does not declare, and require it to fail. Verified both ways here, failing from packages/orphan and resolving from packages/strings. The path-alias grep only looked under packages/, missing apps/, and its passing outcome is grep exiting 1, which reads like a failure unless said. Check 4 claimed to expect one build and one test target. Real output for @nx-exp/core has six, because the atomizer derives its own per-file targets and Nx adds nx-release-publish. Restated with the actual output. Checks 3, 5 and 6 were prose rather than commands. They are commands now, and one jq invocation answers 5 and 6 together by reading every build script at once. Every command in the section has been run and the output shown is the real one.