feat: Add a note to save changes before starting

[JPeer264]

During the release I figured that most of the times you might work on features/bugfixes. In that case the current release process this scenario isn't specified and who knows what it might or might not do.

I added point 1. and 9. where we ask Cursor to save the changes (1) and go back to the state it was before (9). This would make the release process more complete.

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,284	-	8,869	+5%
GET With Sentry	1,435	15%	1,384	+4%
GET With Sentry (error only)	6,306	68%	6,192	+2%
POST Baseline	1,212	-	1,177	+3%
POST With Sentry	552	46%	529	+4%
POST With Sentry (error only)	1,082	89%	1,060	+2%
MYSQL Baseline	3,375	-	3,381	-0%
MYSQL With Sentry	506	15%	493	+3%
MYSQL With Sentry (error only)	2,770	82%	2,725	+2%

View base workflow run