release(life-call): promote CORE 8e DAILY journey#336
Conversation
…-20260722 feat(life-call): verify CORE 8e DAILY journey
|
Warning Review limit reached
Next review available in: 40 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough旅行イベントから往路レポートを生成し、ローカル時刻とHTMLエスケープを考慮したTelegram通知を追加しました。スケジューラーの依存性注入、ヘルパーブロック除外、日次ジャーニー契約テスト、Writer Loop記録も更新しています。 Changes日次旅行ジャーニー
Writer Loop記録更新
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant Scheduler
participant Calendar
participant Travel
participant Telegram
Scheduler->>Travel: fillTravel()
Travel->>Calendar: create travel block
Calendar-->>Travel: creation result
Travel-->>Scheduler: outboundReports
Scheduler->>Telegram: formatted travel notification
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/loop-engineering/47-writer-loop-quality-and-self-improvement.md (1)
743-750: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winE1/E2証跡に再現可能な参照を追加してください。
テスト件数・ハッシュ・
adapter外直呼び0だけでは、どのコマンド、artifact、日時、検索範囲で確認した結果かを独立再現できません。各証跡に検証コマンド、artifact path、実行日時、grep対象範囲を併記してください。Also applies to: 756-757
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/loop-engineering/47-writer-loop-quality-and-self-improvement.md` around lines 743 - 750, Update the E1/E2 evidence entries in the document to include reproducible verification details for every reported result: the exact command used, artifact path, execution timestamp, and grep/search scope. Cover the entries around the E1 and E2 test, probe, archive, ledger, and artifact-only review claims, while preserving the existing counts, hashes, and conclusions.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/life-call/scheduler.js`:
- Around line 296-321: In travelUserOnce, isolate each sendMessage call within
the outboundReports loop in its own try/catch so one Telegram failure does not
stop subsequent reports. Log or otherwise handle the individual notification
error, then always return the successful fillTravel result r regardless of
notification failures.
---
Nitpick comments:
In `@docs/loop-engineering/47-writer-loop-quality-and-self-improvement.md`:
- Around line 743-750: Update the E1/E2 evidence entries in the document to
include reproducible verification details for every reported result: the exact
command used, artifact path, execution timestamp, and grep/search scope. Cover
the entries around the E1 and E2 test, probe, archive, ledger, and artifact-only
review claims, while preserving the existing counts, hashes, and conclusions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 125aa24f-8e9f-4e30-ae77-5f77fb57ffe4
📒 Files selected for processing (7)
apps/life-call/lib/i18n.jsapps/life-call/lib/late-notice.jsapps/life-call/lib/travel.jsapps/life-call/package.jsonapps/life-call/scheduler.jsapps/life-call/test/daily-journey-contract.test.jsdocs/loop-engineering/47-writer-loop-quality-and-self-improvement.md
…-20260722 fix(life-call): isolate CORE 8e report failures
1 participant
Summary
Verification
Summary by CodeRabbit
新機能
改善
テスト