Historical Agent purpose and verification scope
The cited publisher source is an AGENT.md version dated2025-11-22 at18:01:10 UTC,declaring the name ado-sync-judge. Its documented purpose is: Review Azure DevOps synchronization correctness,conflict handling and lifecycle management. The historical rules prioritize external tracker status and distinguish strict increment completion from flexible specification states. These are historical Agent responsibilities,not outcomes tested here. The invocation-use-case section still contains TODO placeholders;this summary does not invent implemented features to fill them.
The catalog classifies the legacy record as a Skill. This page explicitly references a historical Agent document from the same publisher. Official original not verified for the old Skill. No mapping to its old SKILL.md,Skill installation entry or current package is established;the name,repository,URL,install command and install count are retained.
The publisher3.0guide checked on2026-10-18 lists multi-project routing,hierarchy and per-project field mapping as unsupported and says the old1.x command namespaces are gone;3.0also does not sync automatically on status changes. The old Agent responsibilities above must not be read as verified current sync capabilities or installation instructions.
Full related documents,exact Git paths and blobs were checked on2026-10-18 UTC. This is a factual purpose summary,not a complete Agent translation or recovery of the old Skill original. Current installation,invocation,cloud-service prices and runtime outcomes were not tested;document tasks,commands and configuration examples were not executed.