docs(playwright): correct F3→F5 comments in CT provider stack

Both comments in apps/app/playwright/index.ts (header block lines 38-45
and inline at line 66) state that the Vuetify provider gets replaced by
PrimeVue in F3. This predates the RFC clarification that test-runtime
flip is F5, not F3 (per ARCH-TESTING.md §7).

F3 builds the PrimeVue runtime in main.ts but keeps the test runtime
on Vuetify. Component tests continue to mount with the Vuetify provider
until F5 deliberately swaps it. This commit aligns the comments with
that decision so no future contributor wonders whether the F3 sprint
should have touched this file.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/app/playwright/index.ts

@@ -36,12 +36,12 @@ import '@/styles/tokens/_timetable.css'
 //   }
 //
 // Defaults below render every component with the full Vuexy/Vuetify
-// stack. F3 (PrimeVue foundation) replaces the Vuetify plugin line
+// stack. F5 (test-runtime flip) replaces the Vuetify plugin line
 // here with PrimeVue and updates the sanity test — that is a ~2-hour
 // swap, not a rewrite. Vuetify is INTENTIONAL TEMPORARY STATE in this
 // file; do not abstract behind a "UI framework provider" indirection
-// because the abstraction would itself need to be removed in F3.
-// See dev-docs/ARCH-TESTING.md §6 for the migration timeline.
+// because the abstraction would itself need to be removed in F5.
+// See dev-docs/ARCH-TESTING.md §7 for the migration timeline.
 // =============================================================================
 
 export interface HooksConfig {
@@ -63,7 +63,7 @@ const defaultTheme: ThemeDefinition = {
 }
 
 beforeMount<HooksConfig>(async ({ app, hooksConfig }) => {
-  // ---- Vuetify (TEMPORARY: replaced by PrimeVue in F3) -----------------
+  // ---- Vuetify (TEMPORARY: replaced by PrimeVue in F5) -----------------
   const vuetify = createVuetify({
     components,
     directives,