chore(persona-kit): refresh Relayfile trigger catalog

[khaliqgant]

Summary

• bump @relayfile/adapter-core to ^0.3.59 in @agentworkforce/persona-kit and @agentworkforce/runtime
• refresh pnpm-lock.yaml so local deploy tooling resolves the catalog that includes Neon sync-delta triggers
• add a persona-kit regression test proving Neon trigger events lint clean locally

Why

The Neon pipeline is registered server-side, but local agentworkforce deploy still warns triggers.neon: provider not in known-trigger registry because persona-kit/runtime were pinned to adapter-core versions that predate Neon. This makes the local lint path catch up to the published adapter catalog.

Validation

• pnpm --filter @agentworkforce/persona-kit test
• pnpm --filter @agentworkforce/deploy test
• pnpm --filter @agentworkforce/runtime test

[coderabbitai]

Warning

Review limit reached

@khaliqgant, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 6 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cdfc6642-ace6-4df7-8ccf-455c8fe651e6

📥 Commits

Reviewing files that changed from the base of the PR and between 6857d0a and 1620c99.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• packages/persona-kit/package.json
• packages/persona-kit/src/triggers.test.ts
• packages/runtime/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/neon-trigger-catalog-bump

---

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

[gemini-code-assist]

Code Review

This pull request upgrades the @relayfile/adapter-core dependency to version ^0.3.59 in both packages/persona-kit and packages/runtime. It also adds a test case in packages/persona-kit/src/triggers.test.ts to ensure lintTriggers accepts Neon sync-delta trigger events. No review comments were provided, so there is no additional feedback.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[khaliqgant]

Correction / scope clarification: this PR is not required to unblock the Neon deploy.

Published @agentworkforce/persona-kit@4.1.4 already depends on @relayfile/adapter-core@^0.3.50, and @agentworkforce/runtime@4.1.4 already depends on ^0.3.44; both ranges allow @relayfile/adapter-core@0.3.59. The local deploy warning can be cleared in consuming repos by refreshing their lockfile / install so adapter-core@0.3.59 is selected.

So this PR should be treated as optional hardening only: it raises the minimum declared adapter-core range and adds regression coverage that Neon sync-delta triggers lint clean locally. It should not be considered a release gate for the Neon deploy.