docs: align design documentation, review sets, tests, and PathHelpers with removal of Linting subsystem

.reviewmark.yaml

@@ -79,6 +79,7 @@ reviews:
       - "docs/design/version-mark/configuration/configuration.md"               # subsystem design
       - "docs/design/version-mark/configuration/version-mark-config.md"         # VersionMarkConfig unit design
       - "docs/design/version-mark/configuration/tool-config.md"                 # ToolConfig unit design
+      - "docs/design/version-mark/configuration/lint-issue.md"                  # LintIssue unit design
       - "test/**/Configuration/ConfigurationSubsystemTests.cs"                  # subsystem tests
 
   - id: VersionMark-VersionMarkConfig-Review
@@ -97,6 +98,14 @@ reviews:
       - "src/**/Configuration/VersionMarkConfig.cs"                             # implementation
       - "test/**/Configuration/VersionMarkConfigTests.cs"                       # unit tests
 
+  - id: VersionMark-LintIssue-Review
+    title: Review of LintIssue Unit
+    paths:
+      - "docs/reqstream/version-mark/configuration/load.yaml"                   # requirements
+      - "docs/design/version-mark/configuration/lint-issue.md"                  # design
+      - "src/**/Configuration/LintIssue.cs"                                     # implementation
+      - "test/**/Configuration/LintIssueTests.cs"                               # unit tests
+
   # Capture Subsystem
   - id: VersionMark-Capture-Subsystem
     title: Review of Capture Subsystem
@@ -131,23 +140,6 @@ reviews:
       - "src/**/Publishing/MarkdownFormatter.cs"                          # implementation
       - "test/**/Publishing/MarkdownFormatterTests.cs"                    # unit tests
 
-  # Linting Subsystem
-  - id: VersionMark-Linting-Subsystem
-    title: Review of Linting Subsystem
-    paths:
-      - "docs/reqstream/version-mark/linting/linting.yaml"      # subsystem requirements
-      - "docs/design/version-mark/linting/linting.md"           # subsystem design
-      - "docs/design/version-mark/linting/lint.md"              # Lint unit design
-      - "test/**/Linting/LintingSubsystemTests.cs"              # subsystem tests
-
-  - id: VersionMark-Lint-Review
-    title: Review of Lint Unit
-    paths:
-      - "docs/reqstream/version-mark/linting/lint.yaml"         # requirements
-      - "docs/design/version-mark/linting/lint.md"              # design
-      - "src/**/Linting/Lint.cs"                                # implementation
-      - "test/**/Linting/LintTests.cs"                          # unit tests
-
   # SelfTest Subsystem
   - id: VersionMark-SelfTest-Subsystem
     title: Review of SelfTest Subsystem

docs/design/definition.yaml

@@ -12,12 +12,11 @@ input-files:
   - docs/design/version-mark/configuration/configuration.md
   - docs/design/version-mark/configuration/tool-config.md
   - docs/design/version-mark/configuration/version-mark-config.md
+  - docs/design/version-mark/configuration/lint-issue.md
   - docs/design/version-mark/capture/capture.md
   - docs/design/version-mark/capture/version-info.md
   - docs/design/version-mark/publishing/publishing.md
   - docs/design/version-mark/publishing/markdown-formatter.md
-  - docs/design/version-mark/linting/linting.md
-  - docs/design/version-mark/linting/lint.md
   - docs/design/version-mark/self-test/self-test.md
   - docs/design/version-mark/self-test/validation.md
   - docs/design/version-mark/self-test/path-helpers.md

docs/design/version-mark/cli/program.md

@@ -50,5 +50,7 @@ error handling to `context.WriteError`. These methods satisfy requirements
 ## RunLint
 
 `RunLint` is a private helper called from `Run`. It resolves the configuration file path,
-defaulting to `.versionmark.yaml` when `context.LintFile` is `null`, then delegates to
-`Lint.Run`. This satisfies requirement `VersionMark-CommandLine-Lint`.
+defaulting to `.versionmark.yaml` when `context.LintFile` is `null`, then calls
+`VersionMarkConfig.Load` to validate the configuration. It reports all discovered issues via
+`result.ReportIssues` and confirms success when no issues were found. This satisfies
+requirement `VersionMark-CommandLine-Lint`.

