[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699GKMJCM1AHEX5DYSN8SXK":3,"skill-same:01M699GKMJCM1AHEX5DYSN8SXK":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M699GKMJCM1AHEX5DYSN8SXK","troubleshoot-binlog-mcp",null,"Diagnose dotnet-msbuild binlog MCP startup failures. USE FOR: CONNECTION_CLOSED, binlog server won't connect, missing binlog tools, Microsoft.AITools.BinlogMcp not found, dnx launch errors. Checks workspace SDK, feeds, and source mapping without bypassing policy. DO NOT USE FOR: errors inside a binlog (use binlog-failure-analysis), capturing binlogs (use binlog-generation), unrelated MCP servers.","microsoft\u002Ftestfx","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699C71CJ91B5WZ3AXG3GG2M",1059,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftroubleshoot-binlog-mcp\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,9,44,45],"troubleshoot","troubleshoot binlog mcp","MCP","server","source","for","errors","mapping","missing","do","unrelated","use","analysis","Tools","feeds","connect","diagnose","msbuild","dotnet","launch","policy","sdk","2026-11-10 10:12:30",false,"---\nname: troubleshoot-binlog-mcp\ndescription: \"Diagnose dotnet-msbuild binlog MCP startup failures. USE FOR: CONNECTION_CLOSED, binlog server won't connect, missing binlog tools, Microsoft.AITools.BinlogMcp not found, dnx launch errors. Checks workspace SDK, feeds, and source mapping without bypassing policy. DO NOT USE FOR: errors inside a binlog (use binlog-failure-analysis), capturing binlogs (use binlog-generation), unrelated MCP servers.\"\nlicense: MIT\n---\n\n# Troubleshoot Binlog MCP Startup\n\nExplain why the plugin's binlog MCP server cannot connect and give an evidence-based,\npolicy-safe recovery. This diagnoses the **server launch**, not failures recorded in a build.\nNo binlog file or project build is needed.\n\nThis skill runs on demand. It cannot see a host error that was never exposed to the agent,\ninject session-start context, or guarantee activation merely because a plugin was installed.\n\n## 1. Establish what failed\n\nUse the user's error and any host MCP status or startup logs already available.\n`CONNECTION_CLOSED` alone says that the transport closed, not why. Do not translate it\ndirectly into \"package missing.\"\n\n- If the binlog server is connected and its tools are discoverable, stop startup troubleshooting.\n  Continue the original binlog analysis; do not change a working setup.\n- If the plugin's skills loaded but its binlog server did not, continue below.\n- If the plugin itself is not installed\u002Fenabled or no server is registered, address that host\n  configuration first. Do not diagnose NuGet package resolution without a launch attempt.\n- If execution or host logs are unavailable, explain that limit and give the next command for\n  the user to run. Never claim to have inspected logs or repaired a connection.\n\n## 2. Match the host's workspace and SDK\n\nDiscover the affected workspace directory and the host's actual MCP command, arguments, and\nenvironment from available configuration. The shipped command is:\n\n```text\ndotnet dnx Microsoft.AITools.BinlogMcp --yes --prerelease\n```\n\nRun diagnostics from that workspace with the host's environment, not from the plugin directory\nor a temporary directory with different NuGet settings. Inspect:\n\n```text\ndotnet --info\ndotnet --version\ndotnet nuget list source\n```\n\nCheck the applicable `global.json` and inherited NuGet configuration, including parent\u002Fuser\nconfiguration, `clear`, disabled sources, and `packageSourceMapping`. A workspace `clear`\ncan replace the default nuget.org source with a private mirror that lacks this package.\nAn installed SDK is not necessarily the SDK selected in this directory. The shipped\n`dotnet dnx` command requires a .NET 10+ SDK.\n\nDo not dump credential settings, private feed URLs, tokens, or credential-provider output into\nthe answer. Inspect locally as needed and report a redacted source label and relevant error.\n\n## 3. Capture the real launch error\n\nPrefer an existing startup log from the failing host. Otherwise reproduce its **unchanged**\nlaunch command once, from the affected workspace, capturing both stdout and stderr plus the\nexit code. Do not initially add `--source`, replace the configuration, remove `global.json`,\nclear caches, or install another copy: those change the conditions being diagnosed.\n\nA stdio MCP server may remain running waiting for protocol input. Keep stdin open while\nobserving startup and use a bounded execution (for example, 30 seconds) with cleanup of only\nthe diagnostic process tree, including credential-provider children. Use the host's supported\ntimeout\u002Fcancellation facility; if it cannot safely clean up, ask the user to run the command\nlocally instead. Do not leave a background server running or kill unrelated `dotnet` processes.\nA timeout, silence, or an open process is **not** proof that MCP initialized.\n\nOnly if package availability remains unclear, run this supporting probe under the same\nworkspace settings with a bounded execution:\n\n```text\ndotnet package search Microsoft.AITools.BinlogMcp --exact-match --prerelease --format json\n```\n\nInspect the exact package ID and version in `searchResult[].packages`, and check both top-level\nand per-source `problems`. Exit code zero alone does not establish a successful search.\n\n| Observed evidence | Diagnosis and next action |\n|-------------------|---------------------------|\n| `dnx` reports no matching version in the configured feeds | Those settings did not resolve the package. Check whether the approved mirror provides prerelease versions of this exact package. |\n| Search returns no packages and no source problems | Only the searched feeds lack a listed match. This is not proof that `dnx` must fail: a cached tool or unlisted version may still work. |\n| Search has top-level\u002Fper-source problems, HTTP 401\u002F403, TLS, network, or credential-provider errors | Availability is unverified, not \"package missing.\" Address the specific feed\u002Faccess failure first, even if search exited zero. |\n| Search finds the package but `dnx` fails | Follow the launch error. Search does not apply package source mapping; check mapping, restore\u002Fdownload access, and runtime requirements. Do not declare the connection healthy. |\n| Missing `dotnet`, unrecognized `dnx`, or SDK selection error | Fix the host's PATH\u002FSDK selection. Account for `global.json`; do not silently upgrade the repository or remove its SDK pin. |\n| Timeout, unsupported search command, or malformed\u002Fnon-JSON output | Report an inconclusive probe. Use launch logs or a user-run diagnostic; do not infer absence or success. |\n| Launch succeeds but host connection still fails | Investigate the host's actual command\u002Fenvironment and MCP initialization logs; package discovery is no longer the demonstrated failure. |\n\nDo not repeat expensive probes once the evidence establishes the next action.\n\n## 4. Choose a policy-safe recovery\n\nRecommend the smallest change supported by the observed failure:\n\n- Have the feed owner mirror `Microsoft.AITools.BinlogMcp` and its required versions\u002Fdependencies\n  into an approved feed, or correct an approved mapping that excludes it.\n- Repair the approved feed's authentication, connectivity, or certificate configuration when\n  that is the observed problem. Never suggest disabling certificate validation.\n- Add nuget.org only if organizational policy permits and the user approves the change.\n  Do not remove `clear`, disable source mapping, or override sources to bypass enterprise policy.\n- If appropriate and approved, install the tool from an approved feed and register its\n  `binlog-mcp` executable with the host as an alternative MCP server. Confirm the executable's\n  path and avoid registering a duplicate server. Installation alone is not connection recovery.\n- For SDK\u002FPATH issues, make the required SDK available to the host or use a deliberately\n  configured alternative launch. Ask before changing repository SDK selection.\n\nDo not edit NuGet settings, host registration, or SDK pins without the user's approval.\nIf policy prevents recovery, say so. For an existing binlog, offer the text-log replay fallback\nin `binlog-failure-analysis` rather than blocking build diagnosis on MCP repair.\n\n## 5. Verify and report\n\nAfter an approved change, reconnect\u002Frestart the server using the host's supported controls.\nConfirm MCP initialization and a tool listing that contains binlog tools such as\n`binlog_overview`. If a binlog is available, resume the original analysis.\n\nReport the observed cause (or what remains unknown), the relevant redacted evidence, the\nsmallest recovery, and what was actually verified. End with one status line:\n\n```text\nMCP status: connected\n```\n\nUse `connected` only after the host discovers the server's tools, `failed` for an observed\nlaunch\u002Fconnection failure, and `unverified` when only probes or advice are available.\nNever substitute \"package found\" or \"tool installed\" for a verified MCP connection.\n","# Troubleshoot Binlog MCP Startup\n\nExplain why the plugin's binlog MCP server cannot connect and give an evidence-based,\npolicy-safe recovery. This diagnoses the **server launch**, not failures recorded in a build.\nNo binlog file or project build is needed.\n\nThis skill runs on demand. It cannot see a host error that was never exposed to the agent,\ninject session-start context, or guarantee activation merely because a plugin was installed.\n\n## 1. Establish what failed\n\nUse the user's error and any host MCP status or startup logs already available.\n`CONNECTION_CLOSED` alone says that the transport closed, not why. Do not translate it\ndirectly into \"package missing.\"\n\n- If the binlog server is connected and its tools are discoverable, stop startup troubleshooting.\n  Continue the original binlog analysis; do not change a working setup.\n- If the plugin's skills loaded but its binlog server did not, continue below.\n- If the plugin itself is not installed\u002Fenabled or no server is registered, address that host\n  configuration first. Do not diagnose NuGet package resolution without a launch attempt.\n- If execution or host logs are unavailable, explain that limit and give the next command for\n  the user to run. Never claim to have inspected logs or repaired a connection.\n\n## 2. Match the host's workspace and SDK\n\nDiscover the affected workspace directory and the host's actual MCP command, arguments, and\nenvironment from available configuration. The shipped command is:\n\n```text\ndotnet dnx Microsoft.AITools.BinlogMcp --yes --prerelease\n```\n\nRun diagnostics from that workspace with the host's environment, not from the plugin directory\nor a temporary directory with different NuGet settings. Inspect:\n\n```text\ndotnet --info\ndotnet --version\ndotnet nuget list source\n```\n\nCheck the applicable `global.json` and inherited NuGet configuration, including parent\u002Fuser\nconfiguration, `clear`, disabled sources, and `packageSourceMapping`. A workspace `clear`\ncan replace the default nuget.org source with a private mirror that lacks this package.\nAn installed SDK is not necessarily the SDK selected in this directory. The shipped\n`dotnet dnx` command requires a .NET 10+ SDK.\n\nDo not dump credential settings, private feed URLs, tokens, or credential-provider output into\nthe answer. Inspect locally as needed and report a redacted source label and relevant error.\n\n## 3. Capture the real launch error\n\nPrefer an existing startup log from the failing host. Otherwise reproduce its **unchanged**\nlaunch command once, from the affected workspace, capturing both stdout and stderr plus the\nexit code. Do not initially add `--source`, replace the configuration, remove `global.json`,\nclear caches, or install another copy: those change the conditions being diagnosed.\n\nA stdio MCP server may remain running waiting for protocol input. Keep stdin open while\nobserving startup and use a bounded execution (for example, 30 seconds) with cleanup of only\nthe diagnostic process tree, including credential-provider children. Use the host's supported\ntimeout\u002Fcancellation facility; if it cannot safely clean up, ask the user to run the command\nlocally instead. Do not leave a background server running or kill unrelated `dotnet` processes.\nA timeout, silence, or an open process is **not** proof that MCP initialized.\n\nOnly if package availability remains unclear, run this supporting probe under the same\nworkspace settings with a bounded execution:\n\n```text\ndotnet package search Microsoft.AITools.BinlogMcp --exact-match --prerelease --format json\n```\n\nInspect the exact package ID and version in `searchResult[].packages`, and check both top-level\nand per-source `problems`. Exit code zero alone does not establish a successful search.\n\n| Observed evidence | Diagnosis and next action |\n|-------------------|---------------------------|\n| `dnx` reports no matching version in the configured feeds | Those settings did not resolve the package. Check whether the approved mirror provides prerelease versions of this exact package. |\n| Search returns no packages and no source problems | Only the searched feeds lack a listed match. This is not proof that `dnx` must fail: a cached tool or unlisted version may still work. |\n| Search has top-level\u002Fper-source problems, HTTP 401\u002F403, TLS, network, or credential-provider errors | Availability is unverified, not \"package missing.\" Address the specific feed\u002Faccess failure first, even if search exited zero. |\n| Search finds the package but `dnx` fails | Follow the launch error. Search does not apply package source mapping; check mapping, restore\u002Fdownload access, and runtime requirements. Do not declare the connection healthy. |\n| Missing `dotnet`, unrecognized `dnx`, or SDK selection error | Fix the host's PATH\u002FSDK selection. Account for `global.json`; do not silently upgrade the repository or remove its SDK pin. |\n| Timeout, unsupported search command, or malformed\u002Fnon-JSON output | Report an inconclusive probe. Use launch logs or a user-run diagnostic; do not infer absence or success. |\n| Launch succeeds but host connection still fails | Investigate the host's actual command\u002Fenvironment and MCP initialization logs; package discovery is no longer the demonstrated failure. |\n\nDo not repeat expensive probes once the evidence establishes the next action.\n\n## 4. Choose a policy-safe recovery\n\nRecommend the smallest change supported by the observed failure:\n\n- Have the feed owner mirror `Microsoft.AITools.BinlogMcp` and its required versions\u002Fdependencies\n  into an approved feed, or correct an approved mapping that excludes it.\n- Repair the approved feed's authentication, connectivity, or certificate configuration when\n  that is the observed problem. Never suggest disabling certificate validation.\n- Add nuget.org only if organizational policy permits and the user approves the change.\n  Do not remove `clear`, disable source mapping, or override sources to bypass enterprise policy.\n- If appropriate and approved, install the tool from an approved feed and register its\n  `binlog-mcp` executable with the host as an alternative MCP server. Confirm the executable's\n  path and avoid registering a duplicate server. Installation alone is not connection recovery.\n- For SDK\u002FPATH issues, make the required SDK available to the host or use a deliberately\n  configured alternative launch. Ask before changing repository SDK selection.\n\nDo not edit NuGet settings, host registration, or SDK pins without the user's approval.\nIf policy prevents recovery, say so. For an existing binlog, offer the text-log replay fallback\nin `binlog-failure-analysis` rather than blocking build diagnosis on MCP repair.\n\n## 5. Verify and report\n\nAfter an approved change, reconnect\u002Frestart the server using the host's supported controls.\nConfirm MCP initialization and a tool listing that contains binlog tools such as\n`binlog_overview`. If a binlog is available, resume the original analysis.\n\nReport the observed cause (or what remains unknown), the relevant redacted evidence, the\nsmallest recovery, and what was actually verified. End with one status line:\n\n```text\nMCP status: connected\n```\n\nUse `connected` only after the host discovers the server's tools, `failed` for an observed\nlaunch\u002Fconnection failure, and `unverified` when only probes or advice are available.\nNever substitute \"package found\" or \"tool installed\" for a verified MCP connection.\n",{"name":5,"license":15,"description":7},"main","f8f2bfd77819bb789d4736ce7db4a567a37fcf7e",".agents\u002Fskills\u002Ftroubleshoot-binlog-mcp",315,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 14:01:43",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002Ftestfx --skill troubleshoot-binlog-mcp",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002Ftestfx --skill troubleshoot-binlog-mcp",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002Ftestfx --skill troubleshoot-binlog-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftroubleshoot-binlog-mcp\u002FSKILL.md",true,[],[75,100,128,149,168,191],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":46},"01M70GYY0AV0JGMTHE2CN6TNYK","dotnet-breaking-changes","Use before changing .NET\u002FC# code whose callers you do not control: a NuGet library, or a repo with PublicAPI.Shipped\u002FUnshipped.txt, ApiCompat, multiple TargetFrameworks, InternalsVisibleTo, or generated (.g.cs) partials. Green builds miss silent breaks from optional parameters, parameter names, sealing, const values, nullability, and #if. USE FOR: \"without breaking existing callers\"; adding a public method, overload, optional parameter, or interface member to a shipped library; renaming a public method or an internal helper a friend assembly uses; consolidating duplicated logic; changing a signature, nullability, default, or attribute; adding a target framework; RS0016\u002FRS0017 or ApiCompat errors; \"is this PR breaking?\". For a rename, extract, or merge, also invoke csharp-refactoring. DO NOT USE FOR: an executable whose callers all live in one project; renaming a local variable or private member, even in a shipped library; formatting; framework\u002FSDK\u002FNuGet upgrades (use dotnet-upgrade).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdotnet-breaking-changes\u002FSKILL.md",[],[42,82,83,84,85,86,87,30,88,89,90,91,92,93,94,95,96,97,98,99],"dotnet breaking changes","changes","green","project","default","local","interface","generated","upgrade","invoke","you","code","refactoring","merge","rename","library","live","assembly",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":109,"publishedAt":46},"01M699HHE9DTZWAMPB1ZR7ZKSW","testfx-test-value-evidence","Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-test-value-evidence\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[110,111,112,113,114,115,116,117,118,119,120,121,35,122,123,124,83,125,126,127],"test","testfx test value evidence","test value evidence","evidence","value","review","parallel","toolchain","commits","implementing","prs","only","when","apply","with","behavior","Safety","conventions",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":46},"01M699HEYWH1B9XGNBFY8J2FZS","testfx-parallel-safety-preflight","Check concurrency and isolation before implementing or refactoring TestFx tests, lifecycle code, helpers, shared-state declarations, or production paths those tests exercise. Use before narrowing DoNotParallelize or ResourceLock, changing parallelization settings, or introducing asynchronous workers; repeat against the final diff.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-parallel-safety-preflight\u002FSKILL.md",[],[135,126,136,116,137,138,119,139,93,140,94,141,142,143,144,145,146,147,35,148],"testfx parallel safety preflight","preflight","shared","asynchronous","exercise","concurrency","paths","isolation","helpers","diff","parallelization","lifecycle","tests","workers",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":46},"01M699HC61ZV9GJ2C8JV03951G","testfx-localization-validation","Validate generated TestFx localization catalogs, resource IDs, placeholders and locked tokens. Use for RESX\u002FXLF changes, OneLoc PRs, localization build failures, duplicate targets or units, and orphaned translation entries.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-localization-validation\u002FSKILL.md",[],[156,157,158,159,160,161,29,162,163,120,89,35,164,165,83,166,167],"testfx localization validation","validation","localization","validate","translation","ids","tokens","entries","units","duplicate","targets","build",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":46},"01M699H9J2NWQXE4BDT6R0FH7S","testfx-acceptance-validation","Validate TestFx shipping paths and capable CI execution using packed consumers, package\u002Fcache provenance, exact exits and artifacts, and selected-versus-executed test evidence. Use for acceptance regressions, package\u002FMSBuild\u002Flauncher\u002Fprotocol changes, or skipped-only CI results; not for unrelated unit-only or documentation changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-acceptance-validation\u002FSKILL.md",[174],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},[176,177,157,110,41,113,178,179,180,121,181,35,182,183,184,185,34,186,187,188,189,190,141,29],"testfx acceptance validation","acceptance","launcher","ci","execution","package","cache","artifacts","provenance","documentation","shipping","results","protocol","unit","ci results",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":46},"01M699H70BB999BT4F627T1PHE","session-delivery-hygiene","Gate local-session scope, persistent delivery, live PR state, integration provenance, and owned cleanup. Use before implementing guidance changes, changing or pushing PR work, diagnosing package\u002Foutput mismatches, or handing off implementation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsession-delivery-hygiene\u002FSKILL.md",[],[198,199,200,201,202,119,87,203,204,98,205,181,35,184,206,207,83,208,209,210],"session delivery hygiene","delivery","session","hygiene","scope","cleanup","work","pr","output","state","integration","guidance","gate"]