<!-- task=m-operator-runtime-refactor/03_client_bootstrap plan=0 tag=CLIENT -->

# Code Review Reference - CLIENT

> **[IMPLEMENTING AGENT — READ FIRST] Filling in this file is the mandatory final step of implementation.**
> The task is NOT complete until every implementation-owned section below is filled in.
> Complete the `구현 체크리스트`; the final checklist item is mandatory before saving.
> Fill implementation-owned sections, then stop with active files in place and report ready for review.
> If implementation is blocked by a user-only decision, user-owned external environment prerequisite, or scope conflict, fill `사용자 리뷰 요청` with evidence and stop with active files in place; code-review decides whether to write `USER_REVIEW.md`. Evidence gaps that a follow-up agent can close by rerunning commands or collecting artifacts are normal follow-up issues, not user-review blockers by themselves.
> Finalization (`코드리뷰 결과`, log rename, `complete.log`, archive moves, `코드리뷰 전용 체크리스트`) is review-agent-only, even after compaction/resume.
> Follow the ownership table at the bottom of this file for which sections you own.

## 개요

date=2026-05-31
task=m-operator-runtime-refactor/03_client_bootstrap, plan=0, tag=CLIENT

## Roadmap Targets

- Milestone: `agent-roadmap/phase/operator-surface/milestones/operator-runtime-refactor.md`
- Task ids:
  - `client-bootstrap`: Flutter operator shell이 push/Firebase/Mattermost 초기화 없이도 시작 가능한 경계로 분리되고, push-specific integration은 후속 push Milestone 범위로 남는다.
- Completion mode: check-on-pass

## 이 파일을 읽는 리뷰 에이전트에게

> **[REVIEW AGENT ONLY]** 아래 종결 절차는 코드리뷰 에이전트 전용이다. 구현 에이전트는 이 섹션을 실행하지 않는다.

각 항목의 구현을 실제 소스 파일과 대조하고, `검증 결과` 섹션의 출력이 코드와 일치하는지 확인하세요.
리뷰 완료는 아래 순서까지 끝난 상태를 의미합니다.

1. 판정을 append한다.
2. `CODE_REVIEW-cloud-G07.md` -> `code_review_cloud_G07_N.log`, `PLAN-cloud-G07.md` -> `plan_cloud_G07_M.log`로 아카이브한다.
3. PASS이면 `complete.log` 작성 후 active task 디렉터리를 `agent-task/archive/YYYY/MM/m-operator-runtime-refactor/03_client_bootstrap/`로 이동한다. WARN/FAIL이면 user-review gate를 확인한 뒤 다음 active plan/review 파일 또는 `USER_REVIEW.md`를 작성한다.
4. PASS이고 task group이 `m-operator-runtime-refactor`이면 완료 이벤트 메타데이터를 보고한다. roadmap 상태 체크와 `update-roadmap` 호출은 런타임 책임이다.
5. 적용 가능한 `코드리뷰 전용 체크리스트` 항목을 최종 `.log` 위치에서 체크한 뒤 보고한다.

---

## 구현 항목별 완료 여부

| 항목 | 완료 여부 |
|------|---------|
| [CLIENT-1] Core Shell Bootstrap | [x] |
| [CLIENT-2] App Shell Starts Without Push | [x] |
| [CLIENT-3] Push Opt-In Boundary | [x] |

## 구현 체크리스트

- [x] [CLIENT-1] core operator shell bootstrap을 Firebase/Mattermost push initialization과 분리한다.
- [x] [CLIENT-2] bootstrap tests를 추가해 기본 `runAltClient` path가 push/Firebase 없이 app shell을 시작할 수 있음을 검증한다.
- [x] [CLIENT-3] push-specific initialization은 explicit opt-in API로 남기고 후속 push Milestone 범위임을 코드 경계로 드러낸다.
- [x] 원격 ALT checkout root에서 `cd apps/client && flutter test`를 실행하고 실제 stdout/stderr를 review stub에 기록한다.
- [x] CODE_REVIEW-*-G??.md의 구현 에이전트 소유 섹션을 실제 구현 내용과 검증 출력으로 채운다. 이 항목이 완료되기 전에는 구현이 완료된 것이 아니다.

