chore(adlc): update shared harness pin - #190
Merged
Merged
Conversation
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.
Update the pinned Agentic OS harness from
30118a76856c6d0535037a61b7a0f7d9e8e92af5to protected upstream revision8c2650cefac8ba37435832adfa2314846725f21a, so the existing ADLC CI runs the current shared evaluator and lifecycle assets.Validation:
npm testpassed, including 25 ADLC migration tests and the installed upstream readiness, documentation-budget, and module-budget evaluators.npm ls --depth=0confirmed the exact revision;git diff --checkpassed. The diff changes only the existing package pin and lockfile; production deployment remains separate.Lane: agent/huis-macbook-pro-3.local/lean-harness-pin
Base-Revision: 5b11438
Source-Head: 561b3b7