docs(amplify-gen2-migration-e2e-system): improve skill and app workflow docs

Update gen2-migration SKILL.md to clarify snapshot directory
inspection and to guide the agent to check for existing test app
coverage before fixing a bug. Update amplify-migration-apps
README.md to include validation test steps when adding or
modifying apps, and note that E2E failures require fixing the
bug before snapshots can be captured.
---
Prompt: made more changes. commit.

Author: iliapolo

.kiro/skills/gen2-migration/SKILL.md

@@ -39,15 +39,14 @@ with a specific combination of Amplify categories and configurations. See
 
 ### Fix a Bug
 
-The snapshot inputs (`_snapshot.pre.*`) don't change — only the code and possibly the
-expected outputs (`_snapshot.post.*`) change.
-
 1. Read the relevant Context above for the area you're touching.
 
-2. Analyze the bug by reading the affected app's snapshot files. Read the
-   `_snapshot.pre.generate/` and/or `_snapshot.pre.refactor/` files to understand the
-   input configuration, and the `_snapshot.post.*` files to identify what's wrong in the
-   current output.
+2. Determine whether an existing test app covers the bug's scenario. Read the affected
+   app's `_snapshot.pre.generate/` and/or `_snapshot.pre.refactor/` files to understand
+   the input configuration, and the `_snapshot.post.*` files to identify what's wrong in
+   the current output. If no existing app exercises the affected code path, follow the
+   "Adding an App" or "Modifying an App" instructions from `amplify-migration-apps/README.md`
+   to add or update the `_snapshot.pre.*` inputs before proceeding.
 
 3. Reproduce the bug by running the appropriate E2E test:
 
@@ -56,8 +55,11 @@ expected outputs (`_snapshot.post.*`) change.
    npm run test:e2e
    ```
 
-   After the E2E run, inspect the live Gen1 and Gen2 resources and CloudFormation stack
-   events using the AWS CLI to confirm the root cause.
+   The E2E tool logs the directory where on-the-fly snapshots are captured for this run
+   (look for the `Snapshot directory:` line in the output). You can inspect the files in
+   that directory to see the state of the app at each step. In addition, inspect the live
+   Gen1 and Gen2 resources and CloudFormation stack events using the AWS CLI to confirm
+   the root cause.
 
 4. Present the root cause analysis to the user.
 
@@ -111,6 +113,12 @@ expected outputs (`_snapshot.post.*`) change.
    UPDATE_SNAPSHOTS=1 npm run test:e2e
    ```
 
+   The E2E tool logs the directory where on-the-fly snapshots are captured for this run
+   (look for the `Snapshot directory:` line in the output). You can inspect the files in
+   that directory to see the state of the app at each step. In addition, inspect the live
+   Gen1 and Gen2 resources and CloudFormation stack events using the AWS CLI to confirm
+   correctness.
+
 8. Run `yarn build && yarn test` in `packages/amplify-cli/` to verify nothing else broke.
    If tests fail at this point, only test code changes should be needed — the production
    code was already validated by the E2E run.

amplify-migration-apps/README.md

@@ -293,27 +293,36 @@ Make sure to follow the existing patterns and add tests as well.
 2. Run `amplify init`.
 3. Configure the backend using Gen1 CLI.
 4. Run `amplify push`.
-5. Use the [Snapshot Capture Tool](#snapshot-capture-tool) to capture the `pre.generate` snapshot.
+5. Add validation tests under `<app-name>/tests/` that exercise the new app's capabilities
+   (API queries, auth flows, storage operations, etc.). Follow the patterns in existing apps
+   like `project-boards/tests/` or `fitness-tracker/tests/`.
+6. Use the [Snapshot Capture Tool](#snapshot-capture-tool) to capture the `pre.generate` snapshot.
 
     ```console
     npx tsx snapshot.ts pre.generate <app-name>
 
-6. Run `UPDATE_SNAPSHOTS=1 npm run test:e2e` to execute the full migration flow and capture
-   the remaining snapshots (`post.generate`, `pre.refactor`, `post.refactor`).
+7. Run `UPDATE_SNAPSHOTS=1 npm run test:e2e` to execute the full migration flow and capture
+   the remaining snapshots (`post.generate`, `pre.refactor`, `post.refactor`). The E2E may
+   fail if the new app exercises a bug in the migration tooling. In that case the snapshots
+   will not be updated — fix the bug first, then re-run.
 
 ## Modifying an App
 
 1. `cd` into a specific app and run `npm run deploy`.
 2. Locate the deployed app directory in output logs and `cd` into it.
 3. Update the backend using Gen1 CLI.
 4. Run `amplify push`.
-5. Use the [Snapshot Capture Tool](#snapshot-capture-tool) to capture the `pre.generate` snapshot.
+5. Add or update validation tests under `<app-name>/tests/` to cover the modified
+   capabilities. Follow the patterns in existing apps like `project-boards/tests/`.
+6. Use the [Snapshot Capture Tool](#snapshot-capture-tool) to capture the `pre.generate` snapshot.
 
     ```console
     npx tsx snapshot.ts pre.generate <app-name>
 
-6. Run `UPDATE_SNAPSHOTS=1 npm run test:e2e` to execute the full migration flow and capture
-   the remaining snapshots (`post.generate`, `pre.refactor`, `post.refactor`).
+7. Run `UPDATE_SNAPSHOTS=1 npm run test:e2e` to execute the full migration flow and capture
+   the remaining snapshots (`post.generate`, `pre.refactor`, `post.refactor`). The E2E may
+   fail if the app change exercises a bug in the migration tooling. In that case the
+   snapshots will not be updated — fix the bug first, then re-run.
 
 ## Snapshot Testing