KnotLink integration and target resolution API

Declare KnotLink commands, arguments, signals and target resolution, routing remote requests through the same Host operations.

API 3.9 uses IKnotLinkIntegrationCapability with Commands, Signals and ExecuteAsync. Wire protocol v2, Server v3, Plugin API 3.9, funcList manifestVersion3.0.0 and specVersion1.0 are separate version axes.

Custom commands

KnotLinkCommandDescriptor includes Command, FunctionName, Arguments, Returns and RequiredArguments. Argument descriptors include input/default/options; signal descriptors expose fields. Metadata must match execution so the Host can generate capabilities.

GameRewind EXAMPLE_ECHO returns data in PluginCommandResult; the Host encodes the v2 response. Do not duplicate raw parsing or accept legacy space-separated commands.

Semantic selectors

IKnotLinkTargetResolver extends the integration capability and resolves stable ConfigId/FolderId or diagnostics. Do not register it separately. The Host executes the same core command and validation after resolution, without a second operation implementation.

MineRewind matches current_save=true for seven variants: BACKUP, LIST_BACKUPS, RESTORE, AUTO_BACKUP, STOP_AUTO_BACKUP, MARK_IMPORTANT and GET_IMPORTANCE. Discovery names are unique, wire cmd stays unchanged, and operation arguments come from KnotLinkCoreCommands.

Services and verification

Declare KnotLink for events and BackupRequest/RestoreRequest independently for operations. Preserve explicit player-preservation false; unsupported new restore options must return Blocked rather than falling back silently.

Query GET_CAPABILITIES first. status=ok may mean a long task was accepted; completion requires correlated signals. Runtime capabilities are authoritative for available commands, arguments and signals.