Add public social account guard scenario#26
Open
kriptoburak wants to merge 1 commit into
Open
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
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
public_social_account_actionsrisk-rule category for risky social account automation.docs/social-account-guard.mdand link it from the Guard section so users can run the scenario without live credentials.Validation
git diff --cached --checkuv run --python 3.11 --extra dev pytest tests/test_risk_test_service.py tests/test_guard_risk_rules.py -q- 14 passednpm view @xquik/tweetclaw version dist.tarball repository.url homepage --jsonconfirmed1.6.31; npm package page returned a 403 bot-protection response; pre-existing commented README imageassets/comon_option.pngis missing.uv run --python 3.11 --extra dev pytest tests -qcurrently has 160 passed and 11 unrelated failures in guard model token expectations, nanobot stream/session behavior, and system-status path handling.No live social accounts, credentials, or write actions were used.