fix: validation sweep — lifecycle & registry (6 solutions)#228
Merged
Conversation
Addresses Issue #59 from judeper/OceanSquad. scope-drift-monitor: - Bump doc footers from v1.2.1 to v1.2.2 in 5 docs files (prerequisites, dataverse-schema, flow-configuration, troubleshooting, baseline-configuration) - Fix v1.1.1 date from July 2026 to March 2026 in CHANGELOG and README version history (chronologically impossible — sat between Feb and Apr entries) agent-365-lifecycle-governance: - Bump DELIVERY-CHECKLIST.md version from v1.1.4 to v1.1.5 (2 locations) to match current solution version - Update Python requirements.txt minimum versions: requests >=2.28.0 -> >=2.32.0 (CVE-2024-35195 fix) msal >=1.20.0 -> >=1.30.0 (token caching improvements) azure-identity >=1.16.0 -> >=1.18.0 (CAE support) agent-registry-automation: - Update Microsoft.Graph recommended version from 2.36.1 to 2.37.0 in docs/prerequisites.md Validation summary (all 6 solutions): - 49 Microsoft Learn URLs validated — all resolve (200) - No FSI language rule violations in non-CHANGELOG files - No Azure AD product naming issues in non-CHANGELOG files - PowerShell modules current (Az.Accounts 5.3.4, PnP 2.5.0+) - Graph API permissions current (AgentInstance.ReadWrite.All) - Cross-solution references valid (4 checked) - Dataverse column naming compliant No issues found in: agent-intake, agent-knowledge-source-scanner, environment-lifecycle-management (docs already current). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Validation Sweep — Lifecycle & Registry (6 solutions)
Addresses OceanSquad Issue #59.
Scope
Full accuracy validation of 6 lifecycle & registry solutions:
agent-365-lifecycle-governanceagent-registry-automationagent-intakeagent-knowledge-source-scannerenvironment-lifecycle-managementscope-drift-monitorWhat was validated
AgentInstance.ReadWrite.AllcurrentFixes applied
scope-drift-monitor:
July 2026→March 2026(was chronologically impossible — sat between Feb and Apr entries)agent-365-lifecycle-governance:
requests >=2.28.0→>=2.32.0(CVE-2024-35195),msal >=1.20.0→>=1.30.0,azure-identity >=1.16.0→>=1.18.0agent-registry-automation:
No issues found in
agent-intake— docs already current at v1.0.0-previewagent-knowledge-source-scanner— docs already current at v1.1.2environment-lifecycle-management— docs already current at v1.2.2Items for human review
2026-07-15to2026-03-15based on chronological ordering. Please verify this is the correct date.