@agent-native/core-corpus 0.222.0-nightly-20261029004912 → 0.222.0

package/corpus/README.md

@@ -32,4 +32,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core-corpus/corpu
 
 ## Generated Counts
 
-- template files: 15109
+- template files: 15068

package/corpus/templates/analytics/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/analytics/CHANGELOG.md

@@ -52,6 +52,7 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Added
 
+- Outside assistants can open the Traffic dashboard in Analytics.
 - Tables, metric tiles and charts can show a number of seconds as a duration such as 16 min or 7.4 hours, and duration columns sort by time.
 
 ### Improved

package/corpus/templates/assets/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/brain/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/calendar/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/calendar/CHANGELOG.md

@@ -23,6 +23,10 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-10-22
 
+### Added
+
+- Outside assistants can open invite drafts in Calendar for review, with approval required before deleting all drafts.
+
 ### Improved
 
 - Approval links from a connected agent, such as Claude Code, now open the review inside the app, in its own theme.

package/corpus/templates/chat/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/clips/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/clips/CHANGELOG.md

@@ -3,6 +3,25 @@
 All notable user-facing changes to Clips are documented here. Open it any time
 from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-10-28
+
+### Improved
+
+- Clip menus use consistent text-only actions.
+- Recording menus use consistent text-only actions.
+- Recording options are easier to find and titles appear sooner
+
+### Fixed
+
+- Clips desktop preserves your server choice across updates and reconnects after temporary sign-in outages.
+- Recording chapters remain reachable when the list extends below the player.
+- The Chrome extension recorder has more room and a clearer feedback link.
+- The recorder refreshes storage connection status when opened
+
+### Changed
+
+- Earlier screen time is now off by default until you enable it in Labs.
+
 ## 2026-10-27
 
 ### Improved
@@ -1591,29 +1610,4 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 - Recordings now wait for uploaded media to play from storage before finishing, and playback falls back when a compressed storage copy is temporarily broken.
 
-## 2026-07-01
-
-### Improved
-
-- Clip uploads and Loom imports finish sooner by skipping the Builder.io compression wait after upload registration.
-- Recording controls are cleaner and the countdown uses shadowed numbers instead of a filled circle.
-- Shared clips can now copy a ready-to-send prompt that tells agents how to read transcripts, frames, and diagnostics.
-
-### Fixed
-
-- Chrome extension recordings now stream uploads while recording so saving is less likely to time out.
-- Chrome recording uploads now serialize chunks to avoid resumable upload offset races.
-- Clip embeds now render as a clean video-only player without extra page chrome or scrollbars.
-- Clip uploads and playback recover more reliably from storage timeouts.
-- Desktop recording setup no longer offers unsupported browser-tab capture in desktop app windows.
-- Dictation keeps listening through natural pauses and gives clearer start feedback.
-- Embedded player progress is easier to see on dark videos.
-- Loom imports now show clear guidance when Loom does not provide a downloadable video.
-- Move to folder now opens folder choices directly instead of starting an agent chat.
-- Preserve in-flight streaming uploads when the streaming kill switch is disabled mid-recording.
-- Recordings now recover when the final upload finishes but the browser receives a timeout instead of the saved clip response.
-- Redoing a paused desktop recording no longer leaves the recording controls disabled.
-- Shared clips now start playing and scrub instantly instead of buffering — recordings are made seekable on upload, and you can repair older clips
-- Stalled clip uploads now update in the library and surface as failed instead of staying stuck as uploading.
-
 For the full list of updates, see the [changelog folder](./changelog/).

package/corpus/templates/clips/desktop/src-tauri/src/lib.rs

