musubix3 0.1.2 → 0.1.3

package/.github/plugin/marketplace.json

@@ -3,13 +3,13 @@
   "owner": { "name": "nahisaho" },
   "metadata": {
     "description": "GitHub Copilot CLI specification-driven development skills",
-    "version": "0.1.2"
+    "version": "0.1.3"
   },
   "plugins": [
     {
       "name": "musubix3",
       "source": ".",
-      "version": "0.1.2",
+      "version": "0.1.3",
       "description": "Evidence-driven SDD without duplicating native Copilot capabilities."
     }
   ]

package/.github/skills/sdd-formal-codegraph/SKILL.md

@@ -41,12 +41,12 @@ After the work, run `npx musubix3 workflow-record sdd-formal-codegraph complete
    JS/TS imports, re-exports, literal require/dynamic imports, manifest
    entrypoints and local cache-busting URL/templates with a static base are indexed.
    Set `codeGraph.mode` to `strict` when unresolved computed `import()` or
-   `require()` calls must block graph gates; the compatible default warns.
-   Conservative native adapters index Rust modules/`use`, Python imports, Go
-   module imports, Java package imports, C/C++ includes, C# namespace imports,
-   PHP namespace/import dependencies, R source/package dependencies and Julia
-   include/module imports, declarations and direct calls. Other languages are
-   reported as unsupported.
+   `require()` calls, including computed PHP include/require expressions, must
+   block graph gates; the compatible default warns.
+   Conservative native adapters index JS/TS, Rust, Python, Go, Java, Kotlin,
+   C/C++, Objective-C, C#/.NET, Ruby, PHP, Swift, Dart, Scala, Elixir, Haskell,
+   Lua, Zig, Solidity, R and Julia dependencies, declarations and direct calls.
+   Unrecognized extensions stay outside graph inputs.
    Statically resolved cache-busting imports remain valid in strict mode.
    Reflective behavior remains an explicit limitation.
 4. Use native navigation and review to confirm conservative results; rebuild

package/.github/skills/sdd-implementation/SKILL.md

@@ -18,8 +18,8 @@ After the work, run `npx musubix3 workflow-record sdd-implementation complete
    implementation. Configure the selected command with `tddArgs` containing
    `{testId}` or `{testPath}` and a `tddReport`, or use a built-in runner adapter.
    Follow its native identity contract: pytest/Cargo use underscore names, Go
-   uses a `TEST-*` subtest, and JUnit uses an exact `@Tag("TEST-*")` plus an
-   underscore-form ID in the method name.
+   uses a `TEST-*` subtest, JUnit uses an exact `@Tag("TEST-*")`, and xUnit uses
+   a `Fact` `DisplayName` containing the exact ID.
    Run the repository formatter before recording Red. Formatting is part of the
    test fingerprint: after Red, do not edit or reformat the authoritative test
    until the matching Green has been recorded.

package/.github/skills/sdd-quality/SKILL.md

@@ -14,7 +14,7 @@ completed` exactly once.
    explicit independent approval. Use only the exact `musubix3` CLI; never
    substitute similarly named npm packages.
 2. Configure real tests/build/typecheck commands and timeouts. Use an explicit
-   custom report or a built-in Vitest/Jest, pytest, Go test, Cargo or JUnit
+   custom report or a built-in Vitest/Jest, pytest, Go test, Cargo, JUnit or .NET
    adapter. Require executable native adapter contracts in CI; JUnit targets use
    an exact `@Tag("TEST-*")`, and pytest requires `pytest-json-report`. Review
    `requiredChecks`, `qualityProfile`, coverage thresholds and architecture rules.
@@ -27,8 +27,8 @@ completed` exactly once.
    `evidence refresh --json` runs the same fail-closed pipeline. If `input-stability` fails,
    inspect its per-path added/modified/deleted diagnostics and stop generators
    or formatters before rerunning. Standard dependency/build directories,
-   including manifest-scoped Cargo and Maven `target/` and conventional `.venv`
-   or `venv` roots with a regular `pyvenv.cfg`, are excluded; arbitrary source
+   including manifest-scoped Cargo/Maven `target/`, .NET `bin`/`obj`, project-local
+   `.nuget/packages`, and `.venv` or `venv` roots with a regular `pyvenv.cfg`, are excluded; arbitrary source
    directories and source-like generated inputs are not silently ignored.
    Changed mode reports Git changes and dependent files but conservatively runs
    all checks, including commands. It never treats unrun checks as successful.

