Adding manual tests list

[navya9singh]

After tests are generated with npm run convertfourslash, if we need to edit them manually, then this script can be run by
npm run manualtest testname. This creates a manual folder under fourslash/tests/ and adds the name of the test to manualTests.txt.

• All tests in manualTests.txt will ne skipped and not regenerated when convertfourslash is run again.
• Once a manual folder is created, testOutput = cp.execFileSync(go, ["test", "./internal/fourslash/tests/gen"], ["test", "./internal/fourslash/tests/manual"], { encoding: "utf-8" }) can be added to updateFailing.mts to run all the tests under ./manual and update failingtests.txt accordingly.

[Copilot]

Pull Request Overview

This PR adds functionality to manually manage fourslash tests by creating a script that moves generated tests to a separate manual directory and tracks them to prevent regeneration. The purpose is to allow developers to edit auto-generated tests without losing changes when the conversion script runs again.

Key changes:

• Adds a new npm script makemanual that moves tests from generated to manual directory
• Implements tracking of manual tests to skip them during regeneration
• Updates the conversion script to respect manual test exclusions

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
package.json	Adds new npm script makemanual for manual test management
internal/fourslash/_scripts/makeManual.mts	New script that moves tests to manual directory and tracks them
internal/fourslash/_scripts/convertFourslash.mts	Updates conversion logic to skip manual tests during regeneration

[jakebailey]

Maybe a silly question but why can't we generate this one automatically?

[gabritto]

There's no simplified way to compute what the commit characters should be other than the actual implementation. The porting script currently sets empty commit characters if isNewIdentifierLocation is true, which is an approximation that does not always hold, like in this test. An alternative would be to ignore commit characters for all ported tests, but I didn't want to do that and end up with no coverage of it.

[jakebailey]

Would it be simpler to just keep a list of these in the generator script?

[gabritto]

For this case, probably, but there are other tests that need other types of manual fixes, and tests that will need to be at least partially manually ported because they have things like for loops and functions.