Implement findings fixing and template matching features in Mindnet plugin
Node.js build / build (20.x) (push) Waiting to run
Node.js build / build (22.x) (push) Waiting to run

- Added a new command to fix findings in the current section of a markdown file, enhancing user experience by automating issue resolution.
- Introduced settings for configuring actions related to missing notes and headings, allowing for customizable behavior during the fixing process.
- Enhanced the chain inspector to support template matching, providing users with insights into template utilization and potential gaps in their content.
- Updated the analysis report to include detailed metadata about edges and role matches, improving the clarity and usefulness of inspection results.
- Improved error handling and user notifications for fixing findings and template matching processes, ensuring better feedback during execution.
This commit is contained in:
Lars committed 2026-01-18 21:10:33 +01:00
1 parent b0efa32c66
commit 90ccec5f7d
26 files changed
+4536 -32

No files matched your search

+16
View File
@@ -0,0 +1,16 @@
---
id: t_exp_001
title: trigger_experience
type: experience
status: draft
---
## Kontext
Das ist ein Trigger-/Erlebnisabschnitt mit genug Text, um “nontrivial content” zu sein.
Wir testen Template Matching in dieser Section.
> [!edge] ausgelöst_durch
> [[02_event_trigger_detail#Detail]]
> [!edge] wirkt_auf
> [[03_insight_transformation#Kern]]
+13
View File
@@ -0,0 +1,13 @@
---
id: t_evt_001
title: trigger_event_detail
type: event
status: draft
---
## Detail
Details zum Ereignis, optional.
## Note-Verbindungen
> [!edge] references
> [[01_experience_trigger#Kontext]]
+12
View File
@@ -0,0 +1,12 @@
---
id: t_ins_001
title: transformation_insight
type: insight
status: draft
---
## Kern
Hier steht die Transformation/Insight.
> [!edge] resulted_in
> [[04_decision_outcome#Entscheidung]]
+12
View File
@@ -0,0 +1,12 @@
---
id: t_dec_001
title: outcome_decision
type: decision
status: draft
---
## Entscheidung
Hier ist eine Entscheidung als Outcome.
> [!edge] depends_on
> [[05_value_driver#Wert]]
+9
View File
@@ -0,0 +1,9 @@
---
id: t_val_001
title: driver_value
type: value
status: draft
---
## Wert
Ein Wert als Treiber.
+13
View File
@@ -0,0 +1,13 @@
---
id: t_misc_001
title: candidates_only
type: experience
status: draft
---
## Kontext
Genug Text, damit nontrivial true wird. Aber keine expliziten edges hier.
## Kandidaten
> [!edge] resulted_in
> [[04_decision_outcome#Entscheidung]]