Post-plan: extend Pine evidence to Editor status

Author: TayDa64

docs/CHAT_CONTINUITY_IMPLEMENTATION_PLAN.md

@@ -1499,9 +1499,10 @@ node scripts/test-windows-observation-flow.js
 - extended `src/main/tradingview/pine-workflows.js` so Pine Logs evidence-gathering requests can stay verification-first while preserving or auto-appending bounded `get_text` readback
 - extended `src/main/tradingview/pine-workflows.js` so Pine Profiler evidence-gathering requests can also stay verification-first while preserving or auto-appending bounded `get_text` readback
 - extended `src/main/tradingview/pine-workflows.js` so Pine Version History provenance requests can stay verification-first while preserving or auto-appending bounded `get_text` readback
+- extended `src/main/tradingview/pine-workflows.js` so Pine Editor visible status/output requests can stay verification-first while preserving or auto-appending bounded `get_text` readback
 - added dedicated Pine data-workflow regressions in `scripts/test-tradingview-pine-data-workflows.js`
-- extended `scripts/test-windows-observation-flow.js` with verified Pine Logs, Pine Profiler, and Pine Version History readback coverage that gathers text without re-entering a screenshot loop
-- updated `src/main/ai-service/system-prompt.js` so TradingView Pine output/error/provenance requests prefer verified Pine surfaces plus `get_text` over screenshot-only inference
+- extended `scripts/test-windows-observation-flow.js` with verified Pine Logs, Pine Profiler, Pine Version History, and Pine Editor status/output readback coverage that gathers text without re-entering a screenshot loop
+- updated `src/main/ai-service/system-prompt.js` so TradingView Pine output/error/provenance requests prefer verified Pine surfaces plus `get_text`, including Pine Editor visible status/output, over screenshot-only inference
 
 **Why this track exists**
 - Current Pine support is surface-oriented:
@@ -1562,7 +1563,7 @@ node scripts/test-windows-observation-flow.js
 - Pine workflows strengthen analysis honesty instead of bypassing it
 
 **Next best slice from here**
-- extend the same bounded evidence-gathering pattern beyond Pine Version History into broader visible Pine status/output surfaces without implying chart-state insight
+- refine Pine Editor status/output readback into more structured visible compile-result / diagnostics summaries without implying chart-state insight
 
 ### Track E — Honest drawing capability framing
 

scripts/test-bug-fixes.js

@@ -333,6 +333,7 @@ test('ai-service gates TradingView follow-up typing on post-key observation chec
   assert(tradingViewPineContent.includes("type: 'get_text'"), 'TradingView Pine workflows should support bounded Pine Logs readback');
   assert(tradingViewPineContent.includes("text: 'Pine Profiler'"), 'TradingView Pine workflows should support bounded Pine Profiler readback');
   assert(tradingViewPineContent.includes("text: 'Pine Version History'"), 'TradingView Pine workflows should support bounded Pine Version History readback');
+  assert(tradingViewPineContent.includes("text: 'Pine Editor'"), 'TradingView Pine workflows should support bounded Pine Editor status/output readback');
   assert(tradingViewPineContent.includes('wantsEvidenceReadback'), 'TradingView Pine workflows should detect Pine evidence-gathering requests');
   assert(tradingViewPaperContent.includes("target: 'paper-trading-panel'"), 'TradingView Paper workflows should encode paper-trading-panel verification metadata');
   assert(tradingViewPaperContent.includes('paper account'), 'TradingView Paper workflows should ground paper-assist keywords');
@@ -348,6 +349,7 @@ test('system prompt guides Pine evidence gathering toward get_text over screensh
 
   assert(content.includes('TradingView Pine evidence rule'), 'System prompt should include explicit TradingView Pine evidence guidance');
   assert(content.includes('Pine Logs / Profiler / Version History text'), 'System prompt should point the model toward Pine text and provenance evidence');
+  assert(content.includes('Pine Editor visible status/output'), 'System prompt should mention Pine Editor status/output as bounded evidence');
   assert(content.includes('get_text'), 'System prompt should mention get_text for Pine evidence gathering');
 });
 

