Enhance logging in FdsSqlOptions and related classes

- Updated FdsSqlOptions to accept an optional ILogger parameter for improved error logging.
- Modified FdsMfr and FdsMfrClient classes to pass the logger instance to FdsSqlOptions.
- Added detailed error logging in various methods to capture SQL execution issues and file handling errors.
- Improved documentation for FdsSqlOptions to clarify logging behavior.
- Updated Archive class to log compression errors, enhancing traceability of failures.
- Adjusted project configuration to suppress specific warnings related to transitive dependencies.
- Added NuGet.config to define package sources for dependency management.
- Updated submodule references for OCORE and related projects.

.github/copilot-instructions.md

@@ -1,16 +1,20 @@
 # Copilot Instructions
 
 > ## ⚠️ Instruction Sync
-> This file (`.github/copilot-instructions.md`) and the Claude Code instructions
-> (`/CLAUDE.md`) are **two views of the same project rules and must stay in sync**.
-> Whenever you change one, make the equivalent change in the other in the same
-> commit. `CLAUDE.md` may add tool-specific workflow notes, but the shared
+> This file (`.github/copilot-instructions.md`), the Claude Code instructions
+> (`/CLAUDE.md`), and the Codex instructions (`/CODEX.md`) are **three views of
+> the same project rules and must stay in sync**.
+> Whenever you change one, make the equivalent change in the other two in the same
+> commit. `CLAUDE.md` and `CODEX.md` may add tool-specific workflow notes, but the shared
 > project facts (architecture, coding standards, configuration, libraries,
 > secrets, observability) must match.
 
 ## Project Overview
 - **Fuchs Intranet** is an ASP.NET Core (.NET 10) web application — the intranet IS the entire website, served from `/`.
 - Routes: `/{fn?}/{id?}/{code?}` → `IntranetController.Index`; `/do/{fn?}/{id?}/{code?}` → `IntranetController.Do`.
+- Build app: `dotnet build Fuchs/Fuchs.csproj -c Debug`. Build all: `dotnet build Fuchs_Intranet.slnx -c Debug`.
+- Frontend assets are source-built: run the gulp tasks in `Fuchs/` (`npx gulp min`, or `npx gulp all` when copied/static assets also need refreshing) whenever JS or SCSS/CSS sources change. The generated files under `Fuchs/wwwroot/web/` are what the app serves.
+- Test: `dotnet test Fuchs.Tests/Fuchs.Tests.csproj -c Debug`.
 - Project structure (relative to `Fuchs/`):
   - `Controllers/` — `IntranetController` partials (no area)
   - `code/` — business logic, PDF, email, widgets, data models
@@ -74,6 +78,11 @@
   - Name tests `MethodName_Scenario_ExpectedResult`.
   - DB-bound paths that can't be unit-tested should at least have their pure logic covered.
 
+## Decisions & Concepts
+- `Fuchs/Docs/Decisions/` holds immutable ADRs (architecture decision records); `Fuchs/Docs/Concepts/` holds living design write-ups kept in sync with the code. Each folder's `README.md` explains the format, naming, and required YAML frontmatter — **read it before creating or editing entries there.**
+- **Accepted decisions must be followed.** Before working in an area covered by a decision, read it and conform to it; don't silently deviate. Every file's YAML frontmatter has an `applyTo` glob — scan frontmatter across the folder first (cheap) and only read the full body of entries relevant to the files you're touching.
+- **Capture new decisions and concepts as they happen.** When a non-obvious architectural or cross-cutting choice gets settled (by the user or in the course of implementation), add a decision in `Docs/Decisions` in the same change, and create/update the matching concept doc in `Docs/Concepts` if the subsystem's design is otherwise non-obvious from the code.
+
 ## Azure Key Vault — Secret Naming
 - Secret names must satisfy the pattern `^[0-9a-zA-Z-]+$` (alphanumerics and hyphens only; no underscores, dots, or spaces).
 - Hierarchy levels are separated by `--` (double hyphen), which maps to `:` in `IConfiguration`.