feat(core): Pearl automation note + notice registry

[zhubzy]

Summary

• Refactor hardcoded conversation history notices into a declarative RESPONSE_NOTICES registry
• Add Pearl automation note: "If this is a recurring task, ask Pearl to automate this"
• Bump versions to 0.1.195

Test plan

• Slack bot flow with capabilities → Pearl automation note appended
• No history → both "History Not Available" + Pearl note
• Non-Slack flow → no notices
• Capability sub-agent → no notices

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Released version 0.1.195 across bubble-core, bubble-runtime, and bubble-shared-schemas packages.

• Refactor

  • Restructured the notice system to use a data-driven approach with configurable conditions, improving the flexibility of notice display across different scenarios.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Version bumps applied across three packages (bubble-core, bubble-runtime, bubble-shared-schemas) from 0.1.194 to 0.1.195. The capability-pipeline refactors conversation-history notices from inline conditional logic to a data-driven notice system with filtering and formatting capabilities.

Changes

Cohort / File(s)	Summary
Version Updates packages/bubble-core/package.json, packages/bubble-runtime/package.json, packages/bubble-shared-schemas/package.json	Version bumped from 0.1.194 to 0.1.195 across all three packages.
Notice System Refactor packages/bubble-core/src/bubbles/service-bubble/capability-pipeline.ts	Replaced inline conversation-history notice logic with a data-driven RESPONSE_NOTICES array. Added applyResponseNotices helper to filter and format notices conditionally. Updated applyCapabilityPostprocessing to use the new notice system instead of applyConversationHistoryNotice.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Threads context #300 — Refactors conversation-history handling with related notice and parameter injection logic in capability pipeline.
• bump version #293 — Updates package versions across multiple packages in the same workspace.

Poem

🐰 Notices now bloom from data's bright seed,
No hardcoded strings, just what we need—
Filter and format with elegant grace,
Each notice finds its proper place! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: introducing a Pearl automation note and refactoring to a notice registry system. It directly matches the primary objectives of the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/response-notice-registry

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[cloudflare-workers-and-pages]

Deploying bubblelab-documentation with    Cloudflare Pages

Latest commit:	dbf688b
Status:	✅  Deploy successful!
Preview URL:	https://e8fc7f84.bubblelab-documentation.pages.dev
Branch Preview URL:	https://feat-response-notice-registr.bubblelab-documentation.pages.dev

View logs

[Copilot]

Pull request overview

This PR refactors the hardcoded conversation history notices into a declarative RESPONSE_NOTICES registry and adds a new Pearl automation note for recurring tasks. The changes improve maintainability by consolidating notice logic into a single, extensible data structure.

Changes:

• Refactored conversation history notices from inline if-else logic to a declarative registry pattern
• Added "Pearl automation" note that suggests automation for recurring tasks
• Version bumps across three packages to 0.1.195

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
packages/bubble-shared-schemas/package.json	Version bump to 0.1.195
packages/bubble-runtime/package.json	Version bump to 0.1.195
packages/bubble-core/package.json	Version bump to 0.1.195
packages/bubble-core/src/bubbles/service-bubble/capability-pipeline.ts	Refactored notice logic into RESPONSE_NOTICES registry, added Pearl automation note, renamed function from applyConversationHistoryNotice to applyResponseNotices