aisman

Session 11, Step 1: Per-file/issue error reporting with JSON repair and error UI:

Server changes (WorkflowController.cs):
- Added FileProcessResult and IssueProcessError DTOs for granular error reporting
- Implemented TryRepairJsonEscaping state-machine to fix badly-escaped JSON strings
- ProcessOutputBatch now returns per-file and per-issue error details, with retry logic
- ProcessOutputCore accepts optional issueErrors list for try/catch per issue

Client changes (dashboard.js):
- processOutputFiles: Handles result.files map, moves successful files to processed/, writes step.errors back to disk for error files
- checkForNewOutputs: Detects step.errors and sets hasErrors flag; auto-corrects ds_* files with positive session.num
- renderNewOutputsList: Red rows for files with errors, warning icon indicator
- openOutputOverlay: Extracts and displays error panel with per-issue error messages

Styling (dashboard.scss):
- Added aim-output-row-error class for failed file rows
- Added aim-output-error-panel, -hdr, -list, -icon styles for error display

Documentation & bookkeeping:
- Updated .aisman/instructions.md with explicit session.num numbering rules (negative for direct sessions)
- Fixed session numbers in ds_000_007-01/02/03 and ds_000_008/009/010/011 files
- Updated catalog.json: lastDsSessionNum 11, lastIssueNum 268, issues -262 to -268

Issues completed: -262 to -268