chore: add seed db script

[viganogabriele]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e5691eaf-5029-4d77-9034-b5771c9517c8

📥 Commits

Reviewing files that changed from the base of the PR and between ce07438 and 80b301c.

📒 Files selected for processing (3)

• scripts/seed-db.ts
• scripts/seed-user.ts
• src/routers/tg/messages.ts

💤 Files with no reviewable changes (1)

• scripts/seed-user.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• scripts/seed-db.ts

---

Walkthrough

Adds a Bun database seeding command that resets and populates Telegram tables with encrypted synthetic data, while Telegram message router procedures use an exported cipher instance.

Changes

Telegram Data Tooling

Layer / File(s)	Summary
Seed command and reset control package.json, scripts/seed-db.ts, scripts/seed-user.ts	Adds seed:db, defines seed datasets and helpers, checks existing Telegram tables, truncates them with --force, and removes the top-level server import from user seeding.
User, group, and message generation scripts/seed-db.ts	Generates encrypted users, randomized groups, and encrypted messages with linked authors, random group assignments, per-chat IDs, timestamps, batched inserts, and completion counts.
Exported Telegram message cipher src/routers/tg/messages.ts	Exports tgMessagesCipher and uses it for message encryption and decryption across router procedures.

Possibly related PRs

• PoliNetworkOrg/backend#33: Related seeding-tooling changes involving package.json and scripts/seed-user.ts.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: adding a new database seeding script.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/seed-db.ts`:
- Around line 12-69: Apply the repository’s Biome formatter to
scripts/seed-db.ts and commit the resulting formatting changes, ensuring the
file passes bun run biome ci . without altering its behavior.
- Around line 48-62: Protect the force reseeding branch in the seed script by
requiring an explicit development/non-production database guard before executing
the TRUNCATE through DB.execute. Update the existing force handling around argv
and the existing-data check so --force exits safely when the configured database
target is not explicitly approved, while preserving normal seeding and the
existing refusal behavior for populated databases without --force.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3b52a2f7-014e-430c-bc9a-dbe27ab0139f

📥 Commits

Reviewing files that changed from the base of the PR and between fe27ead and ce07438.

📒 Files selected for processing (2)

• package.json
• scripts/seed-db.ts