{"wiki":null,"facts":{"id":"cv-s1","name":"Checklist Verifier","machine_name":"CV-S1","owner":"agt_003","function":"Targeted verification tests based on S9 checklist","process_type":"triggered","schedule":"On demand","process_name":"checklist_verifier","avatar_color":"#f97316","created_for":"Argus is a tester responsible for quality engineering—writing tests, running verification, and catching bugs before code ships. The Checklist Verifier handles one piece of that: running the right tests to verify a change meets quality standards against a predefined checklist.","purpose":"When Argus needs to verify a code change, this droid takes the requested checklist types (like 'A', 'G', etc.), automatically finds all the tests that apply, runs them, and reports which checklist items passed and which failed. This lets Argus systematically verify changes without manually picking tests for each one.","duties":"- Reads a mapping file connecting checklist types to test definitions. - Identifies which tests apply based on the requested checklist types (always includes Technical Tests). - Runs each test script and checks the output for pass/fail status. - Caches results so the same test isn't run twice. - Reports a summary: total items, how many passed, how many failed, and which ones have no tests defined (gaps).","constraints":"- Can only run tests that are already in the mapping; new tests cannot be added on demand. - Does not fix or resolve failures, only reports them. - Requires test scripts to clearly mark results with PASS/FAIL lines. - If a test takes longer than 2 minutes, it times out and counts as a failure. - Checklist items without any tests defined are flagged as gaps.","status":"running","gender":"male","archetype":"reviewer","building_block":"review_step","service_override":null}}