package/.github/skills/sdd-traceability/SKILL.md

@@ -10,8 +10,12 @@ After the work, run `npx musubix3 workflow-record sdd-traceability complete
 --status completed` exactly once.
 
 1. Run `npx musubix3 trace build`. It scans `.musubix` artifacts and comment
-   annotations in JS/TS, Rust, Python, Go, Java/Kotlin, C/C++, C#, Ruby, PHP and
-   Swift, then generates feature `trace.json` files plus an ignored cache.
+   annotations in every Code Graph language, including JS/TS, Rust, Python, Go,
+   JVM, C/C++, .NET, Ruby, PHP, Swift, Dart, BEAM, Haskell, Lua, Zig, Solidity,
+   R and Julia, then generates feature `trace.json` files plus an ignored cache.
+   Haskell `--`/`{- ... -}`, Lua `--`/`--[[ ... ]]`, and Visual Basic
+   apostrophe/XML-documentation comments are scanned without accepting string
+   literals as trace annotations.
 2. Run `npx musubix3 trace check --strict --json`.
    Distinguish malformed IDs, dangling endpoints, stale inputs, and missing
    mandatory design/implementation/test coverage. Non-strict coverage warnings

package/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 ## Unreleased
 
+## 0.1.3 - 2026-09-08
+
+- Add a built-in `dotnet` test adapter with xUnit `DisplayName` targeting and
+  recursive TRX result normalization.
+- Exclude manifest-scoped .NET `bin/` and `obj/` output plus the conventional
+  project-local `.nuget/packages/` cache from snapshots and Code Graph indexing.
+- Exclude Gradle `.gradle/`, Dart `.dart_tool/`, SwiftPM `.build/`, Zig
+  `.zig-cache/`/`zig-out/`, and .NET `.dotnet/` CLI homes only when a nearby
+  ecosystem manifest identifies them as generated project state.
+- Detect C#/.NET projects in `mutation doctor` and safely probe a pinned local
+  Stryker.NET tool manifest without installing or downloading tools.
+- Add conservative Code Graph adapters for Kotlin, Ruby, Swift, Dart, Scala,
+  Elixir, Haskell, Lua, Zig, Solidity, Objective-C/Objective-C++, F# and
+  Visual Basic .NET, including local dependencies, declarations and direct calls.
+- Add Haskell, Lua, and Visual Basic trace-comment extraction with string
+  masking, and expose annotated/executed test identity counts as constitution
+  metrics.
+- Reduce native Code Graph false positives and improve Scala, Visual Basic,
+  Julia, PHP, Swift, Dart, Haskell, and Objective-C resolution precision.
+- Normalize JUnit identities from `system-out` display names independently of
+  XML attribute order, and recognize nested F# `(* ... *)` trace comments.
+- Validate large applications across all 23 supported language groups: 475
+  authored implementation files and 345 traced native tests, all gate-ready.
+
 ## 0.1.2 - 2026-09-07
 
 - Exclude conventional `.venv` and `venv` Python environments identified by a

package/README-ja.md

@@ -1,34 +1,68 @@
 # musubix3
 
-**最新公開版 v0.1.2 · GitHub Copilot CLI 専用 · Node.js ≥20 · TypeScript · MIT**
+**最新リリース v0.1.3 · GitHub Copilot CLI 専用 · Node.js ≥20 · TypeScript · MIT**
 
 [English](README.md)
 
 [musubix2 から musubix3 で変わったこと](MUSUBIX2-TO-MUSUBIX3.md)
 
-要求 → 憲章 → 設計・ADR → 実装 → 追跡可能性 → 品質根拠、という
-仕様駆動開発（SDD）を、8つの Skills と決定的な検証エンジンで支援します。
-形式的整合性検査、コンパイラによる依存解析、ローカル知識検索も含みます。
+GitHub Copilotは、計画、コード生成、編集、テスト、レビューを実行できます。
+musubix3は、その作業を本当に完了と判断するためのrepository-localな仕様と
+決定的な証拠を追加します。
+要求 → 憲章 → 設計・ADR → 実装 → 追跡可能性 → 品質根拠を、
+8つのSkillsと検証CLIで接続します。
 
 [musubix2](https://github.com/nahisaho/musubix2) の考え方を学び、3つの
 ワークスペースで新規実装しています。成果物の互換性・移行機能はありません。
 ID の接続や SAT 判定だけで、実装の正しさを保証するものではありません。
 
+## GitHub Copilotだけでは足りない理由
+
+Copilotは実装を担うエンジンです。要求を理解し、repositoryを調査し、計画を立て、
+ファイルを編集し、toolを実行して結果を説明します。これは不可欠ですが、
+会話が成功したことだけでは、次を継続的に証明できません。
+
+- 実装した振る舞いが、明示的で測定可能な要求と一致しているか
+- すべての要求が設計、コード、正本テストまで接続されているか
+- テストを書き換えず、本当にRedが先に失敗してGreenが成功したか
+- test、graph、formal、qualityの結果が現在のsourceに対して新鮮か
+- 要求変更が影響する成果物へ正しい順序で伝播したか
+- 最終gateを通すためにpolicyを弱めていないか
+
+「テストは成功しました」「実装は完了しました」という会話上の報告は、
+古くなる、範囲が不足する、repository外で失われる可能性があります。
+推論と開発はCopilotへ任せたまま、musubix3が完了条件を永続化し、
+機械検証できる形へ変換します。
+
+| GitHub Copilotが提供するもの | musubix3が補完するもの |
+|---|---|
+| 計画、実装、refactor、tool実行 | 明示的な要求、設計判断、実装link、完了条件を要求するrepository-local SDD Skills |
+| テスト生成とtest runner実行 | 構造化TEST ID、native report正規化、検証可能なRed/Green/Refactor証拠 |
+| 変更内容の説明 | 要求 → 設計 → コード → テストの型付きtraceと双方向impact解析 |
+| repository調査 | 決定的なCode Graph、未解決local dependency診断、architecture gate |
+| 制約・不変条件の提案 | 任意のZ3/Lean整合性検査と、形式モデルから成功テストまでの対応検査 |
+| session単位の完了報告 | freshness、fingerprint、input stability、保護されたpolicy baseline、attestation、fail-closedなready判定 |
+
+musubix3はCopilotを置き換えず、別のcoding agentも追加しません。
+SATだから実装が正しいとも主張しません。開発はCopilotが実行し、
+musubix3は仕様を残し、証拠を検査し、古い・不完全な完了宣言を拒否して、
+「なぜこの変更をreadyと判断できるのか」をreview可能な形でrepositoryへ残します。
+
 ## クイックスタート
 
 対象プロジェクトで、公開済みパッケージを実行します。
 
 ```sh
-npx musubix3@0.1.2 --version
-npx musubix3@0.1.2 init --dry-run
-npx musubix3@0.1.2 init
+npx musubix3@0.1.3 --version
+npx musubix3@0.1.3 init --dry-run
+npx musubix3@0.1.3 init
 copilot
 ```
 
 バージョンを固定してプロジェクトへインストールする場合は、次を実行します。
 
 ```sh
-npm install --save-dev --save-exact musubix3@0.1.2
+npm install --save-dev --save-exact musubix3@0.1.3
 npx --no-install musubix3 --version
 npx --no-install musubix3 init --dry-run
 npx --no-install musubix3 init
@@ -279,10 +313,12 @@ feature: auth
 `ADRs` / `Depends-On`。ADR には背景・採用案・却下案・結果を記録します。
 C4-like 図は明示した内容だけを描画し、完全な C4 モデルを推論しません。
 
-JS/TS、Rust、Python、Go、Java/Kotlin、C/C++、C#、Ruby、PHP、Swift の
 正本となるコード・テストに、エンティティごとに1つのコメントを追加します。
-JS/TS では文字列中の記載をリンクとして扱いません。その他の言語では行コメント
-またはブロックコメントを使用します。網羅率だけを満たす代理 JS/TS ファイルは作成しません。
+JS/TSはparser-awareなcomment位置を使い、Haskellは`--`と`{- ... -}`、
+Luaは`--`と`--[[ ... ]]`、Visual Basicは`'''` XML documentを含む
+apostrophe commentを扱います。これらは文字列中の記載をリンクとして扱いません。
+その他の言語では対応する行commentまたはblock commentを使用します。
+網羅率だけを満たす代理JS/TSファイルは作成しません。
 
 ```ts
 /** @id CODE-AUTH-001
@@ -377,8 +413,10 @@ glob は `*` / `**` / `?` に対応し、外部依存は `npm:` 接頭辞で表
 `tdd.redPreflightCommands`にはformatter等のplain command名を指定でき、
 Redのtest fingerprintを取得する前に成功が必須です。
 通常ファイルの`pyvenv.cfg`を含む`.venv`と`venv`はsnapshotと
-Code Graphから除外されますが、任意のsource directoryにmarkerを置いても
-除外されません。
+Code Graphから除外されます。Gradle `.gradle/`、Dart `.dart_tool/`、
+SwiftPM `.build/`、Zig `.zig-cache/`/`zig-out/`、.NET `.dotnet/`は、
+親directoryに対応manifestがある場合だけ除外されます。同名の任意source
+directoryは追跡対象のままです。
 `codeGraph.mode` の既定値は `compatible` で、未解決の計算された
 `import()` / `require()` は警告です。`strict` にするとグラフゲートを阻止する
 エラーになります。信頼済みbaselineが `strict` の場合、`compatible` への
@@ -411,12 +449,14 @@ strict OIDC identity/key binding、必須コマンド名の最低条件です。
 コマンド未設定は skipped です。
 
 TDD用コマンドには明示的な`tddArgs`と`tddReport`、または組込みの
-`vitest`、`jest`、`pytest`、`go-test`、`cargo`、`junit` adapterが必要です。
+`vitest`、`jest`、`pytest`、`go-test`、`cargo`、`junit`、`dotnet` adapterが必要です。
 明示設定を優先し、adapterは対象引数を導出してnative JSON/JSONL/XMLを正規化します。
 Vitest/Jestの無関係なskipped結果は対象TDDから除外します。pytestにはJSON pluginと
 `test_TEST_APP_001`形式、Goには`TEST-*`名のsubtest、Cargoには`test_app_001`形式、
-JUnitには正確な`@Tag("TEST-APP-001")`とIDをunderscore形式で含むmethod名が必要で、
-launcherのXML report directoryを読み取ります。各フェーズ前に旧レポートを削除し、
+JUnitには正確な`@Tag("TEST-APP-001")`と、IDを含むmethod名または`@DisplayName`を推奨します。
+正規化処理はtestcase属性とJUnit Platformのdisplay-name出力の両方を読み取り、
+xUnitには`[Fact(DisplayName = "TEST-APP-001 ...")]`が必要です。
+それぞれXMLまたはTRX report directoryを読み取ります。各フェーズ前に旧レポートを削除し、
 必要なreport親directoryを作成して、対象テストだけを含むfreshな `musubix-json` を要求します。Redは `failed`、
 Green/Refactorは `passed` のみ有効で、`skipped`、`error`、未生成、不正形式は失敗です。
 Green前にはテスト以外のプロジェクト入力が変更されている必要があります。
@@ -427,10 +467,11 @@ TDDと変更checkpointは共通の単調order ledgerを持ち、Red/Green境界
 明示的なmigration診断で失敗します。欠落・並べ替え・改変・孤立レコードは
 証拠を無効にします。
 
-CIでは6種類すべてについて独立したnative contractを実行します。Vitest、Jest、
+CIではVitest、Jest、
 `pytest-json-report`付きpytest、Go test、Cargo test、固定版JUnit Platform Consoleの
 各fixtureに無関係な失敗テストを置き、生成selectorが対象IDだけを実行し、実際のnative
-reportを正規化できることを検証します。Jestは開発時依存だけであり、Python、
+reportを正規化できることを検証します。.NET adapterは標準TRXを読み取り、
+C#アプリ実験とunit contractで追加検証します。Jestは開発時依存だけであり、Python、
 Go/Rust、Java/JUnitのtoolingはCIでのみ準備され、packageのruntime依存には含まれません。
 
 変更checkpointは各変更要件にリンクした実装とCode Graph上の依存だけを指紋化するため、
@@ -482,7 +523,8 @@ terminal transcriptの古さと未来方向clock skewも制限します。
 並行eventはtimestamp順で出力されない場合があるため、全体sortではなくtool/resultの
 因果順序を検査します。
 gate実行中に入力が変わった場合、`input-stability`は追加・変更・削除された各pathと
-前後のSHA-256を報告します。Cargo/Mavenの標準`target/`は除外しますが、
+前後のSHA-256を報告します。Cargo/Mavenの標準`target/`、manifest直下の
+.NET `bin/`と`obj/`、project-local `.nuget/packages/`は除外しますが、
 source相当の生成入力はfail-closedのままです。組込みadapterは対象test選択とreport引数を
 所有します。Cargo/Goの既存設定にある先頭`test`は安全に統合し、
 `--json-report`など競合するreport引数は早期拒否します。
@@ -565,13 +607,17 @@ Ed25519鍵はmusubix3外で生成し、公開PEMだけを`attestation oidc-audie
   シンボル影響は保守的な**ファイル単位**の逆依存になります。
   非リテラル読み込みは既定では警告ですが、`codeGraph.mode: "strict"` では
   グラフゲートを阻止します。未解決外部パッケージは警告、未解決ローカル参照はエラー。
-  Rust、Python、Go、Java、C/C++、C#、PHP、R、Juliaはローカル
-  import/module/include/source、宣言、直接呼び出しを保守的に解析します。
-  その他の言語は未対応として報告します。他言語用の代理 JS/TS ファイルは
-  作成しません。
-  bundler 独自解決、リフレクションは対象外です。
+  bundler 独自解決とリフレクションは対象外です。Rust、Python、Go、Java、
+  Kotlin、C/C++、Objective-C/Objective-C++、C#、F#、Visual Basic .NET、
+  Ruby、PHP、Swift、Dart、Scala、Elixir、Haskell、Lua、Zig、Solidity、R、
+  Juliaはローカルimport/module/include/source、宣言、直接呼び出しを
+  保守的に解析します。その他の拡張子はグラフ入力に含めません。他言語用の
+  代理 JS/TS ファイルは作成しません。
   build/cache/dependency と symlink は除外しますが、任意の `.gitignore` は
   スキャンフィルターとして読みません。
+- 残るarchitecture改善には、実測根拠を伴うstrict call-resolution ratio policyと、
+  より広いnative test-runner adapter対応があります。このreleaseでは推測的に
+  有効化しません。
 - 検索は **TF-IDF/cosine** であり GraphRAG でも意味推論でもありません。
   日本語は文字 bigram。Git 根拠は最大100コミット・各30ファイルで、共変更は相関、
   著者別ディレクトリ件数は貢献の記録であって因果や専門性ではありません。

package/README.md

@@ -1,36 +1,70 @@
 # musubix3
 
-**Latest published v0.1.2 · GitHub Copilot CLI only · Node.js ≥20 · TypeScript · MIT**
+**Latest release v0.1.3 · GitHub Copilot CLI only · Node.js ≥20 · TypeScript · MIT**
 
 [日本語](README-ja.md)
 
 [What changed from musubix2 to musubix3 (Japanese)](MUSUBIX2-TO-MUSUBIX3.md)
 
-Specification-driven development (SDD) skills backed by deterministic checks:
+GitHub Copilot can plan, generate, edit, test, and review software. musubix3
+adds the repository-local specifications and deterministic evidence needed to
+decide whether that work is actually complete:
 requirements → constitution → design/ADRs → implementation → traceability →
-quality evidence. Optional formal consistency, compiler dependency analysis and
-local knowledge retrieval support the workflow.
+quality evidence.
 
 Learned from [musubix2](https://github.com/nahisaho/musubix2)'s concepts, rebuilt
 cleanly in three workspaces. No artifact compatibility or migration is promised.
 This repository does **not** guarantee correctness simply because IDs are linked
 or requirements are satisfiable.
 
+## Why GitHub Copilot alone is not enough
+
+Copilot is the implementation engine. It understands a request, explores the
+repository, proposes a plan, edits files, runs tools, and explains the result.
+That is necessary, but a successful conversation is not durable proof that:
+
+- the implemented behavior matches an explicit, measurable requirement;
+- every requirement is connected to design, code, and an authoritative test;
+- Red really failed before Green passed without the test being rewritten;
+- test, graph, formal, and quality results still match the current source;
+- a requirement change propagated through all affected artifacts in order;
+- a policy was not weakened merely to make the final gate pass.
+
+Conversation text such as “tests passed” or “implementation complete” is not
+enough because it can become stale, omit scope, or disappear outside the
+repository. Copilot should remain responsible for reasoning and development;
+musubix3 makes the completion criteria persistent and machine-checkable.
+
+| GitHub Copilot provides | musubix3 complements it with |
+|---|---|
+| Planning, coding, refactoring, and tool execution | Repository-local SDD Skills that require explicit requirements, design decisions, implementation links, and completion conditions |
+| Test generation and runner execution | Structured TEST identities, native-report normalization, and verified Red/Green/Refactor evidence |
+| Explanations of what changed | Typed requirement → design → code → test traceability and bidirectional impact analysis |
+| Repository exploration | Deterministic Code Graph indexing, unresolved-local dependency diagnostics, and architecture gates |
+| Suggestions for constraints and invariants | Optional Z3/Lean consistency checks and model-to-passing-test correspondence |
+| A session-level completion report | Freshness, fingerprints, input-stability checks, protected policy baselines, attestations, and a fail-closed readiness gate |
+
+musubix3 does **not** replace Copilot, add another coding agent, or claim that
+formal satisfiability proves implementation correctness. Copilot performs the
+development; musubix3 records the specification, checks the evidence, rejects
+stale or incomplete claims, and leaves a reviewable answer to “why is this
+change ready?”
+
 ## Quick start
 
 Run the published package from the target project:
 
 ```sh
-npx musubix3@0.1.2 --version
-npx musubix3@0.1.2 init --dry-run
-npx musubix3@0.1.2 init
+npx musubix3@0.1.3 --version
+npx musubix3@0.1.3 init --dry-run
+npx musubix3@0.1.3 init
 copilot
 ```
 
 For a reproducible project-local installation:
 
 ```sh
-npm install --save-dev --save-exact musubix3@0.1.2
+npm install --save-dev --save-exact musubix3@0.1.3
 npx --no-install musubix3 --version
 npx --no-install musubix3 init --dry-run
 npx --no-install musubix3 init
@@ -279,9 +313,11 @@ Where/While/When clauses. Japanese controlled forms are documented in
 [README-ja.md](README-ja.md). These are syntax checks, not natural-language
 understanding; arbitrary prose is deliberately rejected.
 
-Source/test trace annotations are read from comments in JS/TS, Rust, Python, Go,
-Java/Kotlin, C/C++, C#, Ruby, PHP and Swift. JS/TS parsing excludes string
-literals; other languages require line or block comments:
+Source/test trace annotations are read from language comments. JS/TS uses
+parser-aware comment locations; Haskell supports `--` and `{- ... -}`, Lua
+supports `--` and `--[[ ... ]]`, and Visual Basic supports apostrophe comments
+including `'''` XML documentation. These scanners exclude string literals;
+other languages require their supported line or block comments:
 
 ```ts
 /** @id CODE-AUTH-001
@@ -380,7 +416,10 @@ Use `tdd.redPreflightCommands` to reference plain configured formatter commands;
 they must pass before Red captures the authoritative test fingerprint.
 Conventional `.venv` and `venv` Python environments containing a regular
 `pyvenv.cfg` are excluded from source snapshots and Code Graph indexing.
-Arbitrary source directories containing that marker remain tracked.
+Gradle `.gradle/`, Dart `.dart_tool/`, SwiftPM `.build/`, Zig
+`.zig-cache/`/`zig-out/`, and .NET `.dotnet/` CLI homes are excluded only when
+their parent contains the corresponding project manifest. Arbitrary same-named
+source directories remain tracked.
 `codeGraph.mode` defaults to `compatible`, where unresolved computed
 `import()`/`require()` calls remain warnings. Set it to `strict` to make those
 diagnostics gate-blocking errors. A trusted strict policy baseline prevents
@@ -416,15 +455,18 @@ failure or skip blocks readiness regardless of `requiredChecks.commands`.
 Optional command failures are nonblocking unless a constitution rule rejects the
 measured count. No configured commands is skipped, not passed.
 TDD commands require either command-specific `tddArgs` plus a `tddReport`, or a
-built-in `vitest`, `jest`, `pytest`, `go-test`, `cargo`, or `junit` adapter.
+built-in `vitest`, `jest`, `pytest`, `go-test`, `cargo`, `junit`, or `dotnet` adapter.
 Explicit custom configuration takes precedence. Adapters derive targeted
 arguments and normalize native JSON/JSONL/XML into `musubix-json`. Vitest/Jest
 reports may contain unrelated skipped tests; targeted TDD selects only the
 requested ID. pytest requires the JSON-report plugin and underscore-form test
 names such as `test_TEST_APP_001`. Go uses a `TEST-*` subtest name, Cargo uses a
-Rust identifier such as `test_app_001`. JUnit methods must carry an exact
-`@Tag("TEST-APP-001")`; keep the underscore-form ID in the method name so it is
-recoverable from the launcher's XML report. Before each phase, musubix3 deletes
+Rust identifier such as `test_app_001`. JUnit methods should carry an exact
+`@Tag("TEST-APP-001")` and an ID-bearing method name or `@DisplayName`; the
+normalizer reads both testcase attributes and JUnit Platform display-name output.
+xUnit tests use
+`[Fact(DisplayName = "TEST-APP-001 ...")]` so TRX preserves the identity.
+Before each phase, musubix3 deletes
 the previous report, creates any required report parent directory, and requires a fresh
 `musubix-json` document containing exactly the selected test. Its status must be
 `failed` during Red and `passed` during Green/Refactor; `skipped`, `error`,
@@ -437,9 +479,10 @@ informational. Legacy chronology without order evidence fails with an explicit
 migration diagnostic. Missing, reordered, altered or orphaned records invalidate
 the evidence.
 
-CI executes isolated native contracts for all six adapters: Vitest, Jest,
+CI executes isolated native contracts for Vitest, Jest,
 pytest with `pytest-json-report`, Go test, Cargo test, and the pinned JUnit
-Platform Console. Each fixture contains an unrelated failing test, proving that
+Platform Console. The .NET adapter consumes standard TRX and is additionally
+validated by unit contracts and the C# application experiment. Each fixture contains an unrelated failing test, proving that
 the generated selector executes only the requested identity and that the real
 native report normalizes correctly. Jest is development-only; the Python,
 Go/Rust, and Java/JUnit tooling is provisioned only in CI and is not shipped as
@@ -510,8 +553,9 @@ Unrelated concurrent events may be emitted out of timestamp order, so strict mod
 checks causal tool/result ordering rather than imposing a global timestamp sort.
 If project inputs change while a gate is running, `input-stability` reports each
 added, modified, or deleted path with before/after SHA-256 values. Standard
-Cargo/Maven `target/` output is excluded, but source-like generated inputs remain
-fail-closed. Built-in adapters own their targeting and report arguments. A
+Cargo/Maven `target/`, manifest-scoped .NET `bin/` and `obj/`, and project-local
+`.nuget/packages/` output are excluded, but source-like generated inputs remain fail-closed.
+Built-in adapters own their targeting and report arguments. A
 legacy leading Cargo/Go `test` subcommand is merged safely; conflicting report
 flags such as `--json-report` are rejected.
 Changes during a gate fail input stability; later source/config changes make
@@ -608,14 +652,18 @@ transcript/session fields into the Ed25519 signature.
   best-effort; symbol impact conservatively expands at **file** level. Nonliteral
   loading is a compatibility warning unless `codeGraph.mode` is `strict`, when
   it blocks graph gates; unresolved external packages remain warnings and
-  unresolved local imports are errors. Bundler-specific resolution, reflection and other
-  Rust, Python, Go, Java, C/C++, C#, PHP, R and Julia have conservative native
-  adapters for local imports/modules/includes, declarations and direct calls.
-  Other languages are reported as unsupported. Ignored
-  build/cache/dependency directories and
+  unresolved local imports are errors. Bundler-specific resolution and
+  reflection remain out of scope. Rust, Python, Go, Java, Kotlin, C/C++,
+  Objective-C/Objective-C++, C#, F#, Visual Basic .NET, Ruby, PHP, Swift, Dart,
+  Scala, Elixir, Haskell, Lua, Zig, Solidity, R and Julia have conservative
+  native adapters for local imports/modules/includes, declarations and direct
+  calls. Other extensions are omitted from graph inputs. Ignored build/cache/dependency directories and
   symlinks are not indexed; custom `.gitignore` rules are not a scan filter.
-- Trace annotations support all languages listed above. Do not create JS/TS
-  proxy files for another language.
+- Remaining architectural work includes evidence-backed strict call-resolution
+  ratio policy and broader native test-runner adapter coverage. Neither is
+  enabled speculatively by this release.
+- Trace annotation comment syntax is documented above. Do not create JS/TS proxy
+  files for another language.
 - Knowledge ranking is **TF-IDF/cosine, not GraphRAG** or semantic reasoning.
   Japanese uses character bigrams. Git co-change and author-directory counts
   cover at most 100 commits/30 files per commit; they indicate correlation and