Admin Model & Superadmin Bootstrap Script

[codebestia]

Background

Admin already exists in the schema (id, address, createdAt, updatedAt) but has no way to actually get a row into it — there is deliberately no admin self-registration endpoint (unlike merchants, who provision themselves on first wallet sign-in). The first admin has to be created some other way: a terminal script. Every other admin issue depends on this model's final shape.

Proposed Steps

1. Extend the Admin model (see Schema Changes) and run prisma migrate dev.
2. Create scripts/create-superadmin.ts:
   • Accepts --address=<G...> and --name="..." CLI args
   • Validates the address with StrKey.isValidEd25519PublicKey (same check used in createChallengeController) — invalid address exits non-zero, no DB write
   • Rejects (loudly, non-zero exit) if an Admin row for that address already exists — this must never silently overwrite or duplicate; re-running with the same address is a mistake to catch, not a no-op to swallow
   • Creates the row with isSuperAdmin: true, active: true, createdBy: null (the bootstrap admin has no creator)
3. Add "admin:create-superadmin": "tsx scripts/create-superadmin.ts" to package.json scripts.
4. No HTTP route is created anywhere for this. It is intentionally CLI-only.

Schema Changes

Admin (extend existing model)

name         String
isSuperAdmin Boolean   @default(false)
active       Boolean   @default(true)
createdBy    String?   (FK → Admin.id, self-relation, nullable — null only for the script-bootstrapped admin)

Acceptance Criteria

• Admin model updated; prisma migrate dev runs cleanly
• npm run admin:create-superadmin -- --address=<valid G...> --name="Jane Doe" creates a row with isSuperAdmin: true, active: true
• Invalid Stellar address → script exits non-zero, no row created
• Address already present in Admin → script exits non-zero, no overwrite or duplicate row
• No HTTP endpoint exists for admin creation as part of this issue

[G-ELM]

I’d like to take this issue on. I’ve reviewed the scope and the implementation is nicely contained: extend the existing Admin model, add the self-relation, create the bootstrap CLI, and wire it into package.json without introducing any HTTP admin-registration route.

I’ll make the script deliberately fail-safe: validate the Stellar address with the same StrKey.isValidEd25519PublicKey check already used by the challenge flow, validate the required CLI arguments, check for an existing admin before writing, and exit non-zero on both invalid addresses and duplicate addresses. The bootstrap row will explicitly use isSuperAdmin: true, active: true, and createdBy: null.

I’ll also make sure the Prisma migration handles the existing Admin data correctly and verify the acceptance cases, particularly that invalid/duplicate input results in no DB write and that rerunning the command cannot silently modify an existing admin.

[grantfox-oss]

🦊 GrantFox — @G-ELM has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #39)
2. Your PR will be reviewed by the ShadeProtocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@G-ELM's PR #53 was approved and merged by @codebestia.

🏆 @G-ELM: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (634 total points). Track your full progress on GrantFox.

👏 Great work, @G-ELM! Keep contributing to ShadeProtocol.