docs/design/version-mark/configuration/configuration.md

@@ -3,6 +3,7 @@
 ## Overview
 
 The configuration subsystem reads and interprets the `.versionmark.yaml` file that defines
-which tools to capture and how to extract their versions. It consists of two units:
-`ToolConfig` (per-tool settings) and `VersionMarkConfig` (the top-level configuration
-container).
+which tools to capture and how to extract their versions, and reports any validation issues
+found during loading. It consists of three units: `ToolConfig` (per-tool settings),
+`VersionMarkConfig` (the top-level configuration container and validation entry point), and
+`LintIssue` (the types used to surface validation issues to callers).

docs/design/version-mark/configuration/lint-issue.md

@@ -0,0 +1,45 @@
+# LintIssue Unit
+
+## Overview
+
+`LintIssue.cs` contains the types used to surface validation issues found while loading a
+`.versionmark.yaml` configuration file. It defines three public types: the `LintSeverity`
+enumeration, the `LintIssue` record, and the `VersionMarkLoadResult` record.
+
+## LintSeverity Enumeration
+
+`LintSeverity` classifies the severity of a validation issue:
+
+| Value     | Meaning                                                                    |
+|-----------|----------------------------------------------------------------------------|
+| `Warning` | Non-fatal advisory message; loading continues.                             |
+| `Error`   | Fatal validation failure that prevents the configuration from being built. |
+
+## LintIssue Record
+
+`LintIssue` represents a single issue found during configuration loading. It carries:
+
+| Property      | Type           | Description                                    |
+|---------------|----------------|------------------------------------------------|
+| `FilePath`    | `string`       | Path to the file containing the issue.         |
+| `Line`        | `long`         | One-based line number of the issue.            |
+| `Column`      | `long`         | One-based column number of the issue.          |
+| `Severity`    | `LintSeverity` | Severity classification.                       |
+| `Description` | `string`       | Human-readable description of the issue.       |
+
+`ToString` formats the record as `"{FilePath}({Line},{Column}): {severity}: {Description}"`,
+producing output in the familiar `file(line,col): error: message` format understood by CI
+systems and editors.
+
+## VersionMarkLoadResult Record
+
+`VersionMarkLoadResult` is the return type of `VersionMarkConfig.Load`. It bundles two
+properties:
+
+| Property | Type                       | Description                                                                 |
+|----------|----------------------------|-----------------------------------------------------------------------------|
+| `Config` | `VersionMarkConfig?`       | The loaded configuration, or `null` when errors prevented building it.      |
+| `Issues` | `IReadOnlyList<LintIssue>` | All validation issues; may contain warnings even when `Config` is non-null. |
+
+The `ReportIssues` method writes all issues to a `Context`, routing `LintSeverity.Error`
+issues to `context.WriteError` and `LintSeverity.Warning` issues to `context.WriteLine`.

docs/design/version-mark/version-mark.md

@@ -73,11 +73,15 @@ Cli Subsystem → Capture Subsystem (VersionInfo.LoadFromFile) → Publishing Su
 ### Lint Mode
 
 ```text
-Cli Subsystem → Linting Subsystem
+Cli Subsystem → Configuration Subsystem (VersionMarkConfig.Load)
 ```
 
-1. The Cli Subsystem (Program) calls `RunLint`, which resolves the config file path.
-2. The Linting Subsystem validates the YAML structure and reports all issues.
+1. The Cli Subsystem (Program) calls `RunLint`, which resolves the config file path,
+   defaulting to `.versionmark.yaml`.
+2. `RunLint` delegates to `VersionMarkConfig.Load`, which validates the YAML structure and
+   returns a `VersionMarkLoadResult` containing all `LintIssue` records found.
+3. `RunLint` calls `result.ReportIssues` to write all issues to the context, then confirms
+   success when no issues were found.
 
 ### Validate Mode