Validate the target project by replaying .tsupgrader/runtime-validation/eval-plan.json with typescript_validate_runtime.
Here, runtime validation means the complete project-specific validation plan, not only checks against an already-running application. Depending on the project, the plan may install dependencies, compile or build, run tests, launch a CLI/server/app, probe routes, and replay browser flows.
Choose the workflow
- Called from
typescript-dependencies-upgradeortypescript-compiler-upgrade: read upgrade-workflow.md. Usemode: "upgrade"and preserve the caller'srootDirectory,packageDirectory, andsessionId. - Invoked directly by the user: read standalone-workflow.md. Use
mode: "standalone"so the health check cannot create, consume, reset, or satisfy an upgrade baseline.
Never use standalone mode during an upgrade, and never fabricate an upgrade workflow for a direct health check.
Eval-plan ownership
This skill owns the eval-plan authoring guidance. When the tool reports that no plan exists, follow plan-authoring.md and its linked references, then resume the selected workflow.
Key principles
- Run one MCP tool at a time. Wait for each call to complete before starting another.
- Keep the plan deterministic. The same plan must be safely replayable without manual cleanup or volatile inputs.
- Separate plan defects from application failures. Fix an invalid assertion rather than changing working application code to satisfy it.
- Do not weaken checks to manufacture a pass. Report environment or credential blockers explicitly.
- Use the captured browser boundary. For each browser flow, call
typescript_prepare_browser_recordingonce and invoke the exact returnedJSTS Playwright Spec Authorchild once; repeat this per flow to record multiple specs. Its final assertion creates and cleans the spec automatically; never hand-author selectors or let the child write the spec.
