OK! At this point we can move the meeting-2026-02-05 test to be request only....

Let me start by looking at the existing meeting test and today's meeting content to understand what we're working with.

Now let me read the actual test files and meeting content in detail.

Now let me check the playwright config and see how tests are registered as projects.

Let me also check the 2026-02-03 project entry.

OK, so the 2026-02-03 test exists but isn't registered as a project in the config. Let me look at the TextSubmission component to understand the test IDs.

Good, I have a clear understanding of the structure. Now let me create the test for today's meeting. The meeting has:

• 9 stages total (4 discussion rounds + 4 share-outs + 1 wrap-up)
• Each discussion round uses GroupActivity with autoComplete={false} and TextSubmission
• Share-out and wrap-up stages are simple (instructor-led)
• All use the same group key alphago-discuss-2026-02-17 so students get new partners each round

Now let me update the playwright config to add the new project and make the 2026-02-05 test request-only (no dependencies, which it already is — I think "request only" means it shouldn't run by default). Let me check how the config handles that.

I see the meeting-2026-02-05 test already has no dependencies, but it's still in the main projects array so it runs by default. Let me make it and the new test "request only" — they should only run when explicitly called with --project.

Now add both meeting tests after the mobile screenshots section so they're only available by explicit request.

Let me check what the test:e2e script does to understand how tests are typically run.

I need to rethink the approach. The projects need to be in the config for --project= to work, but excluded from the default sequential run. Let me restore the meeting-2026-02-05 project and add the new one, then update the runner to skip meeting tests by default.

Now update the sequential runner to exclude meeting tests from the default run.

Now update the line that uses ALL_PROJECTS as the default to use DEFAULT_PROJECTS instead.

Also update the --list output to show which are request-only.

Now let me verify everything looks correct and run the new test. First let me check the dev server is running.

Dev server is running. Let me run the new meeting test.

Test passes. Let me also quickly verify the --list output works and the meeting tests are properly categorized.

All set. Here's what I did:

New test (testing/e2e/tests/meeting-2026-02-17.spec.ts):

• Tests the full 9-stage AlphaGo discussion meeting flow
• Creates instructor + 4 students
• Exercises all 4 discussion rounds with pair formation using the same group key (alphago-discuss-2026-02-17), verifying partner rotation
• Confirms autoComplete=false works correctly on all discussion stages
• Verifies TextSubmission is visible in each discussion round
• Tests actual text submission and instructor view in round 1
• Advances through all 4 share-out stages and the wrap-up stage
• Cleans up the session at the end
• Passes in 7.1s

Request-only meeting tests:

• Both meeting-2026-02-05 and meeting-2026-02-17 are now excluded from the default bun run test:e2e suite
• They're still in the playwright config so --project=meeting-2026-02-17 works
• The sequential runner filters them out by the meeting- prefix
• --list now shows them in a separate "Request-only" section
• Run explicitly with: bunx tsx run-projects.ts meeting-2026-02-17

Yes, those are from the E2E tests. The admin-assessments test likely hits that endpoint with a non-admin user to verify it returns 403 — that's expected behavior being logged as a warning.

I'll check the current git state and prepare the commit(s).

I can see the changes. Let me check for any debugging statements or unnecessary logging:

Good, no debugging statements. The changes look clean:

Summary of changes:

1. New E2E test: testing/e2e/tests/meeting-2026-02-17.spec.ts - tests today's AlphaGo discussion meeting
2. Playwright config: Added meeting-2026-02-17 project and marked both meeting tests as request-only
3. Test runner: Updated to exclude meeting-* tests from default run
4. Dependency update: openai package bumped from 6.17.0 to 6.22.0 (from earlier version bump)
5. Lockfile: Updated with new versions

This should be committed. The untracked test file should be added. Let me proceed:

✅ Commit complete!

Created one commit with all changes:

• New E2E test for today's AlphaGo discussion meeting (meeting-2026-02-17.spec.ts)
• Request-only test configuration - both meeting tests now excluded from default bun run test:e2e
• Test runner updates - filters out meeting-* prefix tests, updated --list output
• Dependencies - includes the OpenAI package update from the earlier version bump

The test passes (7.1s runtime) and exercises the full 9-stage meeting flow with rotating partners. Meeting tests are now request-only and won't run in CI or regular test suites unless explicitly called with --project=meeting-2026-02-17.

Let me explore the codebase to understand the current database setup, existing scripts, and K8s infrastructure.

Good, I have a thorough understanding of the infrastructure. Let me design the implementation.

Let me read the key pattern files to validate the design before writing the final plan.

Good, I have all the patterns I need. Now let me check the root package.json for the existing db script entries to know where to place the new ones.

I have a clear picture now. Let me ask a couple of clarifying questions before finalizing the plan.

Now let me write the final plan.