Remove scope labels from context output and update README example

README.md

@@ -70,6 +70,9 @@ evidence-source:
   type: url                # 'none', 'url', or 'fileshare'
   location: https://reviews.example.com/evidence/index.json
 
+context:                             # optional: reference docs for all reviewers
+  - "docs/design/introduction.md"
+
 reviews:
   - id: Core-Logic
     title: Review of core business logic

docs/design/review-mark/configuration.md

@@ -76,8 +76,8 @@ enumeration and owns SHA-256 fingerprinting, document generation, and elaboratio
 4. `PublishReviewReport()` accepts `ReviewIndex` as a parameter and calls `GetEvidence()`
    for each review-set to determine Current, Stale, Missing, or Failed status.
 5. `ElaborateReviewSet()` generates a Markdown document that includes an optional Context
-   subsection listing resolved context files labeled `[global]` (from `GlobalContext`) or
-   `[local]` (from `ReviewSet.Context`); the subsection is omitted when no context files
+   subsection listing resolved context files as plain paths (global context files first,
+   followed by per-review-set context files); the subsection is omitted when no context files
    resolve. `ReviewSet.Context` holds per-review-set context glob patterns; these patterns
    identify reference material shown during elaboration and do not provide review coverage.
 

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

@@ -98,8 +98,9 @@ and a boolean indicating whether any review-set is non-current.
 Looks up the review-set with the given `id`, resolves its file list and fingerprint, and
 returns a Markdown document with a heading at `markdownDepth`, a metadata table (ID, Title,
 Fingerprint), an optional Context subsection, and a Files subheading. The Context subsection
-lists all resolved context files labeled `[global]` (from `GlobalContext`) or `[local]` (from
-`review.Context`), and is omitted when no context files resolve. Throws `ArgumentException`
+lists all resolved context files as plain paths (global context files from `GlobalContext`
+first, followed by per-review-set files from `review.Context`), and is omitted when no
+context files resolve. Throws `ArgumentException`
 for unknown IDs; throws `ArgumentOutOfRangeException` when `markdownDepth > 5`.
 
 **Coverage note:** Context entries are reference material only. A file listed in `context:` is

docs/reqstream/review-mark/configuration/review-mark-configuration.yaml

@@ -232,8 +232,8 @@ sections:
               - id: ReviewMark-Config-ContextInElaboration
                 title: >-
                   ElaborateReviewSet shall include a Context subsection listing all resolved context
-                  files labeled [global] (from the top-level list) or [local] (from the
-                  per-review-set list), omitting the subsection when no context files exist.
+                  files as plain paths (global context first, then per-review-set context),
+                  omitting the subsection when no context files exist.
                 justification: |
                   Reviewers need to know which reference files to consult.
                 tests:

docs/user_guide/introduction.md

@@ -524,8 +524,8 @@ The command prints a Markdown document to the console:
 
 ## Context
 
-- `[global] docs/design/introduction.md`
-- `[local]  docs/design/core.md`
+- `docs/design/introduction.md`
+- `docs/design/core.md`
 
 ## Files
 

docs/verification/review-mark/configuration/review-mark-configuration.md

@@ -121,14 +121,14 @@ by `ReviewSet_GetFingerprint_ContextNotIncluded`.
 **ReviewMarkConfiguration_ElaborateReviewSet_GlobalContext_AppearsInOutput**:
 `ElaborateReviewSet` is called on a configuration with a global `context:` list; the context
 files exist on disk. Expected outcome: the output Markdown contains a `Context` subsection and
-each context file is listed with the `[global]` label. Requirement coverage:
+each context file is listed as a plain path. Requirement coverage:
 `ReviewMark-Config-ContextInElaboration`. This scenario is tested by
 `ReviewMarkConfiguration_ElaborateReviewSet_GlobalContext_AppearsInOutput`.
 
 **ReviewMarkConfiguration_ElaborateReviewSet_LocalContext_AppearsInOutput**:
 `ElaborateReviewSet` is called on a configuration with a per-review-set `context:` list; the
 context files exist on disk. Expected outcome: the output Markdown contains a `Context`
-subsection and each context file is listed with the `[local]` label. Requirement coverage:
+subsection and each context file is listed as a plain path. Requirement coverage:
 `ReviewMark-Config-ContextInElaboration`. This scenario is tested by
 `ReviewMarkConfiguration_ElaborateReviewSet_LocalContext_AppearsInOutput`.
 

src/DemaConsulting.ReviewMark/Configuration/ReviewMarkConfiguration.cs

@@ -363,7 +363,7 @@
     ///     "Core-Logic" and "core-logic" are distinct IDs. Evidence-source type uses OrdinalIgnoreCase
     ///     because types like "fileshare" and "FILESHARE" are semantically identical.
     /// </remarks>
     internal static void ValidateReviews(
         string filePath,
         IReadOnlyList<ReviewSetYaml> reviews,
         ICollection<LintIssue> issues)
@@ -1102,11 +1102,9 @@
         sb.AppendLine($"| Fingerprint | `{fingerprint}` |");
         sb.AppendLine();
 
-        // Resolve global and local context files, labeling each with its scope
-        var globalContextFiles = GlobMatcher.GetMatchingFiles(directory, GlobalContext)
-            .Select(f => $"[global] {f}");
-        var localContextFiles = GlobMatcher.GetMatchingFiles(directory, review.Context)
-            .Select(f => $"[local]  {f}");
+        // Resolve global and local context files; global files appear first
+        var globalContextFiles = GlobMatcher.GetMatchingFiles(directory, GlobalContext);
+        var localContextFiles = GlobMatcher.GetMatchingFiles(directory, review.Context);
         var allContext = globalContextFiles.Concat(localContextFiles).ToList();
 
         // Emit the context subsection only when at least one context file resolves

test/DemaConsulting.ReviewMark.Tests/Configuration/ReviewMarkConfigurationTests.cs

@@ -1166,7 +1166,7 @@ public void ReviewSet_GetFingerprint_ContextNotIncluded()
     }
 
     /// <summary>
-    ///     Test that ElaborateReviewSet includes a Context subsection with [global] labels
+    ///     Test that ElaborateReviewSet includes a Context subsection with plain file paths
     ///     when global context files resolve.
     /// </summary>
     [Fact]
@@ -1196,14 +1196,13 @@ public void ReviewMarkConfiguration_ElaborateReviewSet_GlobalContext_AppearsInOu
         // Act
         var result = config.ElaborateReviewSet("Core-Logic", _testDirectory);
 
-        // Assert — context subsection is present and the file is labeled [global]
+        // Assert — context subsection is present and the file appears as a plain path
         Assert.Contains("## Context", result.Markdown);
-        Assert.Contains("[global]", result.Markdown);
         Assert.Contains("docs/design.md", result.Markdown);
     }
 
     /// <summary>
-    ///     Test that ElaborateReviewSet includes a Context subsection with [local] labels
+    ///     Test that ElaborateReviewSet includes a Context subsection with plain file paths
     ///     when per-review-set context files resolve.
     /// </summary>
     [Fact]
@@ -1233,9 +1232,8 @@ public void ReviewMarkConfiguration_ElaborateReviewSet_LocalContext_AppearsInOut
         // Act
         var result = config.ElaborateReviewSet("Core-Logic", _testDirectory);
 
-        // Assert — context subsection is present and the file is labeled [local]
+        // Assert — context subsection is present and the file appears as a plain path
         Assert.Contains("## Context", result.Markdown);
-        Assert.Contains("[local]", result.Markdown);
         Assert.Contains("docs/design.md", result.Markdown);
     }