Implement the following plan:

Plan: Feedback Component E2E Tests

Context

The new <Feedback> component was just implemented. It reuses the text_submissions table and API — the submission ID is auto-generated as feedback-{meetingSlug}. We need E2E tests covering the student view (textarea + submit + version tracking) and the instructor view (submission count, dropdown, feedback display).

Approach

Follow the exact same pattern as text-submission.spec.ts: create a dedicated test page at /testing/components/feedback, write a spec file, and register it in playwright.config.ts. Since Feedback reuses the text-submissions API, cleanup uses the existing DELETE /api/text-submissions/e2e/clear/{submissionId} endpoint — no new API routes needed.

Files to Create

1. apps/web/app/testing/components/feedback/page.tsx — Test fixture page

Wraps <Feedback> in a MeetingProvider (meetingSlug: "test-meeting", semester: "spring2026"), producing submissionId feedback-test-meeting. Includes a second instance with a custom prompt.

2. testing/e2e/tests/feedback.spec.ts — E2E test spec

Student tests (using authenticatedPage fixture):

• Shows default prompt text
• Shows custom prompt text (second Feedback instance)
• Submit button disabled when textarea empty
• Submits feedback successfully + persists on reload
• Allows resubmission with version tracking
• Submit button disabled when no unsaved changes

Instructor tests (using testUsers fixture with instructor + student):

• Instructor sees feedback-instructor-view (not the textarea)
• Shows empty state when no submissions
• Student submits → instructor sees submission count update and content in dropdown

Cleanup: beforeEach calls DELETE /api/text-submissions/e2e/clear/feedback-test-meeting.

Files to Modify

3. testing/e2e/playwright.config.ts

Add project entry:

{
  name: "feedback",
  testMatch: /feedback\.spec\.ts/,
  use: { ...devices["Desktop Chrome"] },
  dependencies: deps,
},

Verification

# Check dev server is running
curl -sk -o /dev/null -w "%{http_code}" https://[local-hostname]/

# Run just the feedback tests
cd testing/e2e && CI=true bunx playwright test --project=feedback

If you need specific details from before exiting plan mode (like exact code snippets, error messages, or content you generated), read the full transcript at: ~/.claude/projects/-Users-challen-www-usingandunderstanding-ai/169e6f06-718d-4202-9729-74ba0cd57a8c.jsonl

Read the output file to retrieve the result: [tmp-path]

Your task

First, run git status, git diff, and git log --oneline -10 to understand the current state.

Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.

Cool! Let's add a five minute feedback component to today's activity.

Should we add it to today's e2e test as well?

Your task

First, run git status, git diff, and git log --oneline -10 to understand the current state.

Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.

Your task

First, run git status, git diff, and git log --oneline -10 to understand the current state.

Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.

Let's update the syllabus to state that students have three excused absences from class meetings. And let's add that to the /status page as well, counting the number that they've already used.