Core: Make csf-tools printing and CLI dispatcher output Windows-stable

[obvious-autobuild]

Closes #

What I did

tests-unit--windows in daily-generated failed 4 consecutive runs (SHAs bf830863e, 4f66ceeb2 x3) with three Windows-specific failure signatures, all verified mechanically:

1. CRLF in reprinted config/CSF output (most of the 19 failures). printConfig and printCsf delegate to recast.print without a lineTerminator, and recast defaults that to os.EOL — so every reprinted line gained \r on Windows. Both wrappers now pin lineTerminator: '\n', matching what babelPrint in code/core/src/babel/babelParse.ts already does (including its comment explaining exactly this).
2. Quote-style flips on freshly generated nodes (codemod tests expecting import preview from './preview'; received "...";). _inferQuotes() indexed token offsets into the raw source string; when source lines end in CRLF the offsets no longer align and the count falls back to double quotes. _inferQuotes now normalizes CRLF before counting (a no-op for LF sources).
3. Benign wmic stderr leaked into the CLI help test (No Instance(s) Available.\r\r\n instead of empty stderr). dispatcher.ts calls getProcessAncestry() for every external-CLI command since CLI: Accept Node.js prerelease builds in the version gate #36320 landed 5f32ebb8, and process-ancestry's Windows implementation runs wmic via execSync without a stdio option, so wmic's stderr forwards to the CLI's stderr. process-ancestry@0.1.0 does not fix this, so the PR vendors the ancestry lookup as getProcessAncestry in storybook/internal/common — preserving the upstream Unix and Windows traversal, discarding child stderr via stdio: ['ignore', 'pipe', 'ignore'] — and drops the process-ancestry dependency entirely.

An earlier revision fixed #3 with a Yarn patch instead. That was unsafe for published packages: Yarn wires patches by writing patch:process-ancestry@... descriptors into the dependency manifests of core, cli-storybook, and create-storybook, and those descriptors ship with the published packages while the patch file only exists in the monorepo. Generated sandboxes install published packages from Verdaccio, so every sandbox install failed with ENOENT on .yarn/patches/process-ancestry-npm-0.0.2-a5c4b74866.patch. Vendoring removes the failure class instead of making the patch resolvable: no descriptor, no patch file, one less external dependency.

Adds two regression tests (ConfigObject.test.ts, CsfObject.test.ts) that feed CRLF sources to both printers and assert LF output and correct quote inference. Verified red against the pre-fix code and green after.

Adds a process-ancestry.test.ts unit suite covering PID validation, Unix traversal, Windows CSV parsing, stderr suppression, and cycle detection; TelemetryService.test.ts now mocks the vendored storybook/internal/common export instead of the removed package.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Caution

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

No manual testing is needed: the failures are only observable on Windows (os.EOL = CRLF, wmic present), and the daily-generated workflow's tests-unit--windows job is itself the verification path. On Linux the new regression tests exercise both mechanisms via an os.EOL override and CRLF fixtures.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

No documentation changes apply — internal CI/printing behavior only.

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Declare whether manual QA will be needed for this PR during the next release, through qa:needed or qa:skip

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary Release - 🚫 Not run

This PR does not have a canary release associated.

In-repo PRs: add the ci:canary label. Later pushes republish while the label remains.

Fork PRs: the label does nothing (a later push must not auto-publish). A maintainer publishes from this repository with Run workflow and the pr input. branch and sha are optional; if more than one is set, they must be the same commit. The fork author does not need to do anything.

---

Human author: Gert Hengeveld (gert@chromatic.com)

🔗 Obvious Project · 🧵 Obvious Thread