Spell out the namespace on the Catalog option so it compiles

CI failed on a clean build that a local incremental build had been hiding: the
property is named Catalog, so inside ExtractionOptions the simple name binds to
the member rather than to the namespace of the same name, and Catalog.XafCatalog
does not resolve.

My local build had a stale obj/ and never recompiled the file, which is a good
argument for reproducing a CI failure with a clean tree rather than trusting a
green local run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: peopleworks

src/XafLogicExplainer.Core/Models/ExtractionOptions.cs

@@ -124,6 +124,11 @@ public class ExtractionOptions
     /// <summary>
     /// An explicit catalog, overriding the one that would be loaded from disk.
     /// </summary>
+    /// <remarks>
+    /// Written with the namespace spelled out. The property is called <c>Catalog</c>, so inside
+    /// this class the simple name binds to the member rather than to the namespace of the same
+    /// name, and <c>Catalog.XafCatalog</c> does not compile.
+    /// </remarks>
     [JsonIgnore]
-    public Catalog.XafCatalog? Catalog { get; set; }
+    public XafLogicExplainer.Core.Catalog.XafCatalog? Catalog { get; set; }
 }