Extended session covering direct yttcom.net server access via WinSCP, a Pinegrow local-editing workflow, and a full Claude Code CLI installation wired into Pinegrow as its AI assistant -- which surfaced a genuine BETA bug in Pinegrows own integration, isolation-tested and confirmed not to be a config or install problem on our end.

WinSCP connected to yttcom.net (FTP+TLS, port 21098). Pinegrow installed, firewall/port issues resolved, pointed at a local site mirror folder. Node.js LTS and Claude Code CLI installed and logged in. Claude Code wired into Pinegrow as AI provider -- required also switching the Quick model dropdown away from the default openrouter:auto to actually route to Claude Code. Discovered the in-app chat integration is broken (BETA bug) via consistent garbled output across multiple different requests. Isolation-tested standalone claude CLI outside Pinegrow to confirm the tool itself works and the bug is Pinegrow-side. Logged QA-W032 (full setup + bug findings, later updated with confirmed-broken status and working fallback) and K368 (isolation-testing diagnostic pattern) to Laboratory/memory pipeline. Handoff rewritten.