- Ya
- 29 Agosti 2026, 06:35 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 0badc15
The launchpad button never appeared, and neither did any progress: the Java controller existed, the client existed, and the Next route between them was never written. Every call to /api/security/org-setup-wizard 404'd before it left the browser's own origin. org_setup_wizard_progress is empty in production — not one step has ever been recorded since this shipped. Nothing said so, and that is the part worth noting. Both callers swallow a failed read on purpose: the launchpad button renders nothing until progress is known, so an owner does not watch it flash on and off on every page load, and the wizard treats its progress as an aid rather than a gate. Two deliberate silences met and the feature simply never appeared. A missing route is invisible to tsc, to vitest and to `npm run build` — there is no import to fail, because the contract is a string. So the test that comes with this reads the client's BASE, asserts a handler exists for it, and asserts it exports every verb the client uses. It fails if the file is removed; I checked that rather than assuming it.