feat: update workflow documentation and add release process steps

AGENTS.md

@@ -217,18 +217,11 @@ $controller = new \admin\Controllers\ExampleController($repo);
 - AAA pattern: Arrange, Act, Assert
 - Tests mirror source structure: `tests/Unit/Domain/{Module}/{Class}Test.php`
 
-## Workflow (AGENTS.md)
+## Workflow
 
-When user says **"KONIEC PRACY"**, execute in order:
-1. Run tests
-2. Update documentation if needed: `docs/DATABASE_STRUCTURE.md`, `docs/PROJECT_STRUCTURE.md`, `docs/FORM_EDIT_SYSTEM.md`, `docs/CHANGELOG.md`, `docs/TESTING.md`
-3. SQL migrations (if DB changes): place in `migrations/{version}.sql` (e.g. `migrations/0.304.sql`). **NOT** in `updates/` — build script reads from `migrations/` automatically
-4. Commit
-5. Push
-6. Build update package: `git tag v0.XXX && powershell.exe -ExecutionPolicy Bypass -File build-update.ps1 -FromTag v0.PREV -ToTag v0.XXX -ChangelogEntry "opis"` — skrypt automatycznie aktualizuje `versions.php`
-7. Commit i push plików paczki (`updates/0.30/ver_0.XXX.zip`, `ver_0.XXX_manifest.json`, `updates/versions.php`, `updates/changelog-data.html`)
+When user says **"KONIEC PRACY"**, run `/koniec-pracy` (see `.claude/commands/koniec-pracy.md`).
 
-Before starting implementation, review current state of docs (see AGENTS.md for full list).
+Before starting implementation, review current state of docs.
 
 ## Key Documentation
 - `docs/MEMORY.md` — project memory: known issues, confirmed patterns, ORM pitfalls, caching conventions