@@ -431,7 +431,14 @@ pub fn run() {
 
             #[cfg(target_os = "macos")]
             {
-                app.set_activation_policy(tauri::ActivationPolicy::Accessory);
+                // `CLIPS_TRAY_REGULAR_APP=1` runs the tray as a normal app with a
+                // Dock tile so window-automation tools can target it when testing.
+                let policy = if std::env::var_os("CLIPS_TRAY_REGULAR_APP").is_some() {
+                    tauri::ActivationPolicy::Regular
+                } else {
+                    tauri::ActivationPolicy::Accessory
+                };
+                app.set_activation_policy(policy);
             }
 
             util::build_popover_window(app).map_err(|err| {

package/corpus/templates/content/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/content/CHANGELOG.md

@@ -3,17 +3,39 @@
 All notable user-facing changes to Agent-Native Content are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
+## 2026-10-28
+
+### Improved
+
+- Content menus use consistent text-only actions.
+
+### Fixed
+
+- Choosing Use saved after an interrupted recovery no longer lets the discarded edits come back later
+- Renaming a page while an agent edits it no longer stops your typing from saving or undoes the agent's edit on reload
+
 ## 2026-10-27
 
+### Improved
+
+- An AI suggestion in a comment thread uses the same group as suggested changes in the margin: its summary, edit count, Accept all and Reject all come first, and opening it shows each edit with the usual check and X.
+
 ### Fixed
 
+- Restoring page history preserves text without exposing unauthorized private callout images
 - An agent's Accept on words someone is still typing in returns the suggestion to pending instead of failing with a server error
 - Opening a page you can't access goes straight to the no-access screen without a brief error first, including when you come back to it
 
 ## 2026-10-26
 
+### Improved
+
+- A comment sent to AI says what it asks for on its send button (Reply, Suggest or Apply), and while the AI works, the thread names the model doing it.
+
 ### Fixed
 
+- Opening another comment thread while you're writing a new comment keeps what you wrote.
+- When the AI answers in a long comment thread, the card shows the start of its answer instead of jumping to the end, and scrolling past either end of a card no longer scrolls the page.
 - Document reads preserve bodies containing ordinary prose about starting an embed.
 
 ## 2026-10-25
@@ -69,6 +91,7 @@ time from the command menu (Cmd+K → "What's new").
 
 ### Added
 
+- Outside assistants can open shareable local-file copies in Content, with approval before creating or refreshing the copy.
 - Collection filters add does not contain, starts with, ends with, on or before, and on or after. Date filters can use relative days like today, and is within picks a range the way Notion does, such as the past 2 weeks or this month. A date without a time now counts as the whole day, so "on or before today" keeps rows from later today.
 - Blocks with several comment threads fold into one stack in the margin, which opens in place when you click it or a highlight
 
@@ -86,6 +109,7 @@ time from the command menu (Cmd+K → "What's new").
 
 ### Fixed
 
+- Pages using the live copy keep unsent edits through a refresh, closed tab, or lost connection.
 - A comment on the start of a block no longer highlights blocks added just above it.
 - Saving a Builder entry from Content no longer snaps back on the next refresh, and draft entries get a plain save that Builder shows right away.
 - The Page stays editable while Accept, Reject, Accept remaining, and Reject remaining save, and a failed save returns only that decision to pending

package/corpus/templates/content/changelog/{2026-10-17-choosing-use-saved-after-an-interrupted-recovery-no-longer-l.md → 2026-10-28-choosing-use-saved-after-an-interrupted-recovery-no-longer-l.md}

@@ -1,6 +1,6 @@
 ---
 type: fixed
-date: 2026-10-17
+date: 2026-10-28
 ---
 
 Choosing Use saved after an interrupted recovery no longer lets the discarded edits come back later

package/corpus/templates/content/changelog/{2026-10-17-renaming-a-page-while-an-agent-edits-it-no-longer-stops-your.md → 2026-10-28-renaming-a-page-while-an-agent-edits-it-no-longer-stops-your.md}

@@ -1,6 +1,6 @@
 ---
 type: fixed
-date: 2026-10-17
+date: 2026-10-28
 ---
 
 Renaming a page while an agent edits it no longer stops your typing from saving or undoes the agent's edit on reload

package/corpus/templates/crm/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/design/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/design/CHANGELOG.md

@@ -3,26 +3,54 @@
 All notable user-facing changes to Design are documented here. Open it any time
 from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-10-28
+
+### Fixed
+
+- Dragging a shape inside an SVG now moves it within the drawing, and X/Y, arrow keys, and align move it too.
+- Illustrations the agent draws as SVG now open as separate layers you can select, recolor, and retype.
+- Language and intelligence changes now work during voice chat.
+- Rename a frame by double-clicking its title
+
 ## 2026-10-27
 
+### Added
+
+- Comment threads have a new menu: send a thread to the agent, ask it to suggest changes, have it reply in the thread, or apply the changes and resolve the comment in one step.
+- Mention an AI agent in a comment, or ask it from the thread menu to reply, suggest or apply changes.
+
 ### Improved
 
+- Design ideas appear right away, with clear next steps after your first design.
+- Design runs recover from temporary builder errors and report incomplete edits clearly
+- New screens now fill in on the canvas as the agent writes them, with each element's frame drawn before its content appears
+- Start designs with ready-to-use role-based prompts, then refine, export, or share your first result from the canvas.
 - First-run setup makes free credits the primary path while keeping personal API keys one click away
 
 ### Fixed
 
+- A comment thread no longer opens by itself after you create a frame.
+- Design edits handle whitespace changes and identify stale snapshots clearly
+- Design generation now recovers from temporary connection and edit conflicts
+- Pinching to zoom over a comment pin or card now zooms the canvas instead of the browser.
+- Images removed by undo, redo, or replacement stay gone when their upload
+  finishes.
 - Design imports make your source and page choices clear, and checklist steps take you to the right place.
 
 ## 2026-10-26
 
 ### Improved
 
+- Comments have a new look: a cleaner thread card with agent badges and reactions, a reply box with mention chips and a toolbar, a Threads panel grouped by screen, and avatar pins on the canvas.
 - The editor chat shows its context chips again, so picked screens and layers stay visible and removable after Select closes.
 - The new-design prompt keeps Send as its main button; the mic still dictates.
 - Voice edits make the smallest matching change, say the new value out loud, and start faster
 
 ### Fixed
 
+- Rejected layer deletions no longer hide canvas content or clear the selection.
+- Undoing an image paste keeps it removed when the upload finishes.
+- Vector changes save reliably, and deleted pasted images stay deleted while uploads finish.
 - Suggested actions in the docked chat sit on one line just above the prompt bar.
 
 ## 2026-10-25
@@ -87,6 +115,7 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Added
 
+- Outside assistants can generate screens and open coding handoffs in Design, with approval before creating shareable code links.
 - Export compatible HTML frames for HubSpot email, or ask the agent to adapt existing content into a new email frame while preserving the original.
 - HubSpot conversion exports can verify that original link destinations are preserved.
 - Preview HubSpot emails with sample recipient names and button destinations without changing saved content.
@@ -2428,14 +2457,4 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 - Traditional Chinese copy now uses Taiwan terminology and clearer technical wording.
 
-## 2026-06-24
-
-### Added
-
-- Added a language picker and localized app chrome for supported languages.
-
-### Improved
-
-- Settings now link directly to Agent settings for model, API key, automation, and voice preferences.
-
 For the full list of updates, see the [changelog folder](./changelog/).

package/corpus/templates/dispatch/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/factory/.agents/skills/actions/references/provider-apis.md

@@ -93,3 +93,16 @@ cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
 keep quick scripts in the default foreground mode. Agents should continue
 other work between polls, and on `failed`/`timed_out` split the computation or
 persist intermediate progress with `workspaceWrite` and re-run.
+
+## HubSpot API versions
+
+Write new HubSpot code against a date-based API version (2026-09 or later),
+for example `POST /crm/objects/2026-09/contacts`, not `/crm/v3/...`. Only the
+date-based versions apply the portal's required-property rules to API writes:
+a create that leaves out a property the portal's create form requires, or a
+stage change missing a conditionally required property, is rejected with a
+400, while the same request on `/crm/v3/` succeeds. HubSpot also stops
+supporting v1-v3 after September 2027. Moving existing write code to a dated
+version changes its behavior, because writes that pass today can start failing
+validation, so migrate one app at a time and surface those 400s to the user.
+Reads behave the same on either version.

package/corpus/templates/factory/.agents/skills/review-latest-feedback/SKILL.md

@@ -21,6 +21,10 @@ not judged by ledgers, receipts, or checker output, so don't produce them.
 
 ## The contract
 
+The detailed Slack reaction and reply rules are in
+[slack-reaction-replies.md](references/slack-reaction-replies.md); read it before
+marking, replying to, or closing any Slack report.
+
 Slack reactions on a report's root message mean exactly this:
 
 | Mark | Meaning                                   | When to add                                                                                      |
@@ -43,7 +47,8 @@ might need to take back. Every 👀 you add ends the run with a reply, plus
 either ✅ or 🎫, or a fix PR that is still open and lists the report (its
 merge adds the ✅). A 👀 with no follow-up is the most common complaint about this workflow.
 
-Every claimed report gets **one** reply in its thread per outcome. People
+Every claimed report gets **one** reply in its thread per outcome. The one exception is
+the merged `✅` close-out after an in-review reply, which gets no second reply. People
 have pushed back on replies that were long, technical, condescending, vague
 about who does what next, or that handed them work. Each reply must be:
 
@@ -261,9 +266,10 @@ apart from Steve's own 👀.
 - **Prove it.** The check has to fail with the fix's source changes put
   back to `main` and pass with them. A check that passes without your fix
   doesn't test the bug: write one that does. Tests that read source text
-  never count. For a purely visual fix, a before and after screenshot of the
-  signed-in app stands in. Put the proof under the report in the PR's
-  `Reports` section.
+  never count. For a purely visual fix, before and after screenshots are
+  evidence for a person to inspect, not automated proof. Before merging, a
+  human must open both images and confirm they show the reported change. Put
+  the evidence under the report in the PR's `Reports` section.
 - **Two misses, then stop guessing.** If two attempts don't turn the check
   green, stop editing and capture the real failure first (stack, logs, the
   reporter's actual data). If that doesn't settle it within about 30