case 4754 - licence text: forum registration sentences removed

The AyaNova support forum is being retired, and public registration had been
closed for years. Removes "register on our AyaNova Support Forum" from the
"Data obtained" and "Use and Sharing of Data" sections and the forum data
deletion clause (iv); the purchase information clause becomes (iv).

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

CLAUDE.md

@@ -60,6 +60,7 @@ The rest of the modernization plan: `devdocs/modernization/ROADMAP.md`.
 - Dependency changes: back-end packages only, and only with John's approval (the port that updated them all is done). No front-end dependency changes (Node is pinned at 12.22.9 because of `fibers`).
 - Do not add `[ApiController]` to controllers that lack it. It changes model binding and error responses on routes deployed clients call.
 - No new features.
+- Low-level server fixes (`util`, `generator`, `ControllerHelpers`, `DataList`, startup): check whether Sockeye needs the same fix with `..\sockeye\devdocs\compare-with-raven.sh` (names mapped in `NAME-MAP.md` there), and record the answer.
 - Git: keep it simple and explicit. Do not push, tag, merge or rewrite history unless asked. Tags are annotated and pushed by name.
 - Nothing is accepted blindly: show the diff and say why.
 - Secrets and customer data never go in a repo. Fixtures that contain customer data live outside the repo and are found through an environment variable.

devdocs/build/RELEASE-PROCEDURE.md

@@ -19,15 +19,15 @@ bash on a droplet or the ayanova.com web server (logged in as root).
 5. Test on devtest: upgrade it from `next`, remote E2E, check each change
 6. Tag the release in git
 7. Publish: docs and downloads go live (not announced yet)
-8. **Upgrade the subscription droplets** (Thursday, by time zone)
+8. Download every published file back and check its version
-9. **Announce**: upload `latest-version.json`
+9. **Upgrade the subscription droplets** (Thursday, by time zone)
-10. Download every published file back and check its version
+10. **Announce**: upload `latest-version.json`
 11. Tell subscription customers
 12. Start the next version
 
 **Subscription droplets are upgraded before the release is announced** (John, 2026-10-26, from
 8.3.0 on). Uploading `latest-version.json` is what tells every AyaNova installation that a new
-version exists, so it is the very last publishing step. Between steps 7 and 9 the new docs and
+version exists, so it is the very last publishing step. Between steps 7 and 10 the new docs and
 downloads are already visible on the website; that gap is accepted.
 
 ## 1. Code complete
@@ -148,53 +148,53 @@ next patch version (8.3.1) with its own tag. To see later what any release conta
 
 ## 7. Publish (not announced yet)
 
-On the ayanova.com web server. In the archive folder name (`YYYY-MM-DD-vX.Y.Z`), replace the
+The download folders on the ayanova.com web server:
-example date and version with the real release date and version:
 
-```bash
+- `download/` always holds the current release, plus files that are not part of a release (for
-rm -r /var/www/html/ayanova.com/docs/* && cp -r /var/www/html/ayanova.com/docs-next/* /var/www/html/ayanova.com/docs
+  example `QBFC14_0installer.exe`), which stay.
-```
+- `download/next/` is staging: the release as built and tested in steps 4 and 5.
+- `download/old/` archives the three most recent releases, including the current one, each in a
+  folder named for its release date and version. The current release is therefore in both
+  `download/` and `download/old/`, on purpose.
 
-```bash
+On the ayanova.com web server, in this order:
-mkdir /var/www/html/ayanova.com/download/old/2026-11-05-v8.3.0 && cp -r /var/www/html/ayanova.com/download/next/* /var/www/html/ayanova.com/download/old/2026-11-05-v8.3.0
-```
 
-Remove the oldest release folder in `download/old`: only the three most recent releases are kept
+1. Replace the manual with the new one:
-(since December 2023; customers whose maintenance lapsed must purchase to upgrade, and the older
-versions are kept only to diagnose a regression). List the folder, then remove the oldest; at
-8.3.0 that is 8.2.2:
 
-```bash
+   ```bash
-ls /var/www/html/ayanova.com/download/old
+   rm -r /var/www/html/ayanova.com/docs/* && cp -r /var/www/html/ayanova.com/docs-next/* /var/www/html/ayanova.com/docs
-```
+   ```
 
-```bash
+2. Replace this release's files in `download/` with the tested ones from `next/`. Only the files
-rm -r /var/www/html/ayanova.com/download/old/2024-10-23-v8.2.2
+   in `next/` are overwritten; everything else in `download/` stays. The same command keeps a copy
-```
+   of the current `latest-version.json` (it is not in `next/` and is replaced only in step 10):
 
-```bash
+   ```bash
-cp /var/www/html/ayanova.com/download/next/* /var/www/html/ayanova.com/download && cp /var/www/html/ayanova.com/download/latest-version.json /var/www/html/ayanova.com/download/previous-latest-version.json
+   cp /var/www/html/ayanova.com/download/next/* /var/www/html/ayanova.com/download && cp /var/www/html/ayanova.com/download/latest-version.json /var/www/html/ayanova.com/download/previous-latest-version.json
-```
+   ```
+
+3. Archive the release in `download/old/`, in a folder named `YYYY-MM-DD-vX.Y.Z` with the release
+   date and version (for 8.3.0, released 2026-10-29):
+
+   ```bash
+   mkdir /var/www/html/ayanova.com/download/old/2026-10-29-v8.3.0 && cp /var/www/html/ayanova.com/download/next/* /var/www/html/ayanova.com/download/old/2026-10-29-v8.3.0
+   ```
+
+4. Remove the oldest release folder in `download/old`, so three remain (kept since December 2023;
+   customers whose maintenance lapsed must purchase to upgrade, and the older versions are kept
+   only to diagnose a regression). List the folder, then remove the oldest; at 8.3.0 that is 8.2.2:
+
+   ```bash
+   ls /var/www/html/ayanova.com/download/old
+   ```
+
+   ```bash
+   rm -r /var/www/html/ayanova.com/download/old/2024-10-23-v8.2.2
+   ```
 
 Do **not** upload the new `latest-version.json` yet.
 
-## 8. Upgrade the subscription droplets
+## 8. Check what was published
-
-On the normal Thursday schedule and times (or out of band for an emergency), as in the
-[weekly update](#weekly-os-update): snapshot, health check, OS update, reboot; then any
-one-time steps for this release, then the [release upgrade commands](#upgrade-commands); then the
-health check and the log entry. Mark each server as upgraded in its Sockeye subscription server record.
-
-## 9. Announce
-
-Only after the last subscription droplet is upgraded, from PowerShell on the workstation (overwrites
-the old one; from this moment every AyaNova installation shows that the new version is available):
-
-```powershell
-scp C:\data\code\raven\dist\latest-version.json root@ayanova.com:/var/www/html/ayanova.com/download/
-```
-
-## 10. Check what was published
 
 Download every installer and package back from ayanova.com and check its version: Windows
 installers by the .exe's ProductVersion, Linux zips by the `AyaNova.dll` inside. (Found
@@ -204,7 +204,24 @@ installers by the .exe's ProductVersion, Linux zips by the `AyaNova.dll` inside.
 $ProgressPreference = 'SilentlyContinue'; $d = "$env:TEMP\ayanova-published"; Remove-Item $d -Recurse -Force -ErrorAction SilentlyContinue; New-Item -ItemType Directory $d | Out-Null; foreach ($f in 'ayanova-windows-x64-single-setup.exe','ayanova-windows-x64-lan-setup.exe','ayanova-linux-x64-server.zip','ayanova-linux-x64-desktop.zip','ayanova-subscription-linux-x64-server.zip') { Invoke-WebRequest "https://www.ayanova.com/download/$f" -OutFile "$d\$f" -UseBasicParsing; if ($f -like '*.exe') { "$f  $((Get-Item "$d\$f").VersionInfo.ProductVersion)" } else { Expand-Archive "$d\$f" "$d\$($f -replace '\.zip$','')" ; "$f  $((Get-Item "$d\$($f -replace '\.zip$','')\AyaNova.dll").VersionInfo.ProductVersion)" } }
 ```
 
-Every line must show the new version.
+Every line must show the new version. If one does not, fix the download folder (step 7) and check
+again; no subscription droplet is upgraded and nothing is announced until every line is right.
+
+## 9. Upgrade the subscription droplets
+
+On the normal Thursday schedule and times (or out of band for an emergency), as in the
+[weekly update](#weekly-os-update): snapshot, health check, OS update, reboot; then any
+one-time steps for this release, then the [release upgrade commands](#upgrade-commands); then the
+health check and the log entry. Mark each server as upgraded in its Sockeye subscription server record.
+
+## 10. Announce
+
+Only after the last subscription droplet is upgraded, from PowerShell on the workstation (overwrites
+the old one; from this moment every AyaNova installation shows that the new version is available):
+
+```powershell
+scp C:\data\code\raven\dist\latest-version.json root@ayanova.com:/var/www/html/ayanova.com/download/
+```
 
 ## 11. Tell subscription customers
 

devdocs/modernization/NET10-PORT.md

@@ -277,6 +277,7 @@ Found during the port, out of scope. One line each.
 - **Done in case 4703.** **Improvement, own case after the port (John to create):** bring back logging of JavaScript error details from report page console errors, as Sockeye's port did. AyaNova logs only `ERROR: {message text}`; the per-argument detail (`arg instanceof Error ? arg.message : arg`) is commented out at `biz/ReportBiz.cs:873-876` since case 4586, because `IJSHandle.ExecutionContext` was removed. Sockeye 8.1.0 (`server/biz/ReportBiz.cs:575`) evaluates on the handle instead: `args.Message.Args.Select(arg => arg.EvaluateFunctionAsync("(arg) => arg instanceof Error ? arg.message : arg"))`, which also needs the console handler to be `async` again
 - Pre-existing, same in 8.2.4 (found in the 4579 sandbox test, John: Deferred): rendering a report for a record that does not exist (e.g. work order ids 1 and 2 in a trial without sample data) fails the job with a generic `ArgumentNullException` ("Value cannot be null. (Parameter 'o')") from `JObject.FromObject` in `WorkOrderBiz.GetReportData` (`WorkOrderBiz.cs:1030`), instead of skipping the missing record or saying it is not found. Other object types' `GetReportData` likely do the same
 - **Roles audit, case 4735 (John, 2026-10-25, this release; found in 4719):** check every object's rights as documented in the manual (each page's "Authorization Roles required" section and `ay-biz-admin-roles.md`) against `biz/BizRoles.cs`. Report templates were changeable by Business administration - restricted although the roles page uses exactly that case as its example of a view-only restricted role (fixed in 4719). If that slipped through there could be others; for each mismatch decide whether the code or the page is wrong
+- Found 2026-10-27 (John: later case, no BC customers): when the browser cannot name its time zone, the client uses `America/New_York` (`raven-client` `api/locale.js` `getResolvedTimeZoneName`; Sockeye's client the same), so every date and time is shown, entered and sent to reports in New York time. Windows' new "British Columbia Standard Time" zone (BC permanent UTC−7 from November 2026) does this: Chrome returns `undefined` for it, although it knows `America/Vancouver`'s new rules. Seen on John's PC as backup times three hours late on devtest and Sockeye (the servers were right). Workaround: the time zone override in user settings. Fix: fall back to the browser's current UTC offset (fixed-offset zone) instead of New York
 - Found in the 8.3.0 Cypress runs (2026-10-26; pre-existing, 8.2.4 too): on a first visit over a slow connection the login page can move the keyboard focus back to the username field while it settles (the field has `v-focus` and is re-inserted when the page redraws), so part of a password typed early lands in the username field in plain view; and the service worker reloads the page once when it takes control (`App.vue`, `controllerchange`), clearing both fields. Both within the first seconds of a first visit
 - From case 4697 (John: Deferred): (1) a relative date range that crosses a daylight saving change can be an hour off at its far end, because the client sends only its current offset with list requests; exact would need the client to send its IANA time zone name too (front-end change). (2) Dashboard widgets group by day, week or month with `date_trunc` on the stored UTC times, so for a user far from UTC an item near midnight lands in the neighbouring bar; same need for the time zone name
 - From case 4727 (John: later hardening case, 2026-10-26): AyaNova runs as `www-data` on droplets and in the Linux manual (as in Microsoft's ASP.NET Core with NGINX guide), the same account as NGINX's workers, so NGINX can read `config.json` (database password) and write `data`. A dedicated `ayanova` system account isolates them: service `User=`, ownership, the setup script and the manual, plus a migration for existing droplets and self-hosted installs
@@ -325,3 +326,4 @@ Found during the port, out of scope. One line each.
 | 2026-10-23 | Checklist tidy-up: older unticked items in sections 0–5 checked against current evidence | `main` = `origin/main` = `net8-baseline` in `raven` and `raven-client`; tag on both remotes. Licence gate 730/730 at `181b1e44`. No EF Core warning raised as an error in any log (local dev server, Sandbox, `devtestn10`). `System.Text.Json` 5.0.2 gone from the graph. JwtBearer 10.0.13 done. Report and E2E baselines marked waived (John); Cypress stays open in section 4 and now also covers the UI side of the EF Core screen-by-screen item. Restore manual compared: fine for the default `postgres` setup; dedicated-role note added to Deferred. Stale "still to do" remarks removed. Still open: relative date tokens (section 3, decision needed), Cypress, and the section 5 release steps |
 | 2026-10-23 | `net10-port` merged into `main` (`--no-ff`, no tag) in `raven`, `raven-client`, `raven-launcher`, `raven-test-integration` (John) | Pre-checks: all clean and pushed; `main` = `origin/main` with no commits outside `net10-port`. Post-checks: `git diff net10-port main` empty in all four; pushed. `CLAUDE.md` "Current work" now describes the 8.3.0 release on `main`; stack table updated to .NET 10; dependency rule no longer refers to the port branch. `net10-port` branches kept until after release (section 5) |
 | 2026-10-26 | Final gate, release candidate build, Cypress | See section 5. Performance, same suite and browser, devtest (8.2.4) and `devtestn10` (8.3.0), same droplet size and region (San Francisco): generating the test data 1:43 on 8.2.4, 0:42 and 0:45 on 8.3.0 (about 2.4 times faster; mostly server work); the 21 UI specs that passed in both, 224 s and 200 s (about 10% faster; much of a UI test is Cypress itself). `build-release.bat` failed twice at the subscription zip while an Explorer or PowerShell window was open on `dist\installers` (folder in use); clean once closed |
+| 2026-10-26 | Final build, staging, devtest (RELEASE-PROCEDURE.md steps 3 to 5) | Final build from `05cf4df6` (changelog and manual date only since the release candidate): all five packages 8.3.0, runtime 10.0.14. Staged in `download/next` and `docs-next` on ayanova.com (new droplet `ayanova-2`; its host key changed with the cutover, fingerprint confirmed): SHA-256 of all five files match the build, 665 docs files. Found: the live `latest-version.json` still announces 8.2.3, so installations were never told about 8.2.4; the 8.3.0 announcement covers it. devtest (snapshot first): OS update, .NET 10.0.13, `harden-830.sh` taken from the procedure, the procedure's next-version upgrade command as written, reboot: 8.3.0 boots, schema 20, trial kept, 127.0.0.1 only, program folder read only, `config.json` 640 (was 644), nothing blocked. Cypress on devtest 27/27. Tagged `8.3.0` in `raven` (`05cf4df6`), `raven-client`, `raven-launcher`; publishing, droplet upgrades and the announcement follow on Thursday 2026-10-29 (John) |

dist/assets/LICENSE

@@ -51,7 +51,7 @@ Ground Zero will comply with all applicable laws pertaining to personal data inc
 
 A: Data obtained
 
-Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form) or when you register on our AyaNova Support Forum.
+Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form).
 
 Information you provided in your order (such as your company name, company contact information, contact name, along with the AyaNova products/services/subscriptions purchased) is sent to us from our payment processing partner with whom you placed your order.
 
@@ -61,7 +61,7 @@ Ground Zero will not share your information for marketing purposes with companie
 
 C: Use and Sharing of Data
 
-Personal data you provided when you contact us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form or register on our AyaNova Support Forum) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.
+Personal data you provided when you contact us (such as when you email us directly, email us via our online form, or email us via our online temporary Key request form) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.
 
 Ground Zero will also receive your company information you provided to our payment processing partner, so that we may process your product/service/subscription order.
 
@@ -83,8 +83,7 @@ E: Deleting of Data
 (i) Temporary key requests without subsequent purchase will be deleted within one year.
 (ii) Email correspondence without subsequent purchase will be deleted within two years except where required for maintaining case and support history.
 (iii) Email correspondence including temporary key requests with subsequent subscription purchase will be retained for the life of your subscription. Once a subscription has been allowed to lapse (not renewed), correspondence will be deleted within two years except where required for maintaining case and support history. 
-(iv) Customer information obtained through AyaNova Support Forum registration will be deleted within three years of forum login inactivity. 
+(iv) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. 
-(v) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. 
 
 
 I HAVE READ AND UNDERSTOOD ALL OF THE ABOVE TERMS AND CONDITIONS AND ACKNOWLEDGE THAT THESE TERMS AND CONDITIONS FORM PART OF THIS AGREEMENT.  I AGREE THAT A PRINT-OUT OF THIS AGREEMENT WILL CONSTITUTE A "WRITING" UNDER ANY APPLICABLE LAWS.

dist/assets/license.rtf

@@ -54,7 +54,7 @@ Ground Zero will comply with all applicable laws pertaining to personal data inc
 \f0\fs20\par
 A: Data obtained\f1\fs24\par
 \f0\fs20\par
-Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form) or when you register on our AyaNova Support Forum.\f1\fs24\par
+Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form).\f1\fs24\par
 \f0\fs20\par
 Information you provided in your order (such as your company name, company contact information, contact name, along with the AyaNova products/services/subscriptions purchased) is sent to us from our payment processing partner with whom you placed your order.\f1\fs24\par
 \f0\fs20\par
@@ -64,7 +64,7 @@ Ground Zero will not share your information for marketing purposes with companie
 \f0\fs20\par
 C: Use and Sharing of Data\f1\fs24\par
 \f0\fs20\par
-Personal data you provided when you contact us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form or register on our AyaNova Support Forum) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.\f1\fs24\par
+Personal data you provided when you contact us (such as when you email us directly, email us via our online form, or email us via our online temporary Key request form) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.\f1\fs24\par
 \f0\fs20\par
 Ground Zero will also receive your company information you provided to our payment processing partner, so that we may process your product/service/subscription order.\f1\fs24\par
 \f0\fs20\par
@@ -86,8 +86,7 @@ E: Deleting of Data \f1\fs24\par
 (i) Temporary key requests without subsequent purchase will be deleted within one year.\f1\fs24\par
 \f0\fs20 (ii) Email correspondence without subsequent purchase will be deleted within two years except where required for maintaining case and support history.\f1\fs24\par
 \f0\fs20 (iii) Email correspondence including temporary key requests with subsequent subscription purchase will be retained for the life of your subscription. Once a subscription has been allowed to lapse (not renewed), correspondence will be deleted within two years except where required for maintaining case and support history. \f1\fs24\par
-\f0\fs20 (iv) Customer information obtained through AyaNova Support Forum registration will be deleted within three years of forum login inactivity. \f1\fs24\par
+\f0\fs20 (iv) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. \f1\fs24\par
-\f0\fs20 (v) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. \f1\fs24\par
 \f0\fs20\par
 \par
 I HAVE READ AND UNDERSTOOD ALL OF THE ABOVE TERMS AND CONDITIONS AND ACKNOWLEDGE THAT THESE TERMS AND CONDITIONS FORM PART OF THIS AGREEMENT.  I AGREE THAT A PRINT-OUT OF THIS AGREEMENT WILL CONSTITUTE A "WRITING" UNDER ANY APPLICABLE LAWS.\f1\fs24\par

docs/8.0/ayanova/docs/license.md

@@ -51,7 +51,7 @@ Ground Zero will comply with all applicable laws pertaining to personal data inc
 
 A: Data obtained
 
-Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form) or when you register on our AyaNova Support Forum.
+Information about you (such as your email address, name, company information) is provided to us when you email us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form).
 
 Information you provided in your order (such as your company name, company contact information, contact name, along with the AyaNova products/services/subscriptions purchased) is sent to us from our payment processing partner with whom you placed your order.
 
@@ -61,7 +61,7 @@ Ground Zero will not share your information for marketing purposes with companie
 
 C: Use and Sharing of Data
 
-Personal data you provided when you contact us (such as when you email us directly, email us via our online form, email us via our online temporary Key request form or register on our AyaNova Support Forum) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.
+Personal data you provided when you contact us (such as when you email us directly, email us via our online form, or email us via our online temporary Key request form) will be used to provide technical support, to respond to user inquiries, to provide temporary Key(s), to maintain case and bug issues reported by you, and to send you relevant AyaNova information.
 
 Ground Zero will also receive your company information you provided to our payment processing partner, so that we may process your product/service/subscription order.
 
@@ -83,8 +83,7 @@ E: Deleting of Data
 (i) Temporary key requests without subsequent purchase will be deleted within one year.
 (ii) Email correspondence without subsequent purchase will be deleted within two years except where required for maintaining case and support history.
 (iii) Email correspondence including temporary key requests with subsequent subscription purchase will be retained for the life of your subscription. Once a subscription has been allowed to lapse (not renewed), correspondence will be deleted within two years except where required for maintaining case and support history. 
-(iv) Customer information obtained through AyaNova Support Forum registration will be deleted within three years of forum login inactivity. 
+(iv) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. 
-(v) Purchase information along with company information as provided by our payment processing partner will be retained for a minimum of six years after the end of the taxation year to which they relate as per the Canada Revenue Agency and no longer than 10 years after which will be deleted within one year. 
 
 
 I HAVE READ AND UNDERSTOOD ALL OF THE ABOVE TERMS AND CONDITIONS AND ACKNOWLEDGE THAT THESE TERMS AND CONDITIONS FORM PART OF THIS AGREEMENT.  I AGREE THAT A PRINT-OUT OF THIS AGREEMENT WILL CONSTITUTE A "WRITING" UNDER ANY APPLICABLE LAWS.