feat: add managed Android Appium setup - #4913
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Category | Results |
|---|---|
| Documentation | 4 minor |
| CodeStyle | 3 minor |
🟢 Metrics 665 complexity · 0 duplication
Metric Results Complexity 665 Duplication 0
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Contributor
Author
Solo adversarial requirement auditReviewed the final diff against every #4898 acceptance row and the caller/state matrices. No blocking finding remains.
Final verification:
The issue remains open intentionally until the companion documentation PR is merged and its final issue-level audit is recorded. |
|
You have reached your Codex usage limits for security reviews. Please try again later. |
MohabMohie
added a commit
to ShaftHQ/shafthq.github.io
that referenced
this pull request
Aug 14, 2026
## Summary - document the provider-backed `MOBILE_ANDROID` setup, exact pins, explicit license approval, platform prerequisites, cache/offline rules, and owned lifecycle recovery - document shared MCP ownership and receipt-bound engine bootstrap, including explicit-remote precedence and child-only environment - add a mutation-sensitive docs contract for the recurring CLI commands and public behavior - restore the canonical social-card RGBA format required by the existing repository contract after the latest base image optimization changed it to RGB Companion documentation for ShaftHQ/SHAFT_ENGINE#4898 and engine PRs ShaftHQ/SHAFT_ENGINE#4913 and ShaftHQ/SHAFT_ENGINE#4917. ## Verification - `node tests/android-infrastructure-docs.test.js` - `yarn test:docs` - `yarn test` - `yarn typecheck` - `yarn build` - local `yarn test:playwright` reached no assertions because the required Chromium revision is absent; the PR gate installs Chromium and provides the rendered browser evidence Graphify refresh is intentionally skipped under the session's explicit no-Graphify constraint. The repository's Graphify maintenance contract still passed as part of `yarn test`.
12 tasks
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.
Summary
SHAFT.Infrastructureadaptersaapt2acceptanceVerification
shaft-infrastructure: 101 tests green (2 platform-specific Windows skips)Review
The final solo adversarial requirement audit found no blocking issue. Companion documentation will follow in a separate PR before the issue-level completion audit.
Issue: #4898