Summary

• Adds optional logging infrastructure to the document comparison engine
• Enables graceful handling of document issues (like orphaned footnotes) without failing comparisons
• Provides detailed log entries with codes, messages, and document locations for debugging
• Adds new WASM bindings and TypeScript types for log-enabled comparison methods

Background

Some documents have structural issues (e.g., footnote references pointing to non-existent footnote definitions) that previously caused the comparison to fail with "Invalid document" exceptions. This PR allows users to opt-in to logging mode where these issues are captured and reported while the comparison continues.

Changes

New files:

• Docxodus/ComparisonLog.cs - Core logging infrastructure classes

Modified files:

• Docxodus/WmlComparer.cs - Added Log property to settings, updated methods to log warnings instead of throwing
• wasm/DocxodusWasm/DocumentComparer.cs - Added CompareDocumentsWithLog and CompareDocumentsToHtmlWithLog methods
• wasm/DocxodusWasm/JsonContext.cs - Added DTOs for log entries and responses
• npm/src/types.ts - Added TypeScript types for log entries and responses
• npm/src/index.ts - Added wrapper functions for log-enabled comparison

API

C# (.NET):

var log = new ComparisonLog();
var settings = new WmlComparerSettings { Log = log };
var result = WmlComparer.Compare(doc1, doc2, settings);

foreach (var warning in log.Warnings)
    Console.WriteLine($"{warning.Code}: {warning.Message}");

TypeScript/JavaScript:

const result = await compareDocumentsWithLog(original, modified, {
  authorName: "Reviewer"
});

if (result.success && result.hasWarnings) {
  console.log("Warnings:", result.log);
}

Test plan

• All existing tests pass (1191 passed)
• WASM build succeeds
• TypeScript compiles without errors
• Manual test with malformed document (orphaned footnotes) - comparison succeeds with warnings logged