kaizen: Kaizen Loop payload の summary を trim し、空/空白のみなら検証エラーにしました。 (#77)

[s-hiraoku]

Closes #77

Summary

Kaizen Loop payload の summary を trim し、空/空白のみなら検証エラーにしました。
公開スキーマと回帰テストを更新し、README の契約文言も明確化しました。

Builder notes

Protected path changed: schemas/kaizen-loop-payload.schema.json. Verification passed: npm test; npm run validate:json; required shared skill files exist.

Provider evidence:

• codex: exitCode=0, status=selected, failureClass=none, fallbackReason=none, payloadSource=last-message
  Selected backend: codex
  Final payload source: last-message

Verification

• npm test
• npm run validate:json
• test -f skills/gh-link-issue-pr/SKILL.md && test -f skills/kaizen-bug-router/SKILL.md && test -f skills/pr-guardian/SKILL.md

Verifier

verifier: open_pr_with_warning
summary: Open PR with warning and 2 should_fix item(s); risk is medium.
notes: evidence_grade=reported
risk=medium
confidence=60
should_fix=Verification output contains a non-blocking risk signal.; Verification output contains a non-blocking risk signal.

Kaizen risk policy

Verifier cleared PR with warning: Open PR with warning and 2 should_fix item(s); risk is medium.

Changed files: 6
Changed lines: 41

[coderabbitai]

Warning

Review limit reached

@s-hiraoku, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 380dbe92-65ef-40c1-9c66-0e138f5782e6

📥 Commits

Reviewing files that changed from the base of the PR and between 84a2967 and d2ad276.

⛔ Files ignored due to path filters (2)

• dist/types/KaizenLoopPayload.d.ts.map is excluded by !**/dist/**, !**/*.map
• dist/types/KaizenLoopPayload.js is excluded by !**/dist/**

📒 Files selected for processing (4)

• README.md
• schemas/kaizen-loop-payload.schema.json
• src/types/KaizenLoopPayload.ts
• test/types/KaizenLoopPayload.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kaizen/issue-77-scout-reject-empty-kaizen-payload-summaries

---

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.}

[s-hiraoku]

PR Guardian pass 1/5 complete.

Final mergeability and checks:

• PR is open, ready for review, non-draft.
• mergeStateStatus: CLEAN; mergeable: MERGEABLE.
• Required branch protection on main requires the test check and conversation resolution; pull request approval is not required by branch protection.
• gh pr checks reports test passing and CodeRabbit passing.

CI runs watched:

• Watched CI run 28729286285 with gh run watch --exit-status; it had already completed successfully.

Fixes pushed:

• None. No actionable failing checks or unresolved actionable review feedback were found.

Feedback addressed:

• Paginated GraphQL review-thread sweep found 0 review threads, so there are no unresolved inline threads to address or resolve.
• PR reviews sweep found 0 submitted reviews.
• PR comments sweep found 1 CodeRabbit status/rate-limit comment. It does not request a code change; no action needed.

Skipped or non-blocking items:

• Check annotation warning: GitHub Actions reports Node.js 20 action runtime deprecation for actions/checkout and actions/setup-node. This is outside the PR diff, the required test check passed, and it is not blocking this PR. It should be handled separately as workflow maintenance if desired.

Remaining blockers:

• None found. Do not merge was respected.