style: fix prettier formatting in github-ci and scheduler tests

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/github-ci.test.ts

@@ -142,7 +142,9 @@ Managed by host-driven watcher.
 
     expect(result.terminal).toBe(true);
     expect(result.resultSummary).toContain('실패');
-    expect(result.completionMessage).toContain('CI 완료: GitHub Actions run 654321');
+    expect(result.completionMessage).toContain(
+      'CI 완료: GitHub Actions run 654321',
+    );
     expect(result.completionMessage).toContain('판정: 실패');
     expect(result.completionMessage).toContain('- 실패 job: test');
   });

src/github-ci.ts

@@ -90,9 +90,7 @@ export function parseGitHubCiMetadata(
   };
 }
 
-export function serializeGitHubCiMetadata(
+export function serializeGitHubCiMetadata(metadata: GitHubCiMetadata): string {
-  metadata: GitHubCiMetadata,
-): string {
   return JSON.stringify(metadata);
 }
 
@@ -119,9 +117,7 @@ function formatConclusionLabel(conclusion: string | null | undefined): string {
   }
 }
 
-async function fetchFailedJobs(
+async function fetchFailedJobs(metadata: GitHubCiMetadata): Promise<string[]> {
-  metadata: GitHubCiMetadata,
-): Promise<string[]> {
   const stdout = await execGhApi([
     `repos/${metadata.repo}/actions/runs/${metadata.run_id}/jobs?per_page=100`,
   ]);

src/task-scheduler.test.ts

@@ -5,8 +5,7 @@ const {
   writeTasksSnapshotMock,
   loggerDebugMock,
   checkGitHubActionsRunMock,
-} =
+} = vi.hoisted(() => ({
-  vi.hoisted(() => ({
   runAgentProcessMock: vi.fn(async () => ({
     status: 'success' as const,
     result: 'done',
@@ -23,7 +22,7 @@ const {
       resultSummary: 'GitHub Actions run 123 is in_progress',
     }),
   ),
-  }));
+}));
 
 vi.mock('./provider-fallback.js', () => ({
   detectFallbackTrigger: vi.fn((error?: string | null) => {