sliccy 6.106.0 → 6.107.1

package/README.md

@@ -11,7 +11,7 @@ If this scares, confuses, or excites you, keep reading.
 
 # slicc — Self-Licking Ice Cream Cone
 
-[![48% Vibe_Coded](https://img.shields.io/badge/48%25-Vibe_Coded-ff69b4?style=for-the-badge&logo=claude&logoColor=white)](https://github.com/ai-ecoverse/vibe-coded-badge-action)
+[![49% Vibe_Coded](https://img.shields.io/badge/49%25-Vibe_Coded-ff69b4?style=for-the-badge&logo=claude&logoColor=white)](https://github.com/ai-ecoverse/vibe-coded-badge-action)
 
 [![npm](https://img.shields.io/npm/v/sliccy)](https://www.npmjs.com/package/sliccy)
 

package/dist/node-server/file-logger.d.ts

@@ -17,6 +17,22 @@ export interface FileLoggerOptions {
     /** Run 7-day cleanup on init. Defaults to true. */
     cleanup?: boolean;
 }
+/**
+ * JSON-serializable value nested under a structured log field.
+ * Matches what {@link safeStringify} persists (no functions / symbols).
+ */
+export type StructuredLogValue = string | number | boolean | null | StructuredLogValue[] | {
+    [key: string]: StructuredLogValue;
+};
+/**
+ * Optional structured fields attached to a log line. Keys are caller-chosen
+ * labels; values are JSON-stringified via {@link safeStringify}.
+ * `undefined` values are allowed so optional fields (e.g. `stack?`) type-check;
+ * `JSON.stringify` omits them.
+ */
+export type StructuredLogData = {
+    [key: string]: StructuredLogValue | undefined;
+};
 export declare class FileLogger {
     readonly logDir: string;
     readonly logFile: string;
@@ -26,7 +42,7 @@ export declare class FileLogger {
     private origConsole;
     constructor(options?: FileLoggerOptions);
     /** Write a structured log entry. Respects log level filtering. */
-    log(level: LogLevel, message: string, data?: Record<string, unknown>): void;
+    log(level: LogLevel, message: string, data?: StructuredLogData): void;
     /** Flush and close the log file. Safe to call multiple times. */
     close(): void;
     private installConsoleTee;