## 코드리뷰 전용 체크리스트

> **[REVIEW AGENT ONLY]** 이 체크리스트는 코드리뷰 에이전트만 사용한다.
> 구현 에이전트는 이 섹션을 수정하거나 체크하지 않는다.

- [x] `코드리뷰 결과`에 `PASS`, `WARN`, `FAIL` 중 하나의 판정을 append한다.
- [x] 판정과 `차원별 평가`, Required/Suggested/Nit 분류가 서로 일치한다.
- [x] active `CODE_REVIEW-*-G??.md`를 `code_review_cloud_G07_N.log`로 아카이브한다.
- [x] active `PLAN-*-G??.md`를 `plan_cloud_G07_M.log`로 아카이브한다.
- [x] `.gitignore`의 Agent-Ops 관리 block이 `agent-task/**/*.md`와 `agent-task/**/*.log`를 unignore하여 plan/review/archive 산출물이 추적 가능한지 확인한다.
- [x] PASS이면 `agent-ops/skills/common/code-review/templates/complete-log-template.md` 기준으로 `complete.log`를 작성하고 active `.md` 파일을 남기지 않는다.
- [x] PASS이면 active task 디렉터리 `agent-task/m-operator-runtime-refactor/03_client_bootstrap/`를 `agent-task/archive/YYYY/MM/m-operator-runtime-refactor/03_client_bootstrap/`로 이동하고 최종 archive 경로에서 이 체크리스트를 갱신한다.
- [x] PASS이고 task group이 `m-operator-runtime-refactor`이면 런타임이 읽을 완료 이벤트 메타데이터를 보고하고, roadmap 수정이나 `update-roadmap` 직접 호출을 하지 않는다.
- [x] PASS split 작업이면 이동 후 빈 active parent `agent-task/m-operator-runtime-refactor/`를 제거하거나, 남은 sibling/file이 있어 유지했다고 확인한다.
- [ ] WARN/FAIL이고 user-review gate가 트리거되지 않았으면 다음 active `PLAN-cloud-G07.md`와 `CODE_REVIEW-cloud-G07.md`를 작성하고 `complete.log`를 작성하지 않는다.
- [ ] USER_REVIEW이면 `agent-ops/skills/common/code-review/templates/user-review-template.md` 기준으로 `USER_REVIEW.md`를 작성하고 active `PLAN-*.md`, `CODE_REVIEW-*.md`, `complete.log`를 남기지 않는다.
- [ ] USER_REVIEW가 사용자 결정으로 완료/PASS 해소되면 `USER_REVIEW.md`를 해소 상태로 갱신하고 `complete.log`를 작성한 뒤 task directory를 archive로 이동한다.

## 계획 대비 변경 사항

- `AltClientBootstrapOptions`에 `applyFullscreen` 플래그(기본값 `true`)를 추가하였습니다. Flutter widget test 환경에서 `SystemChrome.setEnabledSystemUIMode` 같은 플랫폼 채널 호출이 블로킹/대기 현상을 발생시키는 이슈를 해소하기 위해, 테스트 코드에서는 `applyFullscreen: false`를 전달하도록 구현하였습니다.

## 주요 설계 결정

- 앱 코어 쉘의 부트스트랩 단계와 Firebase/Mattermost 푸시 알림 초기화 단계를 명시적으로 분리하였습니다.
- `AltClientBootstrapOptions`를 신설하여 푸시 비활성화(`enablePush = false`, 기본값) 상태에서 앱이 Firebase 및 Mattermost 초기화 없이 안전하게 대시보드 쉘을 렌더링하도록 처리하였습니다.
- 테스트의 편리성 및 견고함을 위해 Firebase 초기화 함수(`firebaseInitializer`) 및 Mattermost 호스트 팩토리(`mattermostHostFactory`)를 옵션으로 주입할 수 있게 설계하여, 실제 Firebase 모듈 로드 없이 가짜(Fake/Mock) 연동 객체로 푸시 활성화 시나리오까지 완벽히 단위 테스트할 수 있도록 하였습니다.

## 사용자 리뷰 요청

- 상태: 없음
- 사유 유형: 없음
- 결정 필요: 없음
- 차단 근거: 없음
- 실행한 검증/명령: 없음
- 자동 후속 불가 이유: 없음
- 재개 조건: 없음

## 리뷰어를 위한 체크포인트

- Default `runAltClient`/`bootstrapAltClient` path does not require Firebase or Mattermost push readiness.
- Push initialization is explicit opt-in and remains outside dashboard/widget presentation code.
- New tests avoid platform Firebase initialization by using injected hooks/fakes.

## 검증 결과

### CLIENT-1 중간 검증
```text
$ cd apps/client && flutter test test/app/bootstrap_test.dart
00:00 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: AltClientBootstrap ... call Firebase or Mattermost and returns null
00:01 +1: AltClientBootstrap ... call Firebase or Mattermost and returns null
00:01 +1: AltClientBootstrap ... initializes Firebase and Mattermost push host
00:01 +2: AltClientBootstrap ... initializes Firebase and Mattermost push host
00:01 +2: ... runAltClient renders AltClientApp shell without Firebase/push
00:01 +3: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +3: All tests passed!
```

### CLIENT-2 중간 검증
```text
$ cd apps/client && flutter test test/widget_test.dart test/app/bootstrap_test.dart
00:00 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: ... does not call Firebase or Mattermost and returns null
00:01 +1: ... does not call Firebase or Mattermost and returns null
00:01 +1: ... bootstrapAltClient initializes Firebase and Mattermost push host
00:01 +2: ... bootstrapAltClient initializes Firebase and Mattermost push host
00:01 +2: ... runAltClient renders AltClientApp shell without Firebase/push
00:01 +3: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +3: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +4: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +4: loading /config/workspace/alt/apps/client/test/widget_test.dart
00:02 +4: ... shows ALT dashboard shell with default disconnected socket state
00:02 +5: ... shows ALT dashboard shell with default disconnected socket state
00:02 +6: ... shows ALT dashboard shell with default disconnected socket state
00:02 +7: ... shows ALT dashboard shell with default disconnected socket state
00:02 +8: ... shows ALT dashboard shell with default disconnected socket state
00:02 +8: ... shows ALT dashboard with socket state Connecting
00:02 +9: ... shows ALT dashboard with socket state Connecting
00:02 +10: ... shows ALT dashboard with socket state Connecting
00:02 +11: ... shows ALT dashboard with socket state Connecting
00:02 +12: ... shows ALT dashboard with socket state Connecting
00:02 +13: ... shows ALT dashboard with socket state Connected
00:02 +14: ... shows ALT dashboard with socket state Connected
00:02 +15: ... shows ALT dashboard with socket state Connected
00:02 +16: ... shows ALT dashboard with socket state Connected
00:02 +17: ... shows ALT dashboard with socket state Connected
00:02 +18: ... shows ALT dashboard with socket state Connected
00:02 +19: ... shows ALT dashboard with socket state Connected
00:02 +20: ... shows ALT dashboard with socket state Connected
00:02 +21: ... shows ALT dashboard with socket state Connected
00:02 +22: ... shows ALT dashboard with socket state Connected
00:02 +23: ... shows ALT dashboard with socket state Connected
00:02 +24: ... shows ALT dashboard with socket state Connected
00:02 +25: ... shows ALT dashboard with socket state Connected
00:02 +26: ... shows ALT dashboard with socket state Connected
00:02 +27: ... shows ALT dashboard with socket state Connected
00:02 +28: ... shows ALT dashboard with socket state Connected
00:02 +29: ... shows ALT dashboard with socket state Connected
00:02 +30: ... shows ALT dashboard with socket state Connected
00:03 +30: ... shows ALT dashboard with socket state Connected
00:03 +31: ... shows ALT dashboard with socket state Connected
00:03 +31: ... shows ALT dashboard with socket state Error
00:03 +32: ... shows ALT dashboard with socket state Error
00:03 +33: ... shows ALT dashboard with socket state Error
00:03 +34: ... shows ALT dashboard with socket state Error
00:03 +35: ... shows ALT dashboard with socket state Error
00:03 +36: ... shows ALT dashboard with socket state Error
00:03 +37: ... shows ALT dashboard with socket state Error
00:03 +38: ... shows ALT dashboard with socket state Error
00:03 +39: ... shows ALT dashboard with socket state Error
00:03 +40: ... shows ALT dashboard with socket state Error
00:03 +41: ... shows ALT dashboard with socket state Error
00:03 +42: ... shows ALT dashboard with socket state Error
00:03 +43: ... shows ALT dashboard with socket state Error
00:03 +44: ... shows ALT dashboard with socket state Error
00:03 +45: ... shows ALT dashboard with socket state Error
00:03 +46: ... shows ALT dashboard with socket state Error
00:03 +47: ... shows ALT dashboard with socket state Error
00:03 +48: ... shows ALT dashboard with socket state Error
00:03 +49: ... shows ALT dashboard with socket state Error
00:03 +50: ... shows ALT dashboard with socket state Error
00:03 +51: ... shows ALT dashboard with socket state Error
00:03 +52: ... shows ALT dashboard with socket state Error
00:03 +53: ... shows ALT dashboard with socket state Error
00:03 +54: ... shows ALT dashboard with socket state Error
00:03 +55: ... shows ALT dashboard with socket state Error
00:03 +56: ... shows ALT dashboard with socket state Error
00:03 +57: ... shows ALT dashboard with socket state Error
00:03 +58: ... shows ALT dashboard with socket state Error
00:03 +59: ... shows ALT dashboard with socket state Error
00:03 +60: ... shows ALT dashboard with socket state Error
00:03 +61: ... shows ALT dashboard with socket state Error
00:03 +62: ... shows ALT dashboard with socket state Error
00:03 +63: ... shows ALT dashboard with socket state Error
00:03 +64: ... shows ALT dashboard with socket state Error
00:03 +65: ... shows ALT dashboard with socket state Error
00:03 +66: ... shows ALT dashboard with socket state Error
00:03 +67: ... shows ALT dashboard with socket state Error
00:03 +68: ... shows ALT dashboard with socket state Error
00:03 +69: ... shows ALT dashboard with socket state Error
00:03 +70: ... shows ALT dashboard with socket state Error
00:03 +71: ... shows ALT dashboard with socket state Error
00:03 +72: ... shows ALT dashboard with socket state Error
00:03 +73: ... shows ALT dashboard with socket state Error
00:03 +74: ... shows ALT dashboard with socket state Error
00:03 +75: ... shows ALT dashboard with socket state Error
00:03 +76: ... shows ALT dashboard with socket state Error
00:03 +77: ... shows ALT dashboard with socket state Error
00:03 +78: ... shows ALT dashboard with socket state Error
00:03 +79: ... shows ALT dashboard with socket state Error
00:03 +80: ... shows ALT dashboard with socket state Error
00:03 +81: ... shows ALT dashboard with socket state Error
00:03 +82: ... shows ALT dashboard with socket state Error
00:03 +83: ... shows ALT dashboard with socket state Error
00:03 +84: ... shows ALT dashboard with socket state Error
00:03 +85: ... shows ALT dashboard with socket state Error
00:03 +86: ... shows ALT dashboard with socket state Error
00:03 +87: ... shows ALT dashboard with socket state Error
00:03 +88: ... shows ALT dashboard with socket state Error
00:03 +89: ... shows ALT dashboard with socket state Error
00:03 +90: ... shows ALT dashboard with socket state Error
00:03 +91: ... shows ALT dashboard with socket state Error
00:03 +92: ... shows ALT dashboard with socket state Error
00:03 +93: ... shows ALT dashboard with socket state Error
00:03 +94: ... shows ALT dashboard with socket state Error
00:03 +95: ... shows ALT dashboard with socket state Error
00:03 +96: ... shows ALT dashboard with socket state Error
00:03 +97: ... shows ALT dashboard with socket state Error
00:03 +98: ... shows ALT dashboard with socket state Error
00:03 +99: ... shows ALT dashboard with socket state Error
00:03 +100: ... shows ALT dashboard with socket state Error
00:03 +101: ... shows ALT dashboard with socket state Error
00:03 +102: ... shows ALT dashboard with socket state Error
00:03 +103: ... shows ALT dashboard with socket state Error
00:03 +104: ... shows ALT dashboard with socket state Error
00:03 +105: ... shows ALT dashboard with socket state Error
00:03 +106: ... shows ALT dashboard with socket state Error
00:03 +107: ... shows ALT dashboard with socket state Error
00:03 +108: ... shows ALT dashboard with socket state Error
00:03 +109: ... shows ALT dashboard with socket state Error
00:03 +110: ... shows ALT dashboard with socket state Error
00:03 +111: ... shows ALT dashboard with socket state Error
00:03 +112: ... shows ALT dashboard with socket state Error
00:03 +113: ... shows ALT dashboard with socket state Error
00:03 +114: ... shows ALT dashboard with socket state Error
00:03 +115: ... shows ALT dashboard with socket state Error
00:03 +116: ... shows ALT dashboard with socket state Error
00:03 +117: ... shows ALT dashboard with socket state Error
00:03 +118: ... shows ALT dashboard with socket state Error
00:03 +119: ... shows ALT dashboard with socket state Error
00:03 +120: ... shows ALT dashboard with socket state Error
00:03 +121: ... shows ALT dashboard with socket state Error
00:03 +122: ... shows ALT dashboard with socket state Error
00:03 +123: ... shows ALT dashboard with socket state Error
00:03 +124: ... shows ALT dashboard with socket state Error
00:03 +125: ... shows ALT dashboard with socket state Error
00:03 +126: ... shows ALT dashboard with socket state Error
00:03 +127: ... shows ALT dashboard with socket state Error
00:03 +128: ... shows ALT dashboard with socket state Error
00:03 +129: ... shows ALT dashboard with socket state Error
00:03 +130: ... shows ALT dashboard with socket state Error
00:03 +131: ... shows ALT dashboard with socket state Error
00:03 +132: ... shows ALT dashboard with socket state Error
00:03 +133: ... shows ALT dashboard with socket state Error
00:03 +134: ... shows ALT dashboard with socket state Error
00:03 +135: ... shows ALT dashboard with socket state Error
00:03 +136: ... shows ALT dashboard with socket state Error
00:03 +137: ... shows ALT dashboard with socket state Error
00:03 +138: ... shows ALT dashboard with socket state Error
00:03 +139: ... shows ALT dashboard with socket state Error
00:03 +140: ... shows ALT dashboard with socket state Error
00:03 +141: ... shows ALT dashboard with socket state Error
00:03 +142: ... shows ALT dashboard with socket state Error
00:03 +143: ... shows ALT dashboard with socket state Error
00:03 +144: ... shows ALT dashboard with socket state Error
00:03 +145: ... shows ALT dashboard with socket state Error
00:03 +146: ... shows ALT dashboard with socket state Error
00:03 +147: ... shows ALT dashboard with socket state Error
00:03 +148: ... shows ALT dashboard with socket state Error
00:03 +149: ... shows ALT dashboard with socket state Error
00:03 +150: ... shows ALT dashboard with socket state Error
00:03 +151: ... shows ALT dashboard with socket state Error
00:03 +152: ... shows ALT dashboard with socket state Error
00:03 +153: ... shows ALT dashboard with socket state Error
00:03 +154: ... shows ALT dashboard with socket state Error
00:03 +155: ... shows ALT dashboard with socket state Error
00:03 +156: ... shows ALT dashboard with socket state Error
00:03 +157: ... shows ALT dashboard with socket state Error
00:03 +158: ... shows ALT dashboard with socket state Error
00:03 +159: ... shows ALT dashboard with socket state Error
00:03 +160: ... shows ALT dashboard with socket state Error
00:03 +161: ... shows ALT dashboard with socket state Error
00:03 +162: ... shows ALT dashboard with socket state Error
00:03 +163: ... shows ALT dashboard with socket state Error
00:03 +164: ... shows ALT dashboard with socket state Error
00:03 +165: ... shows ALT dashboard with socket state Error
00:03 +166: ... shows ALT dashboard with socket state Error
00:03 +167: ... shows ALT dashboard with socket state Error
00:03 +168: ... shows ALT dashboard with socket state Error
00:03 +169: ... shows ALT dashboard with socket state Error
00:03 +170: ... shows ALT dashboard with socket state Error
00:03 +171: ... shows ALT dashboard with socket state Error
00:03 +172: ... shows ALT dashboard with socket state Error
00:03 +173: ... shows ALT dashboard with socket state Error
00:03 +174: ... shows ALT dashboard with socket state Error
00:03 +175: ... shows ALT dashboard with socket state Error
00:03 +176: ... shows ALT dashboard with socket state Error
00:03 +177: ... shows ALT dashboard with socket state Error
00:03 +178: ... shows ALT dashboard with socket state Error
00:03 +179: ... shows ALT dashboard with socket state Error
00:03 +180: ... shows ALT dashboard with socket state Error
00:03 +181: ... shows ALT dashboard with socket state Error
00:03 +182: ... shows ALT dashboard with socket state Error
00:03 +183: ... shows ALT dashboard with socket state Error
00:03 +184: ... shows ALT dashboard with socket state Error
00:03 +185: ... shows ALT dashboard with socket state Error
00:03 +186: ... shows ALT dashboard with socket state Error
00:03 +187: ... shows ALT dashboard with socket state Error
00:03 +188: ... shows ALT dashboard with socket state Error
00:03 +189: ... shows ALT dashboard with socket state Error
00:03 +190: ... shows ALT dashboard with socket state Error
00:03 +191: ... shows ALT dashboard with socket state Error
00:03 +192: ... shows ALT dashboard with socket state Error
00:03 +193: ... shows ALT dashboard with socket state Error
00:03 +194: ... shows ALT dashboard with socket state Error
00:03 +195: ... shows ALT dashboard with socket state Error
00:03 +196: ... shows ALT dashboard with socket state Error
00:03 +197: ... shows ALT dashboard with socket state Error
00:03 +198: ... shows ALT dashboard with socket state Error
00:03 +199: ... shows ALT dashboard with socket state Error
00:03 +200: ... shows ALT dashboard with socket state Error
00:03 +201: ... shows ALT dashboard with socket state Error
00:03 +202: ... shows ALT dashboard with socket state Error
00:03 +203: ... shows ALT dashboard with socket state Error
00:03 +204: ... shows ALT dashboard with socket state Error
00:03 +205: ... shows ALT dashboard with socket state Error
00:03 +206: ... shows ALT dashboard with socket state Error
00:03 +207: ... shows ALT dashboard with socket state Error
00:03 +208: ... shows ALT dashboard with socket state Error
00:03 +209: ... shows ALT dashboard with socket state Error
00:03 +210: ... shows ALT dashboard with socket state Error
00:03 +211: ... shows ALT dashboard with socket state Error
00:03 +212: ... shows ALT dashboard with socket state Error
00:03 +213: ... shows ALT dashboard with socket state Error
00:03 +214: ... shows ALT dashboard with socket state Error
00:03 +215: ... shows ALT dashboard with socket state Error
00:03 +216: ... shows ALT dashboard with socket state Error
00:03 +217: ... shows ALT dashboard with socket state Error
00:03 +218: ... shows ALT dashboard with socket state Error
00:03 +219: ... shows ALT dashboard with socket state Error
00:03 +220: ... shows ALT dashboard with socket state Error
00:03 +221: ... shows ALT dashboard with socket state Error
00:03 +222: ... shows ALT dashboard with socket state Error
00:03 +222: All tests passed!
```

### CLIENT-3 중간 검증
```text
$ cd apps/client && flutter test test/integrations/mattermost_push_host_integration_test.dart
00:00 +0: ...ient/test/integrations/mattermost_push_host_integration_test.dart
00:01 +0: ...ient/test/integrations/mattermost_push_host_integration_test.dart
00:01 +0: initialize calls push client init exactly once
00:01 +1: initialize calls push client init exactly once
00:01 +1: auto-login failure does not block initialize
[MattermostHost] Mattermost auto-login failed: Bad state: credentials missing
00:01 +2: auto-login failure does not block initialize
00:01 +2: navigation callbacks are assigned exactly once during initialize
00:01 +3: navigation callbacks are assigned exactly once during initialize
00:01 +3: notification stream remains consumable through integration
00:01 +4: notification stream remains consumable through integration
00:01 +4: All tests passed!
```

### 최종 검증
```text
$ cd apps/client && flutter test
00:00 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: ... /config/workspace/alt/apps/client/test/app/bootstrap_test.dart
00:01 +0: ... does not call Firebase or Mattermost and returns null
00:01 +1: ... does not call Firebase or Mattermost and returns null
00:01 +1: ... bootstrapAltClient initializes Firebase and Mattermost push host
00:01 +2: ... bootstrapAltClient initializes Firebase and Mattermost push host
00:01 +2: ... runAltClient renders AltClientApp shell without Firebase/push
00:01 +3: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +3: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +4: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +4: /config/workspace/alt/apps/client/test/integrations/mattermost_push_ho
st_integration_test.dart: auto-login failure does not block initialize
[MattermostHost] Mattermost auto-login failed: Bad state: credentials missing
00:02 +5: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +6: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +7: ... runAltClient renders AltClientApp shell without Firebase/push
00:02 +8: ... shows ALT dashboard shell with default disconnected socket state
00:02 +9: ... shows ALT dashboard shell with default disconnected socket state
00:02 +10: ... ALT dashboard shell with default disconnected socket state
00:02 +11: ... ALT dashboard shell with default disconnected socket state
00:02 +12: ... ALT dashboard shell with default disconnected socket state
00:02 +13: ... ALT dashboard shell with default disconnected socket state
00:02 +14: ... ALT dashboard shell with default disconnected socket state
00:02 +15: ... ALT dashboard shell with default disconnected socket state
00:02 +16: ... ALT dashboard shell with default disconnected socket state
00:02 +17: ... ALT dashboard shell with default disconnected socket state
00:02 +18: ... ALT dashboard shell with default disconnected socket state
00:02 +19: ... ALT dashboard shell with default disconnected socket state
00:02 +20: ... ALT dashboard shell with default disconnected socket state
00:02 +21: ... ALT dashboard shell with default disconnected socket state
00:02 +22: ... ALT dashboard shell with default disconnected socket state
00:02 +22: ... shows ALT dashboard with socket state Connecting
00:02 +23: ... shows ALT dashboard with socket state Connecting
00:02 +23: ... shows ALT dashboard with socket state Connected
00:02 +24: ... shows ALT dashboard with socket state Connected
00:02 +24: ... shows ALT dashboard with socket state Error
00:02 +25: ... shows ALT dashboard with socket state Error
00:02 +25: All tests passed!
```

---

> **[IMPLEMENTING AGENT — BEFORE SAVING] Have you filled in every implementation-owned section: completion table, implementation checklist, changes from plan, design decisions, and verification output?**
> If anything is blank, go back and fill it in before saving this file.
> Leave review-agent-only sections unchanged.

## 코드리뷰 결과

- 종합 판정: PASS
- 차원별 평가:
  - correctness: Pass
  - completeness: Pass
  - test coverage: Pass
  - API contract: Pass
  - code quality: Pass
  - plan deviation: Pass
  - verification trust: Pass
- 발견된 문제: 없음
- 다음 단계: PASS - active plan/review를 log로 아카이브하고 `complete.log` 작성 후 task directory를 `agent-task/archive/2026/05/m-operator-runtime-refactor/03_client_bootstrap/`로 이동한다. `m-operator-runtime-refactor` completion metadata만 보고하고 roadmap 수정은 런타임에 맡긴다.
