docs: correct Java-only language claims across documentation

MethodAtlas now supports Java, C#/.NET, and TypeScript/JavaScript, but
multiple high-visibility pages still described it as a Java-only tool.
Updated mkdocs.yml site description, landing page hero and feature bullets,
for-security-teams guide (intro, column descriptions, tag explanation),
apply-tags and apply-tags-from-csv mode descriptions, and data-governance
page to reflect all three supported languages accurately.

Author: leogalambos

docs/concepts/data-governance.md

@@ -12,7 +12,7 @@ external communication under any configuration:
 | Operation | Data involved |
 |---|---|
 | Source file traversal | File paths and names within the scan root |
-| Java parsing (JavaParser) | Test source file content — in memory only |
+| Source file parsing (Java, C#, TypeScript) | Test source file content — in memory only |
 | Method discovery | Parsed AST nodes — in memory only |
 | Content hash computation | SHA-256 of the AST string — no content transmitted |
 | CSV / SARIF / plain-text output | Result data written to stdout or a local file |
@@ -37,9 +37,10 @@ provider's inference API. Each request contains exactly:
    This list is included to prevent the AI from inventing or omitting
    methods; only methods the parser found are classified.
 
-3. **The test class source file** — the full text of one Java source file
-   from the scan root, used as semantic context for classification. The file
-   is truncated to the character limit set by [`-ai-max-class-chars`](../cli-reference.md#-ai-max-class-chars)
+3. **The test class source file** — the full text of one test source file
+   (Java, C#, or TypeScript) from the scan root, used as semantic context for
+   classification. The file is truncated to the character limit set by
+   [`-ai-max-class-chars`](../cli-reference.md#-ai-max-class-chars)
    (default: 40 000 characters) before transmission. The class name and all
    method names are always included; if the class body exceeds the limit, the
    trailing lines of the file are omitted.
@@ -65,7 +66,7 @@ Nothing else from the project is included.
 | Other test files submitted as context | No — each class is submitted independently |
 | File paths or directory structure | No — only the class source text and method names are included; the absolute path on disk is not transmitted |
 
-The AI provider receives the text of one Java test class at a time. No
+The AI provider receives the text of one test class (Java, C#, or TypeScript) at a time. No
 information about the surrounding project structure, the production
 implementation, or any other file is included.
 

docs/concepts/for-security-teams.md

@@ -1,6 +1,6 @@
 # Guide for Security Teams
 
-MethodAtlas scans a project's Java test source code and produces a structured inventory of test methods that are relevant to security. This guide is written for security managers, compliance officers, and CISOs who receive MethodAtlas output and need to interpret it, act on findings, and incorporate results into audit evidence packages. It does not assume familiarity with Java development or CI/CD tooling.
+MethodAtlas scans a project's test source code (Java, C#, or TypeScript/JavaScript) and produces a structured inventory of test methods that are relevant to security. This guide is written for security managers, compliance officers, and CISOs who receive MethodAtlas output and need to interpret it, act on findings, and incorporate results into audit evidence packages. It does not assume familiarity with any specific development technology or CI/CD tooling.
 
 ## When you receive a CSV
 
@@ -14,7 +14,7 @@ For a complete column reference, see [Output Formats](../output-formats.md).
 
 ## What MethodAtlas produces
 
-MethodAtlas reads a project's Java test source code and produces a structured
+MethodAtlas reads a project's test source code (Java, C#, or TypeScript/JavaScript) and produces a structured
 inventory of test methods that are security-relevant — methods written to
 verify that the application correctly implements authentication, cryptography,
 input validation, access control, and similar security properties.
@@ -30,11 +30,11 @@ the source changes.
 
 | Column | Present when | Meaning |
 |---|---|---|
-| `fqcn` | Always | Fully qualified class name — the Java package and class that contains this test |
+| `fqcn` | Always | Fully qualified class name — the package/namespace and class that contains this test |
 | `method` | Always | The name of the test method |
 | `loc` | Always | Inclusive line count of the method declaration |
-| `tags` | Always | JUnit `@Tag` values declared in source (e.g. `security`, `auth`) |
-| `display_name` | Always | Text of the `@DisplayName` annotation declared on the method; empty when the annotation is absent or declares an empty string (`@DisplayName("")`) |
+| `tags` | Always | Source-level tag values declared on the test (e.g. `security`, `auth`) — `@Tag` in Java, `[Category]`/`[Trait]` in C# |
+| `display_name` | Always | Display name declared on the method (e.g. `@DisplayName` in Java, `[Fact(DisplayName=…)]` in C#); empty when absent |
 | `content_hash` | `-content-hash` flag | SHA-256 fingerprint of the enclosing class source — enables revision traceability |
 
 ### AI enrichment (present when AI classification is enabled)
@@ -104,7 +104,7 @@ measured by the interaction score.
 
 MethodAtlas produces two independent kinds of security labels for each test method:
 
-**Source-level tags** (`tags` column) are labels (`@Tag("security")`, `@Tag("auth")`, etc.) that a developer typed directly into the Java source file. They are factual — they represent what the developer intended when writing the test. They do not change unless a developer edits the source.
+**Source-level tags** (`tags` column) are labels that a developer typed directly into the source file — `@Tag("security")` in Java, `[Category("security")]`/`[Trait("Tag", "security")]` in C#. They are factual — they represent what the developer intended when writing the test. They do not change unless a developer edits the source.
 
 **AI classifications** (`ai_security_relevant`, `ai_tags`, `ai_display_name`, `ai_reason` columns) are produced by an AI model that reads the test method body and reasons about what the test actually does. The AI does not rely on the developer's intent; it reads the code.
 

docs/overrides/home.html

@@ -186,9 +186,9 @@
   <section class="hero">
     <h1>MethodAtlas</h1>
     <p>
-      Scan Java test sources (JUnit&nbsp;5, JUnit&nbsp;4, TestNG), build a structured
-      security test inventory, and enrich results with AI-generated classification &mdash;
-      without compiling a single class.
+      Scan test sources across Java (JUnit&nbsp;5, JUnit&nbsp;4, TestNG), C# (xUnit, NUnit, MSTest),
+      and TypeScript/JavaScript (Jest, Vitest, Mocha); build a structured security test inventory
+      and enrich results with AI-generated classification &mdash; without compiling a single class.
     </p>
     <div class="hero-buttons">
       <a class="btn-primary" href="installation/">Get started</a>
@@ -207,8 +207,8 @@ <h1>MethodAtlas</h1>
           <div>
             <strong>Source-level test inventory</strong>
             <p>Discovers test methods via lexical parsing &mdash; no compilation required.
-               Supports JUnit&nbsp;5, JUnit&nbsp;4, and TestNG; framework is detected automatically
-               from import declarations.</p>
+               Supports Java (JUnit&nbsp;5, JUnit&nbsp;4, TestNG), C# (xUnit, NUnit, MSTest),
+               and TypeScript/JavaScript (Jest, Vitest, Mocha); framework detected automatically.</p>
           </div>
         </li>
         <li>
@@ -233,9 +233,8 @@ <h1>MethodAtlas</h1>
           <span class="feature-check">✓</span>
           <div>
             <strong>Source write-back</strong>
-            <p>The <code>-apply-tags</code> mode inserts AI-suggested <code>@DisplayName</code>
-               and <code>@Tag</code> annotations directly into source files using a
-               lexical-preserving printer.</p>
+            <p>The <code>-apply-tags</code> mode inserts AI-suggested display names and tags
+               directly into Java and C# source files using a lexical-preserving printer.</p>
           </div>
         </li>
         <li>

docs/usage-modes/apply-tags-from-csv.md

@@ -1,6 +1,6 @@
 # Apply Tags from CSV
 
-The `-apply-tags-from-csv <file>` mode applies reviewed annotation decisions back to Java source files. It reads a MethodAtlas CSV that a human has already reviewed and edited, then writes exactly the `@Tag` and `@DisplayName` annotations recorded in that CSV.
+The `-apply-tags-from-csv <file>` mode applies reviewed annotation decisions back to source files (Java and C#). It reads a MethodAtlas CSV that a human has already reviewed and edited, then writes the tag and display-name annotations recorded in that CSV.
 
 ## When to use this mode
 

docs/usage-modes/apply-tags.md

@@ -1,6 +1,6 @@
 # Source Write-back
 
-The `-apply-tags` modifier instructs MethodAtlas to insert AI-generated `@DisplayName` and `@Tag` annotations directly into the scanned `.java` source files, instead of writing a CSV report.
+The `-apply-tags` modifier instructs MethodAtlas to insert AI-generated display names and tags directly into the scanned Java (`.java`) and C# (`.cs`) source files, instead of writing a CSV report.
 
 ## When to use this mode
 

mkdocs.yml

@@ -1,7 +1,8 @@
 site_name: MethodAtlas
 site_description: >-
-  Scan Java test sources (JUnit 5, JUnit 4, TestNG), build a structured
-  security test inventory, and enrich results with AI-generated classification.
+  Scan test sources across Java (JUnit 5, JUnit 4, TestNG), C# (xUnit, NUnit, MSTest),
+  and TypeScript/JavaScript (Jest, Vitest, Mocha); build a structured security test
+  inventory and enrich results with AI-generated classification.
   Built for regulated environments.
 site_url: https://accenture.github.io/MethodAtlas/
 repo_url: https://github.com/Accenture/MethodAtlas