fix(persona-kit): bump @relayfile/adapter-core to pick up telegram trigger catalog
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-corefrom^0.3.60to^0.5.1inpackages/persona-kit/package.json, updatepnpm-lock.yaml. - Left
packages/runtime's identical^0.3.60pin 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 installresolves@relayfile/adapter-coreto0.5.1insidepackages/persona-kit/node_modules.npm testinpackages/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