docs: add mandatory git workflow to instructions

- Added 'When Making Changes' item #12: Git commit and push
- Make git workflow mandatory after ANY feature/fix/change
- User should not have to ask - it's part of completion
- Include commit message format and types (feat/fix/docs/refactor)
- Emphasize: code only exists when committed and pushed
- Update trade count: 161 -> 168 (as of Nov 14, 2025)
This commit is contained in:
mindesbunister
2025-11-14 05:39:01 +01:00
parent 6590f4fb1e
commit 5c0412bcf2

View File

@@ -1271,11 +1271,28 @@ if (!enabled) {
- Restart container and verify new code is running
- Never say "fixed" or "protected" without deployment confirmation
- This is a REAL MONEY system - unverified fixes cause losses
12. **GIT COMMIT AND PUSH (MANDATORY):** After completing ANY feature, fix, or significant change:
- ALWAYS commit changes with descriptive message
- ALWAYS push to remote repository
- User should NOT have to ask for this - it's part of completion
- Commit message format:
```bash
git add -A
git commit -m "type: brief description
- Bullet point details
- Files changed
- Why the change was needed
"
git push
```
- Types: `feat:` (feature), `fix:` (bug fix), `docs:` (documentation), `refactor:` (code restructure)
- This is NOT optional - code exists only when committed and pushed
## Development Roadmap
**Current Status (Nov 12, 2025):**
- **161 trades executed** with quality scores and MAE/MFE tracking
**Current Status (Nov 14, 2025):**
- **168 trades executed** with quality scores and MAE/MFE tracking
- **Capital:** $97.55 USDC at 100% health (zero debt, all USDC collateral)
- **Leverage:** 15x SOL (reduced from 20x for safer liquidation cushion)
- **Three active optimization initiatives** in data collection phase: