chore(rstest-skill): remove ProvidedExports Troubleshooting

Author: 9aoy

skills/migrate-to-rstest/SKILL.md

@@ -32,7 +32,7 @@ Migrate Jest- or Vitest-based tests and configuration to Rstest with minimal beh
    - Global API replacement rules: `references/global-api-migration.md`
    - Known compatibility pitfalls: `references/rstest-compat-pitfalls.md`
 5. Check type errors
-6. Run tests and fix deltas (if mocks fail unexpectedly under Rspack, see `references/provided-exports-troubleshooting.md`)
+6. Run tests and fix deltas
 7. Remove legacy test runner dependency/config only after Rstest is green
 8. Summarize changes
 
@@ -85,8 +85,7 @@ stop and provide:
 
 - Run the test suite and fix failures iteratively.
 - Fix configuration and resolver errors first, then address mocks/timers/snapshots, and touch test logic last.
-- If mocks fail for re-exported modules under Rspack, use:
-  `references/provided-exports-troubleshooting.md`
+- If mocks fail for re-exported modules under Rspack, first check whether the project is pinned to `rstest < 0.9.3`.
 - Before broad test rewrites, check known pitfalls in:
   `references/rstest-compat-pitfalls.md`
 

skills/migrate-to-rstest/references/provided-exports-troubleshooting.md

@@ -5,9 +5,10 @@ Use this reference when migration passes static replacement but runtime tests st
 For general migration pitfalls (globals mode, setup adapters, mock factory/hoisting, path resolution), use the official Vitest migration guide first:
 https://rstest.rs/guide/migration/vitest
 
-## Re-export mock target mismatch under Rspack
+## Re-export mock target mismatch under Rspack (legacy)
 
-When runtime resolves through source module instead of re-export module, migrated mocks may appear ignored.
+This issue was fixed in `rstest v0.9.3`.
+Treat this section as a legacy note only for projects pinned to `rstest < 0.9.3`.
 
-- First follow `references/provided-exports-troubleshooting.md`.
-- If needed, temporarily stabilize build optimization and re-target mock to the actually resolved module.
+- First confirm the installed Rstest version.
+- If the project is still on an older version, upgrade to `rstest >= 0.9.3` before debugging mock behavior further.