exp-test-tagging

# Test Trait Tagging Analyze an existing test suite and apply a standardized set of trait tags to each test method, giving teams visibility into their test distribution (positive vs. negative, critical-path coverage, smoke tests, etc.). ## When to Use - Auditing a test project to understand the mix of test types - Adding trait attributes to untagged tests - Generating a summary report of trait distribution across a test suite - Reviewing whether critical paths have sufficient coverage ## When Not to Use - Writing new tests from scratch (use `writing-mstest-tests`) - Running or filtering tests (use `run-tests`) - Migrating between test frameworks ## Inputs | Input | Required | Description | |-------|----------|-------------| | Test project or files | Yes | Path to the test project, folder, or specific test files to analyze | | Scope | No | `tag` (apply attributes), `audit` (report only), or `both` (default: `both`) | | Framework | No | Auto-detected. Override with `mstest`, `xunit`, or `nunit` if detection fails | ## Trait Taxonomy Use exactly these trait names and values. Do not invent new trait values outside this table. | Trait Value | Meaning | Heuristics | |-------------|---------|------------| | `positive` | Verifies expected behavior under normal/valid conditions | Asserts success, valid output, expected state, no exceptions for valid input | | `negative` | Verifies correct handling of invalid input, errors, or edge cases | Asserts exceptions, error codes, val...