scripts/test-tradingview-pine-data-workflows.js

@@ -30,6 +30,16 @@ test('pine workflow recognizes pine logs evidence-gathering requests', () => {
   assert.strictEqual(intent.wantsEvidenceReadback, true);
 });
 
+test('pine workflow recognizes pine editor status-output requests', () => {
+  const intent = inferTradingViewPineIntent('open pine editor in tradingview and read the visible compiler status', [
+    { type: 'key', key: 'ctrl+e' }
+  ]);
+
+  assert(intent, 'intent should be inferred');
+  assert.strictEqual(intent.surfaceTarget, 'pine-editor');
+  assert.strictEqual(intent.wantsEvidenceReadback, true);
+});
+
 test('pine workflow recognizes pine profiler evidence-gathering requests', () => {
   const intent = inferTradingViewPineIntent('open pine profiler in tradingview and summarize the metrics', [
     { type: 'key', key: 'ctrl+shift+p' }
@@ -69,6 +79,25 @@ test('open pine logs and read output stays verification-first', () => {
   assert.strictEqual(rewritten[4].text, 'Pine Logs');
 });
 
+test('open pine editor and read visible status stays verification-first', () => {
+  const rewritten = buildTradingViewPineWorkflowActions({
+    appName: 'TradingView',
+    surfaceTarget: 'pine-editor',
+    verifyKind: 'panel-visible',
+    openerIndex: 0,
+    wantsEvidenceReadback: true,
+    requiresObservedChange: false
+  }, [
+    { type: 'key', key: 'ctrl+e', reason: 'Open Pine Editor' }
+  ]);
+
+  assert.strictEqual(rewritten[0].type, 'bring_window_to_front');
+  assert.strictEqual(rewritten[2].type, 'key');
+  assert.strictEqual(rewritten[2].verify.target, 'pine-editor');
+  assert.strictEqual(rewritten[4].type, 'get_text');
+  assert.strictEqual(rewritten[4].text, 'Pine Editor');
+});
+
 test('open pine profiler and summarize metrics stays verification-first', () => {
   const rewritten = buildTradingViewPineWorkflowActions({
     appName: 'TradingView',
@@ -122,6 +151,21 @@ test('pine evidence-gathering workflow preserves trailing get_text read step', (
   assert.strictEqual(rewritten[2].verify.target, 'pine-logs');
 });
 
+test('pine editor evidence workflow preserves trailing get_text read step', () => {
+  const rewritten = maybeRewriteTradingViewPineWorkflow([
+    { type: 'key', key: 'ctrl+e' },
+    { type: 'get_text', text: 'Pine Editor', reason: 'Read visible Pine Editor status text' }
+  ], {
+    userMessage: 'open pine editor in tradingview and summarize the visible compiler status'
+  });
+
+  assert(Array.isArray(rewritten), 'workflow should rewrite');
+  const readSteps = rewritten.filter((action) => action?.type === 'get_text');
+  assert.strictEqual(readSteps.length, 1, 'explicit pine editor readback step should be preserved without duplication');
+  assert.strictEqual(readSteps[0].text, 'Pine Editor');
+  assert.strictEqual(rewritten[2].verify.target, 'pine-editor');
+});
+
 test('pine profiler evidence workflow preserves trailing get_text read step', () => {
   const rewritten = maybeRewriteTradingViewPineWorkflow([
     { type: 'key', key: 'ctrl+shift+p' },

scripts/test-windows-observation-flow.js

@@ -265,6 +265,21 @@ async function run() {
     assert.strictEqual(rewritten[4].text, 'plot(close)');
   });
 
+  await testAsync('low-signal TradingView Pine Editor status request rewrites to panel verification plus get_text', async () => {
+    const rewritten = aiService.rewriteActionsForReliability([
+      { type: 'key', key: 'ctrl+e' }
+    ], {
+      userMessage: 'open pine editor in tradingview and read the visible compiler status'
+    });
+
+    assert(Array.isArray(rewritten), 'pine editor status rewrite should return an action array');
+    assert.strictEqual(rewritten[0].type, 'bring_window_to_front');
+    assert.strictEqual(rewritten[2].type, 'key');
+    assert.strictEqual(rewritten[2].verify.target, 'pine-editor');
+    assert.strictEqual(rewritten[4].type, 'get_text');
+    assert.strictEqual(rewritten[4].text, 'Pine Editor');
+  });
+
   await testAsync('low-signal TradingView Pine Logs evidence request rewrites to panel verification plus get_text', async () => {
     const rewritten = aiService.rewriteActionsForReliability([
       { type: 'key', key: 'ctrl+shift+l' }
@@ -466,6 +481,58 @@ async function run() {
     });
   });
 
+  await testAsync('verified pine editor workflow allows bounded visible status gathering without screenshot loop', async () => {
+    const executed = [];
+    const foregroundSequence = [
+      { success: true, hwnd: 777, title: 'TradingView', processName: 'tradingview', windowKind: 'main' },
+      { success: true, hwnd: 892, title: 'Pine Editor - TradingView', processName: 'tradingview', windowKind: 'owned' },
+      { success: true, hwnd: 892, title: 'Pine Editor - TradingView', processName: 'tradingview', windowKind: 'owned' },
+      { success: true, hwnd: 892, title: 'Pine Editor - TradingView', processName: 'tradingview', windowKind: 'owned' }
+    ];
+
+    await withPatchedSystemAutomation({
+      resolveWindowHandle: async (action) => action?.processName === 'tradingview' ? 777 : 0,
+      getForegroundWindowHandle: async () => 777,
+      getForegroundWindowInfo: async () => {
+        return foregroundSequence.shift() || { success: true, hwnd: 892, title: 'Pine Editor - TradingView', processName: 'tradingview', windowKind: 'owned' };
+      },
+      focusWindow: async () => ({ success: true }),
+      getRunningProcessesByNames: async () => ([{ pid: 4242, processName: 'tradingview', mainWindowTitle: 'TradingView', startTime: '2026-03-23T00:00:00Z' }])
+    }, async () => {
+      const execResult = await aiService.executeActions({
+        thought: 'Open Pine Editor and summarize the visible compiler status',
+        verification: 'TradingView should show Pine Editor before text is read',
+        actions: [
+          { type: 'focus_window', title: 'TradingView', processName: 'tradingview' },
+          { type: 'key', key: 'ctrl+e', reason: 'Open Pine Editor', verify: { kind: 'panel-visible', appName: 'TradingView', target: 'pine-editor', keywords: ['pine editor', 'pine'] } },
+          { type: 'get_text', text: 'Pine Editor', reason: 'Read visible Pine Editor status/output text' }
+        ]
+      }, null, null, {
+        userMessage: 'open pine editor in tradingview and summarize the visible compiler status',
+        actionExecutor: async (action) => {
+          executed.push(action.type);
+          if (action.type === 'get_text') {
+            return {
+              success: true,
+              action: action.type,
+              text: 'Compiler: no errors. Status: strategy loaded.',
+              method: 'TextPattern',
+              message: 'Got text via TextPattern: "Compiler: no errors. Status: strategy loaded."'
+            };
+          }
+          return { success: true, action: action.type, message: 'executed' };
+        }
+      });
+
+      assert.strictEqual(execResult.success, true, 'Execution should proceed after Pine Editor is observed');
+      assert.deepStrictEqual(executed, ['focus_window', 'key', 'get_text'], 'Bounded Pine Editor status gathering should continue to read text after panel verification');
+      assert.strictEqual(execResult.observationCheckpoints.length, 1, 'A post-key observation checkpoint should be returned');
+      assert.strictEqual(execResult.observationCheckpoints[0].verified, true, 'Pine Editor panel observation should pass');
+      assert.strictEqual(execResult.results[2].text, 'Compiler: no errors. Status: strategy loaded.', 'Pine Editor status text should be preserved on the get_text result');
+      assert(!execResult.screenshotCaptured, 'Pine Editor status gathering should not require a screenshot loop');
+    });
+  });
+
   await testAsync('low-signal TradingView DOM request wraps the opener with bounded panel verification', async () => {
     const rewritten = aiService.rewriteActionsForReliability([
       { type: 'key', key: 'ctrl+d' },

src/main/ai-service/system-prompt.js

@@ -125,7 +125,7 @@ Format: \`- [Index] Type: "Name" at (x, y)\`
 ### Visual Honesty Rule (CRITICAL)
 - If you do NOT have a screenshot AND the user did NOT provide a Live UI State list, you MUST NOT claim you can see any windows, panels, or elements.
 - In that situation, either use keyboard-only deterministic steps or ask the user to run \`/capture\`.
-- For TradingView requests that ask for concrete output, profiler-style evidence, or script provenance, prefer verified Pine surfaces plus \`get_text\` (for example Pine Logs / Profiler / Version History text) over screenshot-only indicator guesses.
+- For TradingView requests that ask for concrete output, profiler-style evidence, visible Pine Editor status/output, or script provenance, prefer verified Pine surfaces plus \`get_text\` (for example Pine Logs / Profiler / Version History text or Pine Editor visible status/output) over screenshot-only indicator guesses.
 
 **TO LIST ELEMENTS**: Read the Live UI State section and list what's there.
 
@@ -223,7 +223,7 @@ When the user asks you to DO something, respond with a JSON action block:
   3) perform deterministic selection action,
   4) request screenshot only if all non-visual attempts fail.
 - **Continuity rule**: if the active page title or recent action output indicates the requested browser objective is already achieved, acknowledge completion and avoid proposing additional screenshot steps.
-- **TradingView Pine evidence rule**: if the user wants concrete Pine output, errors, profiler-style evidence, or visible revision/provenance details, prefer \`open/show Pine Logs, Profiler, or Version History\` + verified panel opening + \`get_text\` before relying on screenshot analysis.
+- **TradingView Pine evidence rule**: if the user wants concrete Pine output, errors, profiler-style evidence, visible Pine Editor status/output, or visible revision/provenance details, prefer \`open/show Pine Editor, Logs, Profiler, or Version History\` + verified panel opening + \`get_text\` before relying on screenshot analysis.
 - **If you need to interact with web content inside an app** (like VS Code panels, browser tabs): Use keyboard shortcuts or coordinate-based clicks since web UI may not appear in UIA tree
 
 **Common Task Patterns**:

src/main/tradingview/pine-workflows.js

@@ -35,6 +35,14 @@ function inferPineEvidenceReadIntent(raw = '', surfaceTarget = '') {
 }
 
 function buildPineReadbackStep(surfaceTarget) {
+  if (surfaceTarget === 'pine-editor') {
+    return {
+      type: 'get_text',
+      text: 'Pine Editor',
+      reason: 'Read visible Pine Editor status/output text for bounded evidence gathering'
+    };
+  }
+
   if (surfaceTarget === 'pine-logs') {
     return {
       type: 'get_text',
@@ -126,7 +134,9 @@ function inferTradingViewPineIntent(userMessage = '', actions = []) {
         ? 'Open TradingView Pine Profiler with verification'
         : surface.target === 'pine-version-history'
           ? 'Open TradingView Pine version history with verification'
-          : 'Open TradingView Pine Editor with verification'
+          : wantsEvidenceReadback
+            ? 'Open TradingView Pine Editor with verification and read visible status/output'
+            : 'Open TradingView Pine Editor with verification'
   };
 }