@rivus/agent
v0.21.2
Published
Rivus CLI, plugin SDK and plugin conformance testkit.
Maintainers
Readme
@rivus/agent
Rivus product entrypoint: the plugin SDK, conformance testkit and sole rivus CLI. The CLI delegates to Gateway;
Runtime owns execution. Gateway owns deployment templates and Skills, with no duplicate Agent assets.
The CLI provides rivus upgrade [--json] for an existing macOS LaunchAgent or Linux user systemd Home. It prepares
the latest stable complete four-package release before stopping the service, preserves the Home and Plugin versions,
then backs up, switches and verifies the new process. Interrupted operations resume the original target; a failure
after stop never restores an older data snapshot automatically. Rivus 0.20.0 has no upgrade command; bootstrap the
first invocation with the newly published CLI. See managed Home upgrades
for service prerequisites, first invocation and recovery.
The root exports four values: RIVUS_PLUGIN_API_VERSION, RivusToolInputRejected,
RivusAutomationFailure and readAutomationPresentation. Its 28 type exports are:
RivusPluginManifest,RivusPlugin,RivusPluginRegistry.RivusAgentProfile,RivusAgentDeployment.RivusToolDescriptor,RivusToolExecutor,RivusToolFactoryContext,RivusToolExecutionContext,RivusToolRisk,RivusToolIdempotency,RivusRuntimeToolId.RivusSkillDescriptor.RivusAutomationTemplate,RivusAutomationTickContext,RivusAutomationInput,RivusAutomationOutput,RivusAutomationRetryPolicy.AutomationPresentation,AutomationPresentationItem,AutomationPresentationKind,AutomationPresentationSection,AutomationPresentationSource,AutomationPresentationTable,AutomationPresentationTableCell,AutomationPresentationTableColumn,AutomationPresentationTrend,AutomationLineChart.
Presentation requires schemaVersion: 2. readAutomationPresentation validates and normalizes the same value used
by generation and persistence, including unknown-key rejection. RivusAutomationFailure provides a validated code;
only codes declared in a template's optional retry.terminalFailureCodes stop its occurrence immediately. See the
Automation behavior and
historical pre-0.20 migration.
@rivus/agent/testing exports assertRivusPluginConforms, createFakeRivusPlugin,
RivusPluginConformanceError, RivusPluginLifecycleProbe, RivusPluginConformanceInput and
RivusPluginConformanceReport. Conformance validates registration, references, grant narrowing and optional
lifecycle disposal; test tool executors directly for business behavior.
Only the root, /testing and /package.json are exported. Historical runtime helpers, event constructors,
Memory DTOs and /pi, /acp, /mcp, /bootstrap/pi-feishu, /plugin/starter and Skill aliases are removed
intentionally. Use @rivus/runtime/pi, @rivus/runtime/acp, @rivus/gateway/mcp and Gateway bootstrap/resources.
Configuration no longer rewrites old Agent bootstrap or starter specifiers. See the
SDK example and
deployment migration.
