You are an agent, your current working directory is /app.

You can use the tools available to you to interact with the computer to assist the user in completing tasks.

# Repair the static-analysis pipeline

The workspace contains a frozen, offline Bandit source tree under `/app/vendor/bandit` and two representative inputs under `/app/inputs`. A regression affects the line-oriented bidirectional-control-character check when its finding passes through the shared tester.

Repair the existing source modules so that:

- Running `python3 -m bandit -q -f json -o /app/output.json /app/inputs/suspicious.py /app/inputs/latin1.py` completes and writes valid JSON.
- The suspicious input produces exactly one B613 finding, with high severity, medium confidence, CWE 838, and the finding's manually identified line and column preserved in the serialized result.
- The Latin-1 input completes without an analyzer traceback and produces no B613 finding.
- The shared tester still supplies context-derived location data for findings that do not provide their own line range, while never replacing a non-empty plugin-provided range.
- Existing source, formatter, manager, and functional-test modules remain usable; do not replace the analyzer with a new standalone evaluator or disable checks.

You may inspect and modify the existing Bandit modules. Keep the solution offline and CPU-only. Your final deliverable is `/app/output.json`; do not include explanations in that file.