Test Changes

Produce a practical handoff for manually verifying the work completed in the current conversation.

1. Establish the test surface

Reconstruct the delivered outcome from the conversation, including later corrections and failed or partial attempts. Treat the current workspace, connected systems, and running environment as confirmation of the final state, not as a substitute for the conversation.

Inspect read-only evidence where useful: changed files, git diff, repository status, available scripts, project documentation, generated artifacts, external records, and already-running services. Account for every user-visible behaviour, artifact, or external state changed by the completed work. Separate unrelated pre-existing changes.

If no completed or inspectable change exists, say so and identify what must be completed before manual testing is meaningful.

Completion criterion: every change made in this conversation is mapped to something the user can inspect or exercise, or explicitly marked as having no manual test surface.

2. Build the shortest valid test path

Start with what the user can see right now, before asking them to run anything. Include existing files, rendered artifacts, open applications, running services, URLs, or visible state only when confirmed.

Then provide the minimum prerequisites and commands needed to reach the test surface. Use PowerShell syntax for terminal commands: