Skip to content

fix(badblueprint): use harness paths in scenario TOML#8

Closed
lemontreeran wants to merge 1 commit intosubmission/purple_vanguardfrom
codex/update-harness-branch-for-badblueprint-toml
Closed

fix(badblueprint): use harness paths in scenario TOML#8
lemontreeran wants to merge 1 commit intosubmission/purple_vanguardfrom
codex/update-harness-branch-for-badblueprint-toml

Conversation

@lemontreeran
Copy link
Collaborator

Motivation

  • Ensure the badblueprint scenario references the real harness orchestrator and agent scripts so the Colab notebook FULL SCORING preflight can run without manual patching.

Description

  • Updated scenarios/security_arena/submissions/purple_vanguard/badblueprint/scenario_badblueprint.toml to replace the green agent command with python scenarios/security_arena/orchestrator.py ... and to replace attacker/defender commands with python scenarios/security_arena/agents/generic_attacker.py ... and python scenarios/security_arena/agents/generic_defender.py ..., leaving all other TOML parameters unchanged.

Testing

  • Ran automated checks that scenarios/security_arena/orchestrator.py, scenarios/security_arena/agents/generic_attacker.py, and scenarios/security_arena/agents/generic_defender.py exist and verified the TOML no longer contains vendor/agentbeats-lambda/ or scripts/run_badblueprint_orchestrator.py, and all checks passed.

Codex Task

@lemontreeran lemontreeran deleted the codex/update-harness-branch-for-badblueprint-toml branch January 14, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant