SynapseAudit does not monitor files passively.
There is no continuous scanning, background indexing, or automatic execution tied to editor events.
Analysis begins only when the developer initiates it through one of the supported VS Code interactions, such as:
Executing a SynapseAudit command
Using a context menu action
Interacting with the extension’s UI controls
Each trigger corresponds to a single, intentional analysis cycle.
This design ensures that:
Developers always know when analysis is happening
Results are always tied to a specific action
There is no ambiguity about why findings appeared
Once triggered, SynapseAudit performs its analysis synchronously with the developer’s request and then returns control to the editor.