chore(examples): Correctly tag inputs as Cell

[seefeldb]

pattern, recipe, lift and handler now consistently produce factories that strip any Cell annotations, so that the type the developer declares matches the internal view while external callers can call with or without Cells.

---

Also fixed TypeScript types in patterns by:

1. Adding Cell<> wrappers to input schema properties where UI components expect CellLike values:

   • recipes: bgCounter, email-summarizer, gcal, gmail-importer, input, research-report, rss
   • patterns: chatbot, ct-checkbox-*, ct-list, ct-select, fetch-data, note

2. Removing extraneous asCell: true from simpleValue.tsx that was causing .length property errors

3. Making recipe input properties optional where they have Default<> values and adding fallback handling in recipe implementations

4. Fixing Cell import from type-only to regular import in note.tsx

---

Summary by cubic

Correctly tagged example inputs as Cell to match UI components and Default handling, fixing type errors across patterns and recipes. Updated API types to strip Cell wrappers at module boundaries so patterns/recipes accept plain shapes while callers can pass cells; all examples now pass type checks.

• Bug Fixes

  • Wrapped input schema properties in Cell<Default<...>> where UI expects CellLike values (chatbot, checkbox, list, select, fetch-data, note; bgCounter, email-summarizer, gcal, gmail-importer, input, research-report, rss).
  • Made inputs with Default optional and added fallback initialization inside recipes.
  • Removed incorrect asCell: true from simpleValue.tsx to fix .length errors.
  • Fixed Note to use a regular Cell import; simplified Chat/Note creation calls.
  • Updated email-summarizer and gcal to mark settings as cells and derive reactive prompts; adjusted gmail-importer/rss settings types.
  • Passed CellLike context to common-iframe in the iframe integration.

• Refactors

  • Added StripCell and applied it to pattern(), recipe(), lift(), and handler() overloads to normalize inputs/outputs (strip cell wrappers) while preserving developer ergonomics.

^{Written for commit 7cebc23. Summary will update automatically on new commits.}

[cubic-dev-ai]

4 issues found across 21 files

Prompt for AI agents (all 4 issues)

Understand the root cause of the following 4 issues and fix them.


<file name="packages/patterns/chatbot-outliner.tsx">

<violation number="1" location="packages/patterns/chatbot-outliner.tsx:128">
`appendOutlinerNode` expects a `Cell&lt;Outliner&gt;` and calls `state.outline.key(...)`. When `outline` is omitted, this new fallback returns a plain object, so the tool crashes because `.key` is missing. Please wrap the default in `Cell.of(...)` to keep providing a cell.</violation>
</file>

<file name="packages/patterns/chatbot-note-composed.tsx">

<violation number="1" location="packages/patterns/chatbot-note-composed.tsx:59">
newNote no longer forwards the provided title/content to Note(), so created notes ignore the user-supplied values and always use the defaults. Please pass args.title/content when instantiating the note.</violation>
</file>

<file name="recipes/research-report.tsx">

<violation number="1" location="recipes/research-report.tsx:9">
Marking the `title` input as a Cell breaks this recipe: the callback still treats `title` like a plain string (`title || &quot;Untitled Research Report&quot;`), so the fallback never triggers and `[NAME]` receives a Cell object instead of the expected string. Either keep `title` as a string or update the recipe logic to unwrap the Cell.</violation>
</file>

<file name="recipes/simpleValue.tsx">

<violation number="1" location="recipes/simpleValue.tsx:53">
Dropping the `asCell` marker turns `values` into a plain `string[]`, but the handlers and `derive` logic in this recipe expect a `Cell&lt;string[]&gt;`. That breaks reactivity and the handler state contract.</violation>
</file>

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}