[ddehilster]

What

A Text pane to the right of the editor shows the input file the next run reads. The text can be edited there, and a pulldown above it lists every input file, grouped by folder (input/tune/..., input/test2/...).

• The pane uses the same Monaco model as the input file. An edit in the pane is also an edit to the file, so it's kept as a draft, reverted and downloaded as before.
• Choosing a text sets what Run reads, and the "on " note next to Run follows it. Opening an input file from the sidebar updates the pulldown too.
• A Text button in the header shows or hides the pane, and the browser remembers the choice. The button is hidden when the analyzer has no input files.
• F5 runs from the pane as well as from the editor.
• On narrow screens the pane stacks below the editor.

Why

Analyzers with many test texts were hard to run on a chosen text. The texts were at the bottom of a long sidebar, and opening one replaced the code in the editor. The Med Coder (conceptual-systems/medical-coder) serves this studio with its analyzers and its clinical texts as input files, and needs to choose a text, read it next to the passes and run it.

Testing

• tsc --noEmit passes, and npm test passes (52 tests).
• Headless Chromium against the Med Coder's run server:
  • ClinicalNotes listed its own test folders and the Med Coder texts in the pulldown.
  • Choosing a text showed it in the pane, and Run ran on it (Output: 9 files).
  • ExtractICDCodes behaved the same way.

🤖 Generated with Claude Code