[susumutomita]

Summary

「サンプルのバトルにレッドチームの定義がないから何もテストできない」というご指摘の原因は、problems submodule の pin が古かったことでした（de6a8f5、サンプル Battle に red team が付く前のコミット）。実は disruption の定義は upstream（TenkaCloudChallenge）に既にあります。pin を a7ac11e（main）に bump して取り込みます。

bump で入る変更（de6a8f5..a7ac11e、いずれも安全）:

• refactor README #38 hello-world-battle に実用的な red team: frontend-down disruption（ssm-run-command で nginx 停止 → frontend probe が 200 を返さず加点停止 → ADR-029 に従い 600 秒後に自動復旧）。これで Disruptions タブが空でなくなり、運営が機能をテストできるようになります。
• feat: Makefile で一括起動コマンド (make start-all) を追加 #39 microservice-migration-battle: description に red team 説明を追記。
• feat: Control Plane UI の Docker ビルド CI チェックを追加 #40 problem 「check engine」 validator 追加。
• docs: Quick Start Guide を最新化 #41 microservice teaser の壊れた ASCII 図を除去。

apps/participant-portal/src/plugins/props-builder.test.ts も更新: hello-world-battle を「disruptions 無し」の例に使っていたが、red team が付いたので例を challenge に差し替え、新しい public disruption (frontend-down / publicHint=true) を pin。

⚠️ 反映に deploy が必要

カタログは event-handler Lambda に build 時 bundle されるため、live で見るには problem-deploy backend の再 deploy が必要です（既存の "test" イベントは、disruption がイベント作成時 snapshot か live catalog 参照かで挙動が変わります。確実には bump 反映後に新規イベントを作成）。

Test plan

• make validate-problems: bump 後の 7 metadata すべて有効（hello-world-battle の disruption が SCHEMA を通る）。
• props-builder.test.ts: 空ケースを challenge に変更、hello-world-battle が frontend-down(publicHint=true) を返すことを pin。participant-portal 594 テスト green、coverage 100%。
• make harness / make before-commit green（全 SPA build がカタログ更新込みで通る）。

Regression analysis

• submodule の gitlink 更新 + テスト 1 ファイルのみ。bump 範囲は metadata 2 件 + clone 内 validator + teaser doc で、テンプレート/スキーマの破壊的変更なし。
• validate-problems / 全 SPA build green で、新カタログがアプリの build-time discovery と整合することを確認。

Physical impact

• submodule pin（gitlink）の更新。CDK / CFn / IAM への変更なし → NO-OP（インフラ差分なし）。ただしカタログ内容が変わるため、problem-deploy backend を再 deploy すると event-handler Lambda の bundle が更新される。

[coderabbitai]

Warning

Review limit reached

@susumutomita, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 51 minutes and 31 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e3fe5407-aa7f-4175-a345-1bd3739e1299

📥 Commits

Reviewing files that changed from the base of the PR and between c048824 and 2170af3.

📒 Files selected for processing (2)

• apps/participant-portal/src/plugins/props-builder.test.ts
• problems

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-problems-redteam

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.75%. Comparing base (c048824) to head (2170af3).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1708   +/-   ##
=======================================
  Coverage   92.75%   92.75%           
=======================================
  Files         434      434           
  Lines       11900    11900           
  Branches     3655     3655           
=======================================
  Hits        11038    11038           
  Misses        295      295           
  Partials      567      567           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.