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/diataxis/en/explanation/development-progress-dashboard.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,7 @@ The next real improvement beyond that baseline is now also in code:
72
72
-`src/learning/KnowledgeLearningPlatform.ts` no longer treats `assistantBlocks` as a thin transport wrapper around the same old answer string,
73
73
- the scoped conversation reply is now organized into explicit overview / explanation / evidence summary / memory notice / action guidance sections before citations and knowledge-action affordances are appended,
74
74
- those sections now also consume real scoped data instead of only templated filler: explanation is anchored to the strongest scoped point, evidence summary reflects actual citations, and action guidance now carries memory follow-through hints,
75
+
- the reply policy is now also intent-aware, so comparison-style and how-to-style prompts can shape the explanation and next-action sections differently,
75
76
- which means the Tauri agent surface can now look materially different even when the underlying knowledge result set is unchanged.
Copy file name to clipboardExpand all lines: docs/en/implementation_plan.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,7 @@ Align the active implementation plan with current code reality:
70
70
- artifact-style handling for large HTML assistant outputs through sandboxed preview.
71
71
- structured reply composition now splits the assistant output into overview / explanation / evidence summary / memory notice / action guidance blocks instead of emitting only one wrapped markdown answer.
72
72
- those sections are now also semantically richer: the explanation is anchored to the strongest scoped knowledge point, the evidence summary reflects real scoped citations, and next-action guidance incorporates both scoped nodes and memory-action follow-through.
73
+
- reply composition is now intent-aware as well: comparison-style and how-to-style prompts no longer reuse the exact same explanation/action phrasing as plain explanatory prompts.
Copy file name to clipboardExpand all lines: docs/en/task.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@
11
11
-[x] The Tauri-first plan to evolve toward shared Reader-aligned rich reply rendering is now implemented as the current baseline while preserving knowledge-point/capability compatibility.
12
12
-[x] The backend reply composer now uses `assistantBlocks` as a real organization layer in Tauri: overview, explanation, evidence summary, memory notice, and next-action guidance are emitted as distinct blocks instead of only wrapping the old answer text.
13
13
-[x] The new Tauri reply sections are no longer template-only: explanation, evidence, and next-action guidance now derive from actual knowledge points, citations, and memory-action hints.
14
+
-[x] The reply policy is now intent-aware for Tauri agent output: comparison-style and how-to-style prompts can yield different explanation/action phrasing instead of one generic section style.
14
15
-[x] FR-010 is now governed by the current workflow reality instead of the removed transition-era assumption: repo-owned workflows pin `actions/setup-node@v4` to Node 24 and no longer rely on `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24`.
15
16
-[~] Remote CI closure remains a live release bar rather than a static claim: `Fixrisk Operational Readiness` must stay green on `main`, while residual Node 20 deprecation annotations from marketplace actions remain documented as non-blocking external debt.
markdownBlocks.some((block)=>String((blockas{markdown?: string}).markdown||'').includes('starting anchor for the next concrete steps'))
1568
+
).toBe(true);
1569
+
expect(
1570
+
markdownBlocks.some((block)=>String((blockas{markdown?: string}).markdown||'').includes('move from explanation into concrete guided-learning or focus-mode steps'))
1571
+
).toBe(true);
1572
+
});
1573
+
1499
1574
test('agent conversation exposes readiness and miss diagnostics when scoped retrieval is empty',async()=>{
Copy file name to clipboardExpand all lines: src/learning/KnowledgeLearningPlatform.ts
+62-3Lines changed: 62 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7624,6 +7624,45 @@ export class KnowledgeLearningPlatform implements KnowledgeLearningPlatformAPI {
7624
7624
return`${memoryPrefix}The strongest scoped match is ${leadingPoint.title}. I found ${params.knowledgePoints.length} relevant knowledge point(s) and ${params.citations.length} citation(s).\n\nKey evidence:\n${evidenceLines.join('\n')}`;
0 commit comments