V0.5 Durable Signals & Run History

Signals becomes persistent infrastructure, retaining monitoring configurations, run history and supporting evidence across sessions and over time.

Durable Signals – Signals now persist as ongoing monitoring objects rather than existing only inside the research session that created them.
Signal run history – Previous monitoring runs can be reviewed over time.
Persistent evidence – Supporting evidence remains associated with Signal activity, making changes between runs easier to understand.

Stronger workspace ownership – Improved how Signals and their evidence are kept within the correct workspace.
More reliable long-running monitoring – Signal configuration and execution can survive subsequent sessions and application restarts.
Safer connected research – Strengthened boundaries between personal connections, shared workspace connections and private information.
More reviewable execution – Improved the foundations for understanding what a Signal did and what information it used.

Prevented conversations containing private uploaded documents from being shared publicly.
Strengthened protections around shared workspace connections and credentials.
Hardened how Lucid follows links and retrieves external pages.
Fixed reliability issues affecting background entity analysis and Signal execution.