Account upstream-skipped Webpack CLI corpus

Bun compatibility slice

Account js/third_party/webpack/webpack.test.ts at exhaustive corpus position 4066.

Upstream status

Both cases are explicitly declared with test.skip in Bun because of a documented Bun stdout/stderr lifecycle bug:

• webpack works;
• webpack --watch works.

Required Home behavior

• preserve both upstream skips as todos rather than treating them as unsupported or empty;
• pin the exact 0-pass/2-todo contract in the permanent third-party mini-suite;
• keep the exhaustive gate at zero failures and zero unsupported cases;
• do not fabricate a Webpack implementation or silently promote skipped upstream behavior.

Tracked from #66.

Accounted and pushed in 8aa7bf01f.

The permanent third-party mini-suite now pins js/third_party/webpack/webpack.test.ts at exactly 0 passed and 2 todos, matching Bun's two explicit test.skip declarations. This deliberately preserves the upstream stdout/stderr lifecycle bug annotation without fabricating Webpack output or marking the file unsupported.

Verification:

• focused position 4066: 0 passed, 2 todos, 0 failed, 0 unsupported;
• adjacent positions 4065–4066: 11 passed, 2 todos, 0 failed, 0 unsupported;
• permanent third-party mini-suite: passed;
• formatting and diff checks: passed.