Preserve repeated block deltas in streaming cards

Applying dedupeWithLastPartial: true to block updates drops any consecutive block chunks that have identical text, but this path is explicitly using mode: "delta". In block-streaming mode, identical adjacent deltas are valid output (for example, repeated short chunks), so the second chunk is now discarded and the final card content is truncated whenever runtimes emit duplicate block deltas without an intervening different partial.

Useful? React with 👍 / 👎.

Keep duplicate-id warnings for distinct config overrides

This condition suppresses duplicate plugin-id warnings purely on origin (bundled + config) and does not require both candidates to resolve to the same directory. That means a config-loaded plugin with the same id as a bundled plugin but from a different path is now silently accepted, hiding real id collisions/shadowing in plugins.load.paths where operators previously got a warning.

Useful? React with 👍 / 👎.

The isBundledAndConfig branch pushes a new record to records[] and updates seenIds to point to the current candidate. If a third candidate with the same manifest.id arrives with alternating origin (e.g., another bundled after seenIds was updated to config), the condition evaluates to true again and pushes another record. This can repeat unboundedly with each alternating candidate.

This diverges from the samePlugin path (line 221), which replaces the lower-precedence record in-place, maintaining exactly one record per manifest.id. Given the PLUGIN_ORIGIN_RANK precedence (config=0 vs bundled=3), consider replacing in-place:

This ensures only one record per plugin ID, consistent with the samePlugin pattern.

This is a comment left during a code review.
Path: src/plugins/manifest-registry.ts
Line: 238-251

Comment:
The `isBundledAndConfig` branch pushes a new record to `records[]` and updates `seenIds` to point to the current candidate. If a third candidate with the same `manifest.id` arrives with alternating origin (e.g., another `bundled` after `seenIds` was updated to `config`), the condition evaluates to true again and pushes another record. This can repeat unboundedly with each alternating candidate.

This diverges from the `samePlugin` path (line 221), which replaces the lower-precedence record in-place, maintaining exactly one record per `manifest.id`. Given the `PLUGIN_ORIGIN_RANK` precedence (config=0 vs bundled=3), consider replacing in-place:

```suggestion
if (isBundledAndConfig) {
  // Prefer config over bundled per PLUGIN_ORIGIN_RANK precedence.
  if (PLUGIN_ORIGIN_RANK[candidate.origin] < PLUGIN_ORIGIN_RANK[existing.candidate.origin]) {
    records[existing.recordIndex] = buildRecord({
      manifest,
      candidate,
      manifestPath: manifestRes.manifestPath,
      schemaCacheKey,
      configSchema,
    });
    seenIds.set(manifest.id, { candidate, recordIndex: existing.recordIndex });
  }
  continue;
}
```

This ensures only one record per plugin ID, consistent with the `samePlugin` pattern.

How can I resolve this? If you propose a fix, please make it concise.

Stop deduping block deltas by substring match

This guard drops any block chunk whose text already appears anywhere in streamText, but this branch feeds queueStreamingUpdate(..., { mode: "delta" }), where repeated chunks are valid output. In streams that emit duplicate/recurring delta tokens (for example repeated short words or characters), later chunks are skipped and the fallback block-only path can close with truncated card content.

Useful? React with 👍 / 👎.

Retain bundled duplicates so loader can mark overrides

Silently continuing on bundled+config ID collisions removes the bundled entry from manifestRegistry.plugins; downstream, loadOpenClawPlugins only processes candidates whose rootDir exists in that registry map (src/plugins/loader.ts:592-604), so the bundled plugin is skipped entirely instead of being surfaced as an overridden/disabled duplicate. This regresses duplicate-precedence visibility for users inspecting plugin status and diagnostics.

Useful? React with 👍 / 👎.

Preserve repeated block deltas in streaming updates

Passing dedupeWithLastPartial: true on the mode: "delta" block path causes legitimate repeated chunks to be dropped, because queueStreamingUpdate updates lastPartial on every deduped call and then suppresses the next identical chunk. In streams that emit identical adjacent deltas (for example repeated short tokens) without an intervening onPartialReply snapshot, the second chunk is discarded and the final card content is truncated.

Useful? React with 👍 / 👎.