fix(prompts.ts): edited contradictory assistant output

[jonsguez]

When user wanted a one line commit the system prompt and the user/assistant one-shot example were contradicting each other, confusing the LLM. This fix modifies the assistant output so that prompt and one-shot are consistent.

see Issue #469

Before:

OCO_ONE_LINE_COMMIT=true OCO_DESCRIPTION=false oco

└  Generated commit message:
——————————————————
feat(algo_2.py): replace hardcoded debug_stop value with environment variable for better configurability 
feat(buffers.py): add BufferVal class to encapsulate value and timestamp for improved data handling

OCO_ONE_LINE_COMMIT=true OCO_DESCRIPTION=true oco

└  Generated commit message:
——————————————————
feat(algo_2.py): replace hardcoded debug_stop value with environment variable for flexibility
feat(buffers.py): add BufferVal class to encapsulate value and timestamp
Replacing the hardcoded value of debug_stop with an environment variable allows for greater flexibility in debugging scenarios. The addition of the BufferVal class provides a structured way to manage data values along with their timestamps, enhancing the overall data handling capabilities in the application.

After:

OCO_ONE_LINE_COMMIT=true OCO_DESCRIPTION=false oco

└  Generated commit message:
——————————————————
feat(algo_2.py, buffers.py): add environment variable support for debug stop and implement BufferVal class for enhanced data handling

OCO_ONE_LINE_COMMIT=true OCO_DESCRIPTION=true oco

└  Generated commit message:
——————————————————
feat(algo_2.py, buffers.py): add environment variable support for debug stop and implement BufferVal class for enhanced data handling
The changes introduce the ability to set the debug stop value via an environment variable, allowing for more flexible debugging configurations. Additionally, a new BufferVal class is added to encapsulate value and timestamp, improving data management within the DataProcessingBuffer.