hermes - 💡(How to fix) Fix Treat memory quota exceeded as a non-retryable tool-loop failure [1 pull requests]

Problem: Gateway logs show repeated memory tool failures when a memory write would exceed the configured quota, for example Replacement would put memory at 1,431/1,375 chars and Memory at 1,371/1,375 chars... would exceed the limit. The same turn then produced a repeated exact failure warning.

Quota exceeded is deterministic until content is shortened or existing memory is removed, so retrying the same memory write in the same turn cannot succeed. The agent should treat this as a non-retryable failure and move to recovery guidance instead of looping.

Expected behavior:

• Memory quota exceeded results should be classified as non-retryable.
• The tool/agent loop should suppress identical same-turn retry attempts after the first quota failure.
• The agent should receive actionable guidance: shorten the new content, replace an existing entry, or skip memory write.
• Logs should retain the attempted size/current limit without causing repeated noisy warnings.

Acceptance:

• Unit coverage for add and replace operations that exceed memory quota.
• A second identical same-turn memory call is blocked or summarized rather than executed again.
• The user-facing response explains the required recovery action.
• Successful memory writes and legitimate revised retry attempts still work.