[khaliqgant]

Summary

Deploying any persona with a telegram trigger (agents repo's hn-monitor, inbox-buddy, joke-bot) warns at compile/deploy time:

triggers.telegram: provider "telegram" is not in the known-trigger registry; trigger names will not be linted

Root cause: persona-kit's lintTriggers sources its known-trigger list from @relayfile/adapter-core's KNOWN_TRIGGER_CATALOG, but persona-kit/package.json pins it via ^0.3.60 — a caret range capped below 0.4.0. relayfile-adapters has actually published telegram's catalog entry since 0.4.1 (AgentWorkforce/relayfile-adapters#220, confirmed by extracting the real npm tarballs for 0.4.1 through the current 0.5.1 — telegram is in all of them). persona-kit just can never resolve to a version that has it.

(I initially misdiagnosed this as telegram never being published at all and filed AgentWorkforce/relayfile-adapters#240 — closed that with a correction once I actually unpacked the published tarballs and found telegram was there all along.)

Change

• Bump @relayfile/adapter-core from ^0.3.60 to ^0.5.1 in packages/persona-kit/package.json, update pnpm-lock.yaml.
• Left packages/runtime's identical ^0.3.60 pin alone — runtime only imports @relayfile/adapter-core/vfs-client, unrelated to trigger linting, so out of scope for this fix.

Verification

• pnpm --filter @agentworkforce/persona-kit install resolves @relayfile/adapter-core to 0.5.1 inside packages/persona-kit/node_modules.
• npm test in packages/persona-kit — 286/286 pass.
• npm run typecheck — clean.
• Direct functional check against the built package:

  lintTriggers({ triggers: { telegram: [{ on: 'message' }] } })
  // before: [{ level: 'warning', code: 'unknown_provider', provider: 'telegram', ... }]
  // after:  []

Note: merging this doesn't make the warning disappear for users immediately — persona-kit/cli/agentworkforce still need a lockstep release cut before the new agentworkforce CLI picks it up.

🤖 Generated with Claude Code

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2fee35de-2623-4fc9-8376-9e5aaa6bb7aa

📥 Commits

Reviewing files that changed from the base of the PR and between 6186b94 and c63b78e.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• packages/persona-kit/package.json
• packages/runtime/package.json

---

📝 Walkthrough

Walkthrough

@relayfile/adapter-core is upgraded from ^0.3.60 to ^0.5.1 in the Persona Kit and Runtime package manifests.

Changes

Adapter core upgrade

Layer / File(s)	Summary
Update adapter-core dependency constraints packages/persona-kit/package.json, packages/runtime/package.json	Both package manifests update @relayfile/adapter-core from ^0.3.60 to ^0.5.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

• Issue 249 — Covers the requested @relayfile/adapter-core version cutover in the same two packages.

Suggested reviewers: github-actions[bot]

Poem

A bunny bumps the version bright,
From sixty-three to five-oh-one’s flight.
Two package burrows share the glow,
Their adapter hops now onward go.
Ears up high—release in sight!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the persona-kit dependency bump to pick up the Telegram trigger catalog.
Description check	✅ Passed	The description is directly about the adapter-core version bump and its impact on Telegram trigger linting.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/persona-kit-adapter-core-telegram

---

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

[gemini-code-assist]

Code Review

This pull request updates the @relayfile/adapter-core dependency from ^0.3.60 to ^0.5.1 in packages/persona-kit/package.json along with its lockfile entries. The reviewer recommends also updating this dependency in packages/runtime/package.json to avoid version mismatches, duplicate package installations, and potential runtime issues within the monorepo.

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.

[gemini-code-assist]

While updating @relayfile/adapter-core to ^0.5.1 resolves the trigger linting issue in persona-kit, leaving packages/runtime on ^0.3.60 introduces a dependency version mismatch within the monorepo. Since @agentworkforce/runtime depends on @agentworkforce/persona-kit (via workspace:*), having mismatched versions of a core library like @relayfile/adapter-core can lead to duplicate package installations in node_modules and potential runtime issues (such as instanceof check failures or multiple registry instances) if any objects or types are shared between the two packages. To maintain consistency and avoid duplicate dependency resolution, it is highly recommended to also bump @relayfile/adapter-core to ^0.5.1 in packages/runtime/package.json.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[khaliqgant]

Addressed the gemini-code-assist feedback in c63b78e: bumped packages/runtime's @relayfile/adapter-core pin from ^0.3.60 to ^0.5.1 too, so it matches persona-kit instead of resolving a second, older major/minor line in the workspace. Verified safe — runtime only touches the ./vfs-client subpath (untouched by the trigger-catalog change), typecheck is clean, and all 139 runtime tests still pass against the bumped dependency.