release: AAA 0.17.1 product language hardening - #200
Merged
Conversation
Owner
Author
|
Follow-up review fixes are in 80bb64c: embedded underscore identifiers and filenames are now blocked, scans fail closed on unreadable or non-UTF-8 source and traversal errors, diagnostics use repository labels plus relative paths only, and the default local provider path now resolves the sibling Across Orchestrator checkout. Evidence: focused release tests 23/23 passed; real-provider plus release-lock tests 15/15 passed without an environment override; full backend regression 1578/1578 passed without an override; the four-repository scan and open-source check passed. |
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
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.
Summary
Release train
Producer runtime versions are unchanged:
Local validation
Hosted live-E2E boundary
A manual GitHub-hosted live-E2E run correctly stopped before task creation because the hosted macOS runner had neither a configured cloud provider nor a local Agent. Dependency installation and the real Orchestrator provider succeeded. No private model credential was injected and the provider gate was not weakened. The equivalent full live journey passed locally through Codex CLI.
Boundaries