[BUG] "not from a Roo-registered terminal" spam in logs

[ArtemGr]

Problem (one or two sentences)

Roo reports a failure every time I build something:

error @ log.ts:460
console.ts:139 [Extension Host] [onDidStartTerminalShellExecution] Shell execution started, but not from a Roo-registered terminal: Object
Hio @ console.ts:139

(a) should be a warning, not an error; (b) should only report that once if at all, in order not to interfere with VSCode extension development

Context (who is affected and when)

anyone visiting VSCode Developer Tools

Reproduction steps

Run a terminal-using command

Expected result

logs quiet

Actual result

spam in logs

Variations tried (optional)

No response

App Version

v3.52.1

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

error @ log.ts:460
console.ts:139 [Extension Host] [onDidStartTerminalShellExecution] Shell execution started, but not from a Roo-registered terminal: Object
Hio @ console.ts:139

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

The log spam comes from src/integrations/terminal/TerminalRegistry.ts where two console.error calls fire every time a shell execution starts/ends in a terminal that Roo did not create (lines 64 and 89). Since non-Roo terminals are completely normal (user terminals, other extensions, etc.), this is expected behavior and should not be logged as an error.

Proposed changes in src/integrations/terminal/TerminalRegistry.ts:

1. Downgrade the two "not from a Roo-registered terminal" console.error calls (lines 64 and 89) to console.warn
2. Add a deduplication mechanism (a Set tracking terminal IDs that have already been warned about) so each unregistered terminal only produces the warning once, preventing log spam
3. Update or add tests to cover the new behavior

This approach addresses both concerns from the issue: (a) severity downgraded from error to warning, and (b) message only logged once per unregistered terminal to avoid spam.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[ArtemGr]

so each unregistered terminal only produces the warning once

new tasks usually spawn new terminals if user does not keep a terminal open, hence this solution will not reduce the number of inappropriate (roo is not the only terminal user out there) roo logging?
@roomote