test(portal): cover the onboarding password generator

[kingmakeruix]

What

Adds the missing test plumbing to synkronus-portal and focused, deterministic tests for generateStrongPassword — the handoff password an administrator creates when welcoming a new Formulus user.

• pnpm run test (vitest) wired up in synkronus-portal/package.json, using the same vitest version (^3.2.7) the monorepo already has in desktop and formulus-formplayer
• vitest config kept in vite.config.ts (rather than a new file), matching how formulus-formplayer does it
• pnpm run test added to the pre-flight list in synkronus-portal/AGENTS.md

Why

The generator guarantees a minimum length, one character per class, and the exclusion of look-alike characters (0, O, 1, l, I) — all of it was untested, so a change to the character sets would have been invisible. This is the onboarding path for every new Portal user.

Production randomness is untouched. Only the entropy source is stubbed (seeded xorshift32 over crypto.getRandomValues), so every assertion is reproducible and the suite cannot go flaky.

Testing

From synkronus-portal/:

pnpm run lint          # clean
pnpm run test          # 6 passed
pnpm run format:check  # clean
pnpm run build         # ok

Coverage of generateStrongPassword:

Case	Assertion
default	16 characters
minimum	4, 0, -5 all clamp up to 12
above minimum	24 and 64 are honoured
per class	always at least one uppercase, lowercase, digit, symbol
look-alikes	none of 0, O, 1, l, I in a 256 character password
determinism	same seed produces the same password

The look-alike test is a real guard, not a tautology: adding O to the UPPER set makes it fail, and reverting makes it pass again.

Scope is limited to this utility and its test setup, as the issue asks — no wider Portal test-suite migration.

Closes #908

[najuna-brian]

Hi @kingmakeruix
Thank you for the PR.

Please always comment on the issues and request them to be assigned to you before opening a PR 😊

Once they are assigned then we can go ahead and open a PR.

Thanks for the contribution again

[najuna-brian]

We also invite you to please join the Community Forum HERE
And introduce yourself and catchup with the rest of the activities

[kingmakeruix]

@najuna-brian Thanks for the correction — understood. I have commented on #908 requesting assignment, and I will ask for the issue to be assigned before opening a PR from now on instead of after.

I also went back to #912 for #947, so both are in the right order now, and I will not push further changes to either branch until the assignment is granted.

Thanks again, and thanks for the forum invitation — I will join and introduce myself.