Merge pull request #46 from nsbradford/nick10-10-fix_tests

fix tests

playwright.config.ts

@@ -18,7 +18,7 @@ export default defineConfig({
   /* Retry on CI only */
   retries: process.env.CI ? 2 : 0,
   /* Opt out of parallel tests on CI. */
-  workers: process.env.CI ? 1 : undefined,
+  workers: undefined, // process.env.CI ? 1 : undefined,
   /* Reporter to use. See https://playwright.dev/docs/test-reporters */
   reporter: 'html',
   /* Shared settings for all the projects below. See https://playwright.dev/docs/api/class-testoptions. */

src/prompts.ts

@@ -36,6 +36,7 @@ RULES YOU MUST FOLLOW:
 - The questions should be ordered logically. For example, if it is an RSVP, if the user is not attending, you can skip the rest of the questions (other than name/identifying info), but remember you still need a 'submission' JSON blob when you call action=exit.
 - Users might sometimes be uncertain about some fields; you can press a little, but you must ultimately respect their decision.
 - Intelligently infer things based on the user inputs. For example, if you are asking for a GitHub username, and the user provides you with their GitHub URL, you can simply extract the username from the URL instead of asking the user for clarification. (Never tell the user you are doing this, though.)
+- Do NOT confirm with the user before submitting the form. Just submit it when you've gathered all the info.
 
 YOUR SCHEMA:
 Name: ${form.name}