Skip to content

Refactor mock adapter into composable scenario fixtures #9

@simonhsze

Description

@simonhsze

What

Break up adapters/mock.py into smaller, composable pieces so the mock review path stays maintainable as scenarios expand.

Motivation

adapters/mock.py has grown into a very large file with scenario-specific challenges, defenses, judge guidance, and evidence heuristics all mixed together. It works, but it is now a clear maintenance hotspot and makes the public code surface harder to trust and extend.

Scope

  • split scenario constants, templates, and evidence heuristics into separate modules or fixture files
  • keep deterministic mock behavior for tests
  • preserve current public demo behavior and scenario-aware scoring
  • add or update tests to protect behavior during the refactor

Why this matters

The mock adapter is now part of the public product story, not just an internal test helper. Its implementation should be understandable and maintainable enough to support that role.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions