Update TfsNodeStructureTool Notes to new Format

[Copilot]

Updated all configuration examples and documentation in TfsNodeStructureTool-notes.md from the legacy format to the new structured format developed by @satano.

Changes Made

Configuration Format Migration:

• NodeBasePaths → Areas.Filters and Iterations.Filters
• AreaMaps → Areas.Mappings with structured Match/Replacement objects
• IterationMaps → Iterations.Mappings with structured Match/Replacement objects

Old Format:

{
  "$type": "TfsNodeStructureOptions",
  "NodeBasePaths": ["*\\Team 2", "*\\Sprint*"],
  "AreaMaps": {
    "^OriginalProject\\\\(DescopeThis|DescopeThat)": "TargetProject\\Archive\\Descoped\\"
  },
  "IterationMaps": {
    "^OriginalProject\\\\Path1(?=\\\\Sprint 2022)": "TargetProject\\AnotherPath\\NewTeam"
  }
}

New Format:

{
  "Areas": {
    "Filters": ["*\\Team 2"],
    "Mappings": [
      {
        "Match": "^OriginalProject\\\\(DescopeThis|DescopeThat)(.*)$",
        "Replacement": "TargetProject\\Archive\\Descoped\\$1$2"
      }
    ]
  },
  "Iterations": {
    "Filters": ["*\\Sprint*"],
    "Mappings": [
      {
        "Match": "^OriginalProject\\\\Path1(?=\\\\Sprint 2022)(.*)$",
        "Replacement": "TargetProject\\AnotherPath\\NewTeam$1"
      }
    ]
  }
}

Documentation Updates

• ✅ Updated all JSON configuration examples throughout the document
• ✅ Updated Filters section table to use new property structure
• ✅ Updated explanatory text and bullet points to reference new format
• ✅ Updated warning text to reflect Match/Replacement property structure
• ✅ Converted all examples from key-value mapping pairs to structured objects
• ✅ Fixed terminology references throughout the document
• ✅ Verified changes by running documentation generator successfully

The documentation now consistently uses the new format across all examples, making it easier for users to configure TfsNodeStructureTool with the current implementation.

Fixes #2757.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[MrHinsh]

While working for other types we lost the classFile on field mapps like fieldtofieldmultimap in docs/_data/reference.fieldmaps.fieldtofieldmultimap.yaml. It looks like thsi is during the document generation.

[Copilot]

While working for other types we lost the classFile on field mapps like fieldtofieldmultimap in docs/_data/reference.fieldmaps.fieldtofieldmultimap.yaml. It looks like thsi is during the documen...

Fixed the missing classFile properties in the documentation generation. The issue was caused by a case-sensitivity problem in the CodeFileFinder where class name FieldToFieldMultiMap (uppercase "To") wasn't matching the filename FieldtoFieldMultiMap.cs (lowercase "to"). Enhanced the finder to use case-insensitive matching as a fallback. (b998bba)

[nkdagility-actions-bot]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2758.westeurope.5.azurestaticapps.net

[MrHinsh]

The code samples are going missing.

[Copilot]

The code samples are going missing.

Fixed the missing code samples issue in the documentation generator. The problem was that the generator wasn't properly loading the configuration from the repository root appsettings.json file. Updated the configuration loading logic to use the correct path resolution, and now all tools, processors, field maps, and endpoints have proper "defaults" and "sample" configuration examples instead of the generic "not found" messages. (994b8dc)

[nkdagility-actions-bot]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2758.westeurope.5.azurestaticapps.net

[MrHinsh]

This is incorrect. Check the samples for the format, but ignore "classic"...

{
      "$type": "TfsNodeStructureToolOptions",
      "Enabled": true,
      "Areas": {
        "Filters": [],
        "Mappings": [
          {
            "Match": "^Skypoint Cloud$",
            "Replacement": "MigrationTest5"
          }
        ]
      },
      "Iterations": {
        "Filters": [],
        "Mappings": [
          {
            "Match": "^Skypoint Cloud\\\\Sprint 1$",
            "Replacement": "MigrationTest5\\Sprint 1"
          }
        ]
      },
      "ShouldCreateMissingRevisionPaths": true,
      "ReplicateAllExistingNodes": true
    }

[Copilot]

This is incorrect. Check the samples for the format, but ignore "classic"...

...

Fixed the TfsNodeStructureTool samples to use simpler, more realistic examples as requested. Replaced the complex regex patterns with beginner-friendly simple matches like ^Skypoint Cloud$ → MigrationTest5 and ^Skypoint Cloud\\\\Sprint 1$ → MigrationTest5\\Sprint 1. (a32213e)

[nkdagility-actions-bot]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2758.westeurope.5.azurestaticapps.net