Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

Classify the error-log triage state file in the JSON write-back guard

[._.]/ Adam Eivy945cc058c60b
diff --git a/server/test/jsonWritebackExceptions.js b/server/test/jsonWritebackExceptions.js
index b0a229761e..54b6be152a 100644
--- a/server/test/jsonWritebackExceptions.js
+++ b/server/test/jsonWritebackExceptions.js
@@ -49,6 +49,10 @@ export const JSON_WRITEBACK_EXCEPTIONS = [
"key": "cosReports.js :: reportFile",
"reason": "No write-back cycle: reports are generated from agent records and written whole; getReport only projects a stored report."
},
+ {
+ "key": "errorLogTriage.js :: stateFile",
+ "reason": "No failed-read write-back: readState reads strictly (strict:true), so a corrupt store throws instead of resetting the cursors; only an absent file seeds the empty state."
+ },
{
"key": "imageTo3d/sourceKeying.js :: preparedCacheMetadataPath ( targetPath )",
"reason": "Cache-only: source bytes and the explicit keying/framing request rebuild the prepared image metadata."