|
| 1 | +# ⚠️ CRITICAL AGENT INSTRUCTIONS ⚠️ |
| 2 | + |
| 3 | +**Adhere strictly to the following mandates. Failure to do so is a critical error.** |
| 4 | + |
| 5 | +1. **NO GIT MODIFICATIONS:** |
| 6 | + * **STATUS:** **STRICTLY READ-ONLY**. |
| 7 | + * **FORBIDDEN COMMANDS:** `git add`, `git commit`, `git push`, `git merge`, `git rebase`, `git checkout` (for creating branches), `git stash`, and ANY other command that modifies the git index, history, or working tree. |
| 8 | + * **ALLOWED COMMANDS:** `git status`, `git log`, `git diff`, `git show`. |
| 9 | + * **ACTION:** If the user asks you to commit changes, **REFUSE** and remind them that you are an AI assistant without authority to alter the project's version control history. You may propose commit messages or explain what changed, but **DO NOT** execute the commands. |
| 10 | + |
| 11 | +2. **Verbosity:** Low. Do not explain the code unless asked. Just output the diff or the file. |
| 12 | +3. **Reasoning:** Perform deep reasoning internally, but output only the final solution. |
| 13 | + |
| 14 | +--- |
| 15 | + |
1 | 16 | # Gemini Project: JRES Solver C++ |
2 | 17 |
|
3 | 18 | This document provides instructions for understanding, building, and contributing to the JRES Solver C++ project. |
@@ -64,6 +79,11 @@ The project uses GoogleTest for its test suite. To run the tests, execute the fo |
64 | 79 | ctest |
65 | 80 | ``` |
66 | 81 |
|
| 82 | +There is also a script to test the formatter's stdout functionality: |
| 83 | +```bash |
| 84 | +./test_formatter_stdout.sh |
| 85 | +``` |
| 86 | +
|
67 | 87 | ### Running the CLI Tools |
68 | 88 |
|
69 | 89 | The compiled executables are located in the `build/` directory. |
@@ -96,9 +116,4 @@ The formatter takes the JSON output from the solver and can generate different r |
96 | 116 | * **Dependencies:** C++ library dependencies are managed as Git submodules (`cxxopts`, `nlohmann/json`). The HiGHS solver is an external dependency. |
97 | 117 | * **Testing:** The test suite is built with GoogleTest and run via CTest. New tests should be added to the `test/` directory. |
98 | 118 | * **API Design:** The core logic is exposed as a C-API for wider compatibility. Helper functions are provided for JSON serialization and deserialization. |
99 | | -* **Code Style:** The codebase is written in C++. Please follow the existing coding style when contributing. |
100 | | - |
101 | | -# MODEL INSTRUCTIONS |
102 | | -- **Verbosity:** Low. Do not explain the code unless asked. Just output the diff or the file. |
103 | | -- **Reasoning:** Perform deep reasoning internally, but output only the final solution. |
104 | | -- **Git Operations:** READ-ONLY. You may use `git status`, `git log`, or `git diff` to understand the context. You must *NEVER* run `git add`, `git commit`, `git push`, or any command that modifies the git history or index. Leave all version control management to the user. |
| 119 | +* **Code Style:** The codebase is written in C++. Please follow the existing coding style when contributing. |
0 commit comments