npm - @clipboard-health/ai-rules - Versions diffs - 2.43.1 → 2.43.3 - Mend

@clipboard-health/ai-rules 2.43.1 → 2.43.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@clipboard-health/ai-rules",
-  "version": "2.43.1",
+  "version": "2.43.3",
   "description": "Pre-built AI agent rules for consistent coding standards.",
   "keywords": [
     "ai",

package/skills/cb-babysit/SKILL.md CHANGED Viewed

@@ -19,9 +19,9 @@ Resolve bundled "./scripts" paths relative to SKILL.md.
 The skill uses two sentinels with visible footer lines.
-**Addressed sentinel**: `<sub>🤖 <code>cb-babysit:addressed v1 core@3.22.1</code></sub>`. Appended on its own line at the end of every reply the skill posts so re-runs know which threads and review-body comments are already handled. Dedupe also recognizes the legacy `babysit-pr:addressed v1` prefix from before this skill was renamed.
+**Addressed sentinel**: `<sub>🤖 <code>cb-babysit:addressed v1 core@3.22.3</code></sub>`. Appended on its own line at the end of every reply the skill posts so re-runs know which threads and review-body comments are already handled. Dedupe also recognizes the legacy `babysit-pr:addressed v1` prefix from before this skill was renamed.
-**Follow-up sentinel**: `<sub>🤖 <code>cb-babysit:followup v1 core@3.22.1</code></sub>`. Attached to replies that defer an out-of-scope comment as a tracked follow-up. The sentinel is additive: the post-reply scripts still append the `addressed` sentinel at the end.
+**Follow-up sentinel**: `<sub>🤖 <code>cb-babysit:followup v1 core@3.22.3</code></sub>`. Attached to replies that defer an out-of-scope comment as a tracked follow-up. The sentinel is additive: the post-reply scripts still append the `addressed` sentinel at the end.
 **Sentinel recency rules.** The script emits a per-thread `activityState` with three values. Step 6a owns the handling rules for each state.
@@ -247,7 +247,7 @@ Body templates (the script appends the `addressed` sentinel if missing):
 - **Agree**: `Addressed in <commit-url>. <one-line what-changed>.`
 - **Disagree**: `Leaving current behavior. <reasoning>.`
 - **Already fixed**: `Already handled by <commit-url-or-file:line>. <brief pointer>.`
-- **Defer**: `Out of scope for this PR; this looks like follow-up work rather than something introduced or required by this change. <one-line rationale or pointer if useful>.\n\n<sub>🤖 <code>cb-babysit:followup v1 core@3.22.1</code></sub>`
+- **Defer**: `Out of scope for this PR; this looks like follow-up work rather than something introduced or required by this change. <one-line rationale or pointer if useful>.\n\n<sub>🤖 <code>cb-babysit:followup v1 core@3.22.3</code></sub>`
 For Defer replies, include the follow-up sentinel on its own line as shown. The script will append the `addressed` sentinel after it on its own line, so the final body ends with the follow-up sentinel followed by a blank line followed by the `addressed` sentinel. `grep cb-babysit:followup` finds the deferral and `grep cb-babysit:addressed` still marks the thread handled for dedupe.
@@ -263,7 +263,7 @@ The PR-level summary should:
 - Group by source. Use `## Review-body findings` for step-7 work and `## Conversation-tab comments` for step-6b work. Omit a section if its list is empty.
 - Inside each section, group verdicts under **Agree / Disagree / Already fixed / Deferred (out of scope)** subheadings. Omit a subheading if its list is empty.
-- Under **Deferred (out of scope)**, list each deferred item as a bullet, followed on its own line by `<sub>🤖 <code>cb-babysit:followup v1 core@3.22.1</code></sub>` so grep catches them individually.
+- Under **Deferred (out of scope)**, list each deferred item as a bullet, followed on its own line by `<sub>🤖 <code>cb-babysit:followup v1 core@3.22.3</code></sub>` so grep catches them individually.
 - Include the commit URL for fixes.
 - End with a fenced fingerprint block listing every current fingerprint (addressed and deferred) one per line. Include both `reviewBodyComments[].fingerprint` (whole-body, one per automated review) and `activeIssueComments[].fingerprint` (per Conversation-tab comment). Future runs dedupe by matching these against `priorBabysitSentinels`.

package/skills/cb-babysit/scripts/_sentinel.sh CHANGED Viewed

@@ -10,7 +10,7 @@
 SENTINEL_PREFIX='cb-babysit:addressed v1 '
 LEGACY_SENTINEL_PREFIX='babysit-pr:addressed v1 '
-SENTINEL='<sub>🤖 <code>cb-babysit:addressed v1 core@3.22.1</code></sub>'
+SENTINEL='<sub>🤖 <code>cb-babysit:addressed v1 core@3.22.3</code></sub>'
 # Bot author allowlist (JSON array literal). Used by unresolvedPrComments.sh
 # as a fallback when GraphQL's `author.__typename == "Bot"` misses a GitHub

package/skills/cb-ship/SKILL.md CHANGED Viewed

@@ -40,10 +40,11 @@ Resolve bundled "./references" paths relative to SKILL.md.
    - Session: [Resume command from 6a] (omit if none)
    - Existing changes: [Uncommitted changes that remain outside the shipped scope] (omit if none)
-   🚀 [Complete url] (e.g., `https://github.com/clipboardhealth/core-utils/pull/123`) 🚀
+   🚀 [Complete url] 🚀
    ```
-   Keep the PR as the final line and visually separate it from everything else
-   with a blank line. Use the middle section only for meaningful behavior or
-   outcome details. Put lower-priority handoff metadata and caveats under
-   `Details`.
+   Keep the PR as the final line using a complete URL, for example,
+   `https://github.com/clipboardhealth/core-utils/pull/123`. Visually separate
+   it from everything else with a blank line. Use the middle section only for
+   meaningful behavior or outcome details. Put lower-priority handoff metadata
+   and caveats under `Details`.

package/skills/cb-ship/references/pr-template.md CHANGED Viewed

@@ -17,5 +17,5 @@ Concisely explain the user intent from session history and the meaningful behavi
 Optional, don't fabricate: ticket links, rollout plan, residual risk, or specific areas for reviewers to focus.
-<sub>🤖 <code>cb-ship:created v1 core@3.22.1</code></sub>
+<sub>🤖 <code>cb-ship:created v1 core@3.22.3</code></sub>
 ```

package/skills/flaky-debug/references/root-cause-kb/README.md CHANGED Viewed

@@ -18,6 +18,7 @@ When adding an entry, keep the same sections used by the seeded entries:
 | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
 | `element was detached from the DOM`, `element is not stable`, open dialog or sheet disappears during a mutation/refetch                      | Overlay is rendered below a query-driven mapped row that is reconciled or removed                 | [Query-driven list dialog teardown](./query-driven-list-dialog-teardown.md)               |
 | Dialog title or sheet content never becomes stably visible after it opened                                                                   | The owning list item remounted while the overlay was open                                         | [Query-driven list dialog teardown](./query-driven-list-dialog-teardown.md)               |
+| Open menu or form detaches as a delayed provider token arrives; route lifecycle shows a parent remount                                       | A token-dependent provider topology replaced the authenticated application subtree                | [Query-driven list dialog teardown](./query-driven-list-dialog-teardown.md)               |
 | Fingerprints `33deef731a10`, `2d93cd67b48a`                                                                                                  | Home Health instance of query-driven overlay ownership                                            | [Query-driven list dialog teardown](./query-driven-list-dialog-teardown.md)               |
 | `Cognito user '<email>' does not exist`, `UserNotFoundException` immediately after a successful user-create response                         | Consumer is rediscovering an opaque Cognito username through an eventually consistent email alias | [Cognito email-alias eventual consistency](./cognito-email-alias-eventual-consistency.md) |
 | Email-based Cognito Admin mutation fails while the same user exists under `from_admin_<uuid>`                                                | Strong username identity was discarded at the producer boundary                                   | [Cognito email-alias eventual consistency](./cognito-email-alias-eventual-consistency.md) |

package/skills/flaky-debug/references/root-cause-kb/query-driven-list-dialog-teardown.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Query-Driven List Dialog Teardown
-Last reviewed: 2026-07-16.
+Last reviewed: 2026-07-17.
 ## Symptom signatures
@@ -8,6 +8,8 @@ Last reviewed: 2026-07-16.
 - A dialog or sheet opens, then its title/content disappears or never becomes stably visible.
 - The failure moves between actions on different rows of the same query-backed list.
 - A mutation succeeds, but the confirmation interaction or post-success assertion loses the overlay.
+- An already-open menu or other interaction surface detaches when a delayed
+  provider token changes the authenticated application's React topology.
 - Known families: `33deef731a10` and `2d93cd67b48a`.
 ## Mechanism
@@ -16,9 +18,15 @@ The overlay is owned by a component rendered beneath a mapped query result, such
 The decisive test is structural: if deleting or replacing the launching row also destroys the open overlay, the product has this mechanism even when the visible failure is a locator timeout.
+The same structural mechanism can occur above the list. A token-dependent
+provider wrapper that returns raw application children before bootstrap and
+wraps those children after bootstrap replaces the authenticated route subtree.
+That higher ancestor remount destroys menus, drawers, and form state even after
+list-owned dialogs have been hoisted into a stable host.
 ## Affected repositories and surfaces
-- `cbh-admin-frontend`: Home Health case and visit action dialogs; other query-driven list dialogs found by the repository sweep.
+- `cbh-admin-frontend`: Home Health case and visit action dialogs; other query-driven list dialogs found by the repository sweep; authenticated route state beneath the Knock bootstrap boundary.
 - `cbh-mobile-app`: placement sign-on-bonus and badge-history sheets; workplace-review comment and reply action sheets.
 - Any React surface that renders modal state and overlay JSX inside a query-backed `.map()` descendant.
@@ -31,16 +39,19 @@ The decisive test is structural: if deleting or replacing the launching row also
 The durable Home Health fix is [cbh-admin-frontend#7574](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7574). Repository-wide follow-ups landed in [cbh-admin-frontend#7569](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7569), [cbh-mobile-app#12857](https://github.com/ClipboardHealth/cbh-mobile-app/pull/12857), and [cbh-mobile-app#12860](https://github.com/ClipboardHealth/cbh-mobile-app/pull/12860).
+[cbh-admin-frontend#7608](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7608) fixed the provider-topology variant. It keeps the authenticated application children at a stable React position and conditionally mounts only the Knock guide consumers beneath the token-dependent providers. Component coverage proved that delayed and immediate tokens preserve the application mount and local state; a rate-negotiation E2E fault injection holds the Knock-token response across an open interaction and requires exactly one end-negotiation request.
 ## What failed and why
 - Repeated `toPass` blocks, response waits, locator retries, failure trackers, and expanded timeouts hardened whichever Home Health step failed most recently but left overlay ownership unchanged. The family recurred across [STAFF-1329](https://linear.app/clipboardhealth/issue/STAFF-1329), [STAFF-1369](https://linear.app/clipboardhealth/issue/STAFF-1369), [STAFF-1495](https://linear.app/clipboardhealth/issue/STAFF-1495), [STAFF-1554](https://linear.app/clipboardhealth/issue/STAFF-1554), [STAFF-1582](https://linear.app/clipboardhealth/issue/STAFF-1582), [STAFF-1673](https://linear.app/clipboardhealth/issue/STAFF-1673), and [STAFF-1685](https://linear.app/clipboardhealth/issue/STAFF-1685).
 - Preserving modal state across a remount did not preserve the DOM node Playwright or a user was interacting with. The Team Members recurrence from [STAFF-1422](https://linear.app/clipboardhealth/issue/STAFF-1422) to [STAFF-1459](https://linear.app/clipboardhealth/issue/STAFF-1459) is the precedent.
 - Pausing backing-list observers and deferring invalidations in [cbh-admin-frontend#7559](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7559) reduced the race window but was explicitly an interim mitigation: another ancestor update could still remove the row. The hoisted host later deleted that workaround.
+- Hoisting Home Health dialogs in [cbh-admin-frontend#7574](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7574) correctly removed their query-row ownership, but it could not preserve the earlier action menu or the route when the delayed Knock token replaced a higher provider boundary. [STAFF-1856](https://linear.app/clipboardhealth/issue/STAFF-1856) established that failed scope with route lifecycle telemetry and immediate post-remount Knock requests.
 - Splitting the E2E test alone would reduce blast radius and improve fingerprints, but it would not fix the user-facing overlay teardown.
 ## Current status
-Fixed for the known admin and mobile surfaces covered by [STAFF-1789](https://linear.app/clipboardhealth/issue/STAFF-1789), [STAFF-1790](https://linear.app/clipboardhealth/issue/STAFF-1790), [STAFF-1796](https://linear.app/clipboardhealth/issue/STAFF-1796), [STAFF-1797](https://linear.app/clipboardhealth/issue/STAFF-1797), and [STAFF-1806](https://linear.app/clipboardhealth/issue/STAFF-1806). Treat future instances as the same mechanism when overlay ownership is still below a replaceable query row; extend the stable-host pattern and guard rather than adding per-test waits.
+Fixed for the known query-row surfaces covered by [STAFF-1789](https://linear.app/clipboardhealth/issue/STAFF-1789), [STAFF-1790](https://linear.app/clipboardhealth/issue/STAFF-1790), [STAFF-1796](https://linear.app/clipboardhealth/issue/STAFF-1796), [STAFF-1797](https://linear.app/clipboardhealth/issue/STAFF-1797), and [STAFF-1806](https://linear.app/clipboardhealth/issue/STAFF-1806). The admin Knock provider-topology variant is fixed by [cbh-admin-frontend#7608](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7608); the corresponding mobile topology remains tracked by [STAFF-1872](https://linear.app/clipboardhealth/issue/STAFF-1872). Treat future instances as the same mechanism when interaction ownership remains below any replaceable ancestor; make the ancestor composition stable or move interaction ownership above that boundary rather than adding per-test waits.
 ## Evidence
@@ -50,3 +61,6 @@ Fixed for the known admin and mobile surfaces covered by [STAFF-1789](https://li
 - [cbh-admin-frontend#7574](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7574): hoisted host and deletion of the temporary guard.
 - [cbh-mobile-app#12857](https://github.com/ClipboardHealth/cbh-mobile-app/pull/12857): mobile sheet hoists and architecture guard.
 - [cbh-mobile-app#12860](https://github.com/ClipboardHealth/cbh-mobile-app/pull/12860): indirect workplace-review descendants hoisted after the syntactic guard could not detect them.
+- [STAFF-1846](https://linear.app/clipboardhealth/issue/STAFF-1846): source deep dive and prior-attempt dossier for the provider-topology fix.
+- [STAFF-1856](https://linear.app/clipboardhealth/issue/STAFF-1856): provider-topology recurrence, route lifecycle telemetry, and the failed scope of the dialog-only hoist.
+- [cbh-admin-frontend#7608](https://github.com/ClipboardHealth/cbh-admin-frontend/pull/7608): stable application composition plus delayed-token and fault-injection regression coverage.