📝 docs: account lifecycle endpoints + refreshtoken warning #126
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/account-lifecycle"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Document the account-lifecycle group under
## Usersinsites-and-users.md(roadmap §2.4, issue #70):Closes #70.
Evidence
Live probe 2026-10-11 (END_USER session, reads only):
GET /api/users/{id}/refreshtoken→412, bare arrayuser.already.activated— confirms the canonical conventions example verbatim.GET /api/users/{email}/isReadyForSiteInstallation→403, bare arraynot authorized(witharguments/fieldasnull) — a third status code serving the bare-array format (412/404/403), folded into the conventions section.Write paths (register, reset, activation, update/delete) documented from the 2026-09 re-exploration, not exercised. Real account ids/emails kept out — placeholders only.
Docs-only change, no code touched. Test suite: 139 passed (unchanged baseline).
Merge Danger
Door: two-way (docs-only, trivially revertible)
Blast Radius: none — documentation only.
WIP: 📝 docs: account lifecycle endpoints + refreshtoken warningto 📝 docs: account lifecycle endpoints + refreshtoken warning