99

Hello, When i run 99v, i get an empty response by the agent. Here's a video that showcases the issue: https://github.com/user-attachments/assets/33099c45-3012-4044-b46a-4e65867a3d14

1. Steps to reproduce 1. Windows 11 or Linux, Neovim 0.11.x, installed and logged in 2. 99 with and prompt delivery + workspace alignment working (#180-class prompt fix and #181-class / tmp path fix — required so the agent actually completes search and writes TEMP_FILE) 3. Setup: 4. Open a project with a known entrypoint (e.g. with ) 5. Run search (), prompt: 6. Agent completes (stdout often status-only or citation markdown) 7. Quickfix / Trouble stays empty on stock Note: Pure stock may be blocked earlier by #180 / #181. The parsing gap below is independent; it appears once the agent runs and returns results. 2. Relevant text / action taken Expected: Quickfix shows file locations from the search. Actual: Agent finds the code but 99 does not populate . Common cases: Status-only stdout: agent writes qfix lines to TEMP_FILE but 99 reads conversational stdout or status text instead of parseable locations Citation markdown**: agent returns `startLine:endLine:pathQFixHelpers.create_qfix_entries"qf_list":[]--workspaceqf_list--workspacenormalize_qfix_response_retrieve_responseqf_listqf_list"C"CursorAgentProvider:_retrieve_responsesearchvibenormalize_qfix_responsevisualtutorial`: return raw text (no normalization).

Fixes crashes when marks are used before validation during visual selection operations. Problem The current code creates marks and immediately uses them for logging and RequestStatus before validating they were created successfully. When the buffer is modified between range calculation and mark creation, the marks fail to create but are still used, causing crashes. Current flow: 1. Create marks (may fail silently) 2. Use marks for logging - crashes if invalid 3. Pass marks to RequestStatus - crashes if invalid 4. Start status updates - crashes if invalid 5. Much later, in async callback, validate marks (too late) Solution Validate marks immediately after creation, before using them. This fails fast with a clear error message instead of crashing later with cryptic errors. New flow: 1. Create marks 2. Validate marks immediately 3. If invalid, log fatal error and return early 4. If valid, proceed safely knowing marks are good Benefits Fails fast with clear error message No defensive nil checks needed throughout codebase Single validation point instead of scattered checks Prevents crashes in logging, RequestStatus, and status updates Better user experience with actionable error message Testing All existing tests pass (68/68) Linting passes Formatting passes Follows existing error handling patterns in the codebase