Renoise annotation board

Use the annotation board as an optional visual-intent surface, not as a node graph, timeline, creation workspace, or automatic step in generation.

Decide whether to open

• Do not call render_renoise_whiteboard_widget merely because visual annotation could help.
• If the request is clear without region/frame annotation, proceed directly through Renoise.
• If visual ambiguity is material, offer the annotation board in normal text and wait for the user to accept.
• An explicit request such as "打开标注板" or "我想圈出要改的位置" is acceptance.
• Within one task, reuse the existing canvasSessionId. If the user explicitly asks to bring the board back into view, call render_renoise_whiteboard_widget with that canvasSessionId; this remounts the UI for the same session and requests fullscreen. Never tell the user to click an earlier tool result, and never use a read/prepare tool as a UI launcher.

Open a board

1. Resolve the project directory already in scope. Do not guess a broader directory.
2. Call render_renoise_whiteboard_widget with that absolute projectDir to create a new session. For an existing active session, pass only canvasSessionId to reopen it.
3. A new session shows a compact launcher and opens only after the user clicks it and approves the exact path. Reopening an already authorized session requests fullscreen immediately and requires no second approval.
4. Keep the returned canvasSessionId; every later operation requires that active authorization. Board data and submitted annotation requests persist in the approved project and may be read through a later authorized session for the same page.