From c892a6d07a124b1bac44252cb8c954381a8b7b5e Mon Sep 17 00:00:00 2001 From: Frank Tovar Date: Sat, 11 Apr 2026 23:21:50 +0200 Subject: [PATCH] updated db and agents --- AGENTS.md | 10 +++++++++- src/RolemasterDb.App/rolemaster.db | Bin 4313088 -> 4313088 bytes 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 43aa18b..64d0ffc 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -16,14 +16,22 @@ These tool paths should be used instead of any entry in the PATH environment var - Keep changes as small as possible, design solutions that achieve the goals with minimal churn. - Always place each newly created class into its own file. The file name must match the class name. - When asked to begin working on a task, create a detailed implementation plan first, present the plan to the user, and ask for approval before beginning with the actual implementation. +- Don't make assumptions in the plan. If necessary, ask all clarifying questions before presenting the final plan. - When an task is finished, perform a code review to evaluate if the change is clean and maintainable with high software engineering standards. Iterate on the code and repeat the review process until satisfied. - After the implementation is finished, verify all changed files, and run `python D:\Code\crlf.py $file1 $file2 ...` only for files you recognize, in order to normalize all line endings of all touched files to CRLF. - If there's documnentation present, always keep it updated. +- After every iteration, evaluate if the test coverage would fall below 100%, and write tests if necessary. +- After every iteration, run `jb cleanupcode --build=False $file1;$file2;...` for every file you touched. +- After every frontend change, verify the results using an ephemeral playwright. ### Git - Never change the .gitignore file without consent. -- At the end perform a git commit with a one-liner summary. +- Keep changes small and commit often. If one iteration encompasses many smaller tasks with more than one commit, create a git branch and do the commits there. Let me review the branch before merging it back to master. +- When multiple commits are necessary, pause after every commit and ask the user to give a command to proceed. +- After every iteration, do a git commit with a brief summary of the changes as a commit message. +- If you find unexpected changes in the code (deletions, changes, diff results that were not communicated), never revert them and never restore the old state. Assume that those changes happened with intent. +- Never use `git restore`, `git checkout --`, reset commands, or equivalent rollback actions to discard local changes unless the user explicitly asks for that exact rollback. ### PowerShell diff --git a/src/RolemasterDb.App/rolemaster.db b/src/RolemasterDb.App/rolemaster.db index 74c035e8b666bc413098ed894d0799e146055992..8f6681ff7aaabf81e8ac981a8dd43fe31d3f4e04 100644 GIT binary patch delta 656 zcmWmBPe_w-7zgm*@Atm%_Bws{Zt8Tkt=6V4ZM|DsZ~wNrwJsYLLUc_G3<~NH7IiU4 z;A@Ad81lnbF;MbadH5M9ZD5dx=^;8L;$epl9Tt=rUHa~U4-a2>4$s3gUAEXXyz|Fs z?r|Vy1!5GK2*jki%kFqZpU5^+99dZ9>uG6=fBGO@;iKcyPSLS&fvZ`mlj-Yx=c05= z%w(l5yR6xW%_`?5kU@cFwu1^S;DA<9&bQqkVn)vLPPKt1yi?Af1!;pV&Dr(W3~f>W zBT7{F(dN_&)4>I9Xon8y1P^pUH+bOy90VWuApnQqFa+Ufy3C+rckf?}PL*G&wnJ1b=<{f@}QuY@M4a+_AsFrpUN*GHHxo4@bg-0A=lfU>y zH^rtr+(z3kjX%6T5xg_;U@|y)^Y(;c7(D)udidWPhF9#ihQn0EX!wU}$yykCpcnce z0!N`A2H+S(;W!u&gE*XkK^TIQaB4}`%w@SmKN7xMQ9Jpys@cT{D`t^Dt*ZUJQ87nF zs%n0>F>P1)zL=kt=9O-%UNhk|oPo1&PSk7XgLmneP|}HB${YhY>X|b2jIPW`P?f?E*)gu4^ delta 626 zcmWm5KWGzC0LSt7?p-c_n&gsR5>s=j_0AfrX)gWa`7dn~ ziGd6*P{0iy@PZF|M6KkXACrMUEMUSB7=)vc zf@3fQ$KeE|VHh%C!TvV_qc8^Ja8j^P^*HU))Uwt4q6k+}J9#{{u+^&0YWi