docs: update feature workflow rule to emphasize staging and pushing changes

Author: StuMason

.cursor/rules/801-feature-workflow.mdc

@@ -1,7 +1,6 @@
 ---
 description: FOLLOW feature development workflow WHEN implementing new features TO ensure consistent, tested, and documented changes
-globs: src/**/*.{ts,tsx}
-alwaysApply: true
+globs: src/**/*
 ---
 
 # Feature Development Workflow
@@ -17,7 +16,8 @@ alwaysApply: true
 - Locate and review feature documentation in docs/features directory
 - Follow documentation requirements systematically
 - IMPORTANT Commit frequently to trigger pre-commit hooks (linting, formatting, tests)
-- Push to remote remotr
+- CRITICAL Always stage ALL modified files after making changes
+- CRITICAL Always push changes to remote after committing
 - Add comprehensive tests for new functionality
 - Push completed work to remote for PR review
 
@@ -29,28 +29,36 @@ alwaysApply: true
 3. Review docs/features/002-server-info-resource.md
 4. Implement ServerInfo interface
 5. Add getServerInfo method with tests
-6. Commit to run hooks: "feat: add server info interface"
-7. Implement ServerStatus interface
-8. Add getServerStatus method with tests
-9. Commit to run hooks: "feat: add server status resource"
-10. Fix any linting issues
-11. Push to remote when complete
+6. git add . # Stage ALL changes
+7. Commit to run hooks: "feat: add server info interface"
+8. git push origin feature/server-info # Push changes immediately
+9. Implement ServerStatus interface
+10. Add getServerStatus method with tests
+11. git add . # Stage ALL changes again
+12. Commit to run hooks: "feat: add server status resource"
+13. git push origin feature/server-info # Push changes again
+14. Fix any linting issues
+15. git add . && git commit -m "fix: linting issues"
+16. git push origin feature/server-info
 </example>
 
 <example type="invalid">
 # Poor workflow
 1. Start coding without checking docs
 2. Make all changes in one big commit
 3. Skip tests or add them later
-4. Push directly to main
-5. Fix linting issues after PR
+4. Leave changes unstaged
+5. Forget to push changes to remote
+6. Push directly to main
+7. Fix linting issues after PR
 </example>
 
 ## Critical Points
 <critical>
 - ALWAYS work from feature documentation
-- 
 - NEVER skip tests for new functionality
 - Commit OFTEN to utilize pre-commit hooks
+- ALWAYS stage ALL modified files after making changes
+- ALWAYS push changes to remote after committing
 - Keep commits focused and well-described
 </critical>