You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CHAT_CONTINUITY_IMPLEMENTATION_PLAN.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1339,7 +1339,7 @@ The findings below are grounded in current repo seams, especially:
1339
1339
1340
1340
### Track A — Intent-safe reliability rewrites
1341
1341
1342
-
**Status:**First slice completed in working tree
1342
+
**Status:**Second slice completed in working tree
1343
1343
1344
1344
**Delivered so far**
1345
1345
- hardened `extractRequestedAppName(...)` in `src/main/ai-service.js` so passive open-state phrasing no longer gets treated as app-launch intent
@@ -1679,6 +1679,7 @@ This is the next Pine-facing implementation slice after the current Logs / Profi
1679
1679
**Delivered so far**
1680
1680
- extended `src/main/tradingview/pine-workflows.js` with a `provenance-summary` evidence mode for `pine-version-history`
1681
1681
- Version History metadata requests such as `summarize the top visible revision metadata` now preserve or auto-append bounded `get_text` provenance-summary readback
1682
+
-`get_text` provenance-summary results now attach deterministic visible revision metadata such as latest visible revision label, latest visible relative time, visible revision count, and visible recency signal
assert(pineWorkflowContent.includes('diagnostics and warnings text'),'Pine workflows should use diagnostics-specific readback wording');
252
252
assert(pineWorkflowContent.includes('provenance-summary'),'Pine workflows should support version-history provenance-summary evidence mode');
253
253
assert(pineWorkflowContent.includes('top visible Pine Version History revision metadata'),'Pine workflows should use provenance-summary-specific readback wording');
254
+
assert(pineWorkflowContent.includes('pineSummaryFields'),'Pine workflows should carry explicit structured summary fields for provenance summaries');
254
255
});
255
256
256
257
test('system prompt includes Pine diagnostics guidance',()=>{
@@ -262,6 +263,7 @@ test('system prompt includes Pine diagnostics guidance', () => {
262
263
assert(systemPromptContent.includes('TradingView Pine diagnostics rule'),'System prompt should include Pine diagnostics guidance');
263
264
assert(systemPromptContent.includes('visible revision/provenance details'),'System prompt should steer Pine provenance requests toward verified Version History text');
264
265
assert(systemPromptContent.includes('treat visible Pine Version History entries as bounded audit/provenance evidence only'),'Pine provenance guidance should prevent overclaiming from visible revision history');
assert(evidenceMessage.content.includes('Treat Pine Version History as bounded provenance evidence only'));
73
+
assert(evidenceMessage.content.includes('latest visible revision label, latest visible relative time, visible revision count, and visible recency signal'));
73
74
assert(evidenceMessage.content.includes('Do not infer hidden diffs, full script history, authorship, or runtime/chart behavior from the visible revision list alone.'));
assert(/topvisiblePineVersionHistoryrevisionmetadata/i.test(rewritten[4].reason),'version-history metadata readback should use provenance-summary wording');
266
273
});
267
274
@@ -338,6 +345,13 @@ test('pine version history metadata workflow preserves trailing get_text read st
338
345
assert.strictEqual(readSteps.length,1,'explicit version-history metadata readback step should be preserved without duplication');
339
346
assert.strictEqual(readSteps[0].text,'Pine Version History');
Copy file name to clipboardExpand all lines: scripts/test-windows-observation-flow.js
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -578,6 +578,14 @@ async function run() {
578
578
assert.deepStrictEqual(evidenceModes,['provenance-summary'],'Version History metadata workflow should preserve provenance-summary evidence mode');
579
579
assert.strictEqual(execResult.observationCheckpoints[0].verified,true,'Pine Version History panel observation should pass');
580
580
assert.strictEqual(execResult.results[2].text,'Revision 18 saved 2m ago; Revision 17 saved 18m ago; showing 2 visible revisions','Version History metadata text should be preserved on the get_text result');
581
+
assert.strictEqual(execResult.results[2].pineStructuredSummary.latestVisibleRevisionLabel,'Revision 18','Version History metadata summary should expose the latest visible revision label');
582
+
assert.strictEqual(execResult.results[2].pineStructuredSummary.latestVisibleRelativeTime,'2m ago','Version History metadata summary should expose the latest visible relative time');
583
+
assert.strictEqual(execResult.results[2].pineStructuredSummary.visibleRevisionCount,2,'Version History metadata summary should expose the visible revision count');
584
+
assert.strictEqual(execResult.results[2].pineStructuredSummary.visibleRecencySignal,'recent-churn-visible','Version History metadata summary should expose a bounded visible recency signal');
Copy file name to clipboardExpand all lines: src/main/ai-service/message-builder.js
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,7 @@ function buildPineEvidenceConstraint({ foreground, userMessage }) {
85
85
86
86
if(requestKind==='provenance-summary'){
87
87
lines.push('- Rule: Treat Pine Version History as bounded provenance evidence only; summarize only the top visible revision labels, relative times, and other metadata that are directly visible.');
88
+
lines.push('- Rule: When possible, structure the summary into compact visible fields such as latest visible revision label, latest visible relative time, visible revision count, and visible recency signal.');
88
89
lines.push('- Rule: Do not infer hidden diffs, full script history, authorship, or runtime/chart behavior from the visible revision list alone.');
Copy file name to clipboardExpand all lines: src/main/ai-service/system-prompt.js
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -229,7 +229,7 @@ When the user asks you to DO something, respond with a JSON action block:
229
229
- **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.
230
230
- **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.
231
231
- **TradingView Pine diagnostics rule**: treat visible Pine Editor compile results, compiler errors, warnings, and diagnostics as bounded text evidence. Do not turn \`no errors\` into claims about runtime correctness, market validity, or trading edge.
232
-
- **TradingView Pine provenance rule**: treat visible Pine Version History entries as bounded audit/provenance evidence only. Summarize top visible revision labels, relative times, and other directly visible metadata, but do not infer hidden diffs, full script history, authorship, or runtime/chart behavior from the visible list alone.
232
+
- **TradingView Pine provenance rule**: treat visible Pine Version History entries as bounded audit/provenance evidence only. Summarize top visible revision labels, latest visible revision label, latest visible relative time, visible revision count, visible recency signal, and other directly visible metadata, but do not infer hidden diffs, full script history, authorship, or runtime/chart behavior from the visible list alone.
233
233
- **TradingView Pine line-budget rule**: Pine scripts are limited to 500 lines. Do not propose pasting or generating Pine scripts longer than 500 lines; prefer bounded edits, read visible line/status hints first when needed, and mention the limit explicitly when it affects read/write guidance.
234
234
- **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
0 commit comments