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 offline security scan pipeline

You are given a vendored Bandit source tree under `/app/vendor/pycqa-bandit` and
an offline fixture set under `/app/workload/fixtures`. Repair the existing source
so the normal file-level Trojan Source check can be used by an integration
caller, then produce `/app/output.json` by running the supplied scan entrypoint.
Do not replace the scanner with a new standalone evaluator.

The producer must preserve the scanner's security semantics:

- bidirectional Unicode controls are reported as B613 with HIGH severity and
  MEDIUM confidence;
- the finding location is 1-based and points to the physical source line and
  character column containing the control character;
- file-level plugins may provide their own non-empty `linerange`; generic tester
  enrichment must not erase it, while issues without a custom range still get
  the framework context range;
- filename and original file bytes remain attached to each issue, and the
  non-UTF-8 fixture must be decoded according to its Python encoding declaration;
- clean files must remain clean.

Use the existing modules and integration path. The output contract is documented
in `/app/CONTRACT.md`; its schema version must be exactly
`bandit_trojan_repair.v1`. Include every `*.py` fixture in lexical filename order,
including clean files, and use the supplied `/app/run_scan.py` after repairing
the source. Keep the workspace offline and do not add dependencies.