Repository navigation
Release 0.6.10 with minimal core setup and optional workflows - #7
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.
Fresh agent setup installs the connection/reference core and MCP entry. Customers explicitly select optional skills or recipes; upgrades and removal preserve their policy, records and retained dependencies. The reference now explains the existing --out option when a customer requests a saved portable check result.
All336 copied source files match the accepted product package. Cold public validation passed748tests with one Linux-only skip. After two output-instruction paragraphs changed, all implementation/dependency hashes stayed unchanged and52affected installer/output checks passed. Relocated actual SDK tests, interfaces and tarball boundaries pass; production dependency audit reports zero vulnerabilities. The209-file artifact is bound to its final hash. GitHub workflows are unchanged.
One native Claude developer-context trial completed the same requested supplied-pair check/save using --out and preserved customer records. Four earlier requested-task failures remain retained. This does not establish clean-client, unfamiliar-human, hosted/customer or comparative-value acceptance.
Product source integration: https://github.com/sunlover7/agentlinkops/pull/268. Merge after exact source integration and final initiative notes validation, then tagv0.6.10 and verify the published registry artifact, Homebrew, marketplace and discovery surfaces independently.