case 4630 - release procedure: client copyright year is automatic

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

devdocs/build/RELEASE-PROCEDURE.md

@@ -13,7 +13,7 @@ bash on a droplet or the ayanova.com web server (logged in as root).
 ## Release order at a glance
 
 1. Code complete: every case committed and pushed, local E2E passes
-2. Docs: changelog, manual copyright date
+2. Docs: changelog (manual and client copyright years are automatic)
 3. Build with `build-release.bat`
 4. Stage the installers and docs in the `next` folders on ayanova.com
 5. Test on devtest: upgrade it from `next`, remote E2E, check each change
@@ -54,6 +54,8 @@ cd C:\data\code\raven-test\e2e; .\local-run.bat
 - Manual revision stamp and copyright year: set automatically when the manuals are built
   (`docs/8.0/rev_date.py`, the date of the last commit that changed each manual). After the build,
   check the bottom of a page in `server/AyaNova/wwwroot/docs`: `REV-` must be that date.
+- Copyright year on the login page: set automatically when the client is built (`raven-client`
+  `ayanova/vue.config.js`, the year of the build).
 - `dist/latest-version.json`: the new version and its changelog anchor (for example `#ayanova-830`). Set at the version bump; check it here.
 
 ## 3. Build