chore(ai tooling): sync harness configs

.cursor/agents/profiler.md

@@ -1,5 +1,6 @@
 ---
 name: profiler
+model: composer-2
 description: Performance profiler that browses 5chan routes via playwright-cli, collecting Web Vitals and React rerender data via react-scan. Returns a structured issues list for a batch of routes. Use proactively when profiling browsing performance, finding bottlenecks, or diagnosing excessive React rerenders.
 ---
 

.cursor/agents/test-apk.md

@@ -1,5 +1,6 @@
 ---
 name: test-apk
+model: composer-2
 description: Android APK testing specialist that runs the 5chan APK on a local Android emulator. Manages emulator lifecycle, builds and installs debug APK, runs instrumentation tests, captures logcat diagnostics, and debugs WebView upload automation (imgur, postimages). Use proactively when the user asks to test APK features, debug Android uploads, run emulator tests, or investigate WebView automation issues.
 ---
 

.cursor/skills/implement-plan/SKILL.md

@@ -47,7 +47,7 @@ Each subagent prompt must include:
 - **File paths** and context needed to work independently
 - **Constraints** or edge cases from the plan
 
-Use `model: "fast"` for straightforward tasks. Omit model for complex ones.
+Use the `plan-implementer` agent's configured model unless the harness explicitly requires a supported model override for a straightforward task. Omit overrides for complex or cross-cutting tasks.
 
 Wait for all subagents in a batch to complete before starting the next batch.
 

.cursor/skills/profile-browsing/SKILL.md

@@ -54,16 +54,15 @@ Keep batches balanced. Add thread views (`/:boardIdentifier/thread/:cid`) as nee
 
 ## Step 2: Spawn Profiler Subagents
 
-Read the profiler subagent definition at `.cursor/agents/profiler.md`. Then spawn one `shell` Task per batch **in parallel** (single message, multiple Task calls):
+Read the profiler subagent definition at `.cursor/agents/profiler.md`. Then spawn one `profiler` Task per batch **in parallel** (single message, multiple Task calls):
 
 ```
 For each batch, create a Task:
-  subagent_type: "shell"
+  subagent_type: "profiler"
   prompt: |
-    You are a performance profiler. Follow the workflow in .cursor/agents/profiler.md.
     Session name: "prof-N"
     Routes to profile: /route1, /route2, ...
-    [Include the full profiler workflow from the agent file]
+    Any non-default app URL or extra profiling constraints
 ```
 
 Spawn up to 4 subagents simultaneously. Each opens its own browser session, navigates routes, scrolls, collects both Web Vitals and react-scan data per route, and returns a structured issues list.

.cursor/skills/test-apk/SKILL.md

@@ -7,8 +7,8 @@ description: Test and debug Android APK features using a local Android emulator.
 
 ## Overview
 
-Delegates APK testing to a **shell subagent** (`model: fast`) to keep the main context clean.
-The subagent manages the emulator, builds/installs the APK, executes tests, and returns structured diagnostics.
+Delegates APK testing to the dedicated `test-apk` subagent to keep the main context clean.
+That subagent manages the emulator, builds and installs only when needed, executes the requested tests, and returns structured diagnostics.
 
 ## Workflow
 
@@ -25,14 +25,13 @@ Ask the user (or infer from context) what to test. Common scenarios:
 | Manual APK interaction | Build, install, launch, capture logcat |
 | Contract tests (fixtures) | `yarn contract:postimages` |
 
-### Step 2: Delegate to Shell Subagent
+### Step 2: Delegate to the `test-apk` Subagent
 
-Spawn a **shell** subagent with `model: fast`. Use the prompt template below, filling in `{TEST_DESCRIPTION}` with the user's requirements.
+Spawn the `test-apk` subagent with the prompt template below, filling in `{TEST_DESCRIPTION}` with the user's requirements and any exact commands or classes you want run.
 
 ```
 Use the Task tool:
-  subagent_type: "shell"
-  model: "fast"
+  subagent_type: "test-apk"
   prompt: <see Prompt Template below>
 ```
 

.cursor/skills/translate/SKILL.md

@@ -28,7 +28,7 @@ For each key, check if the English value already exists in `public/translations/
 
 ### Step 3 — Spawn translator subagents
 
-For **each key**, spawn a `translator` subagent (using the Task tool with `subagent_type: "generalPurpose"` and `model: "fast"`). The prompt for each subagent must include:
+For **each key**, spawn a `translator` subagent using the Task tool with `subagent_type: "translator"`. The prompt for each subagent must include:
 - The key name
 - The English value
 - An instruction to follow the translator subagent's system prompt
@@ -45,7 +45,7 @@ Follow your system prompt for the full workflow (create dictionary file, dry run
 ```
 
 **Parallelism rules:**
-- Spawn up to 4 subagents concurrently (Task tool limit).
+- Spawn up to 4 subagents concurrently.
 - If there are more than 4 keys, batch them: spawn 4, wait for completion, then spawn the next batch.
 
 ### Step 4 — Report results