sonar-dock

What the scan recorded

Observed events

every prompt, every tool call

Hooks

session.start, command.run {command=sonar}, session.measure, prompt.submit, tool.call, turn.complete, turn.step, ui.render {component=AbovePrompt}, ui.render {component=UserMessage, surface=terminal, props.origin has {kind=composer}, ui.render {component=AssistantMessage, surface=terminal}, ui.render {component=ToolUse, surface=terminal}, ui.render {component=ToolResult, surface=terminal}, ui.render {component=ToolGroup, surface=terminal}, ui.render {component=Spinner}, ui.render {component=TurnDuration}, ui.render {component=CommandOutput, surface=terminal, props has {command=sonar}, ui.render {component=ToolProgress, surface=terminal}, ui.render {component=InfoNotice, surface=terminal}, ui.render {component=SessionMode, surface=terminal}, ui.render {component=PromptHint, surface=terminal}, ui.render {component=Pane, requestId=?}

API calls

$.clock.after, $.clock.every, $.command.register, $.config.list, $.process.run, $.session.usage, $.state.get, $.state.set, $.store.get, $.store.set, $.ui.blit, $.ui.close, $.ui.invalidate, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed with warnings

Scanned revision

f6eb872ec18f

Marketplace warnings

sonar-dock

UI rewrite review

UI hook source contains control-character strings. Review any values passed to next() as rewritten props.text; the scanner does not trace whether these strings reach that call. hooks/diagram/flowchart.ts:193

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.