follow the instructions in c:\Users\micha\workspace\dig_network\dig-slashing\docs\prompt\start.md, besure to trace through all links in the file and follow the decision tree to understand how to complete this task. Then pick the next uncomplete requirement in c:\Users\micha\workspace\dig_network\dig-slashing\docs\requirements\IMPLEMENTATION_ORDER.md (a `DSL-NNN` id) and implement it in a TDD workflow. Do not forget to utilize gitnexus, repomix, socraticode before adding or modifying anything to the code base. Do not forget to commit and push the changes as you complete each requirement. Each requirement MUST have its own dedicated test file named `tests/dsl_NNN_<short_name>_test.rs` per ยง22 of docs/resources/SPEC.md. All tests must have comprehensive comments describing what they test and how they prove the requirement is satisfied. All written code must have comprehensive high signal, llm friendly comments that describe usage, rationale, decisions, and other contextual information, and it should include semantic links to SPEC.md sections and to other code where appropriate. Load the repomix file into context before any changes.
Scope reminder: dig-slashing is validator slashing only (ProposerEquivocation, InvalidBlock, AttesterDoubleVote, AttesterSurroundVote) plus Ethereum-parity participation rewards/penalties plus continuous inactivity accounting plus optimistic-slashing fraud-proof appeals. DFSP / storage-provider slashing is out of scope.