Seed data: enable badge creation and linking to units

[stefan-burke]

Summary

• Extend seed data to create badge records and link them to units. This enables seeds and tests to cover badge creation alongside units.
• Update seed service to seed two inspections per user for broader coverage.

Changes

• db/seeds/units.rb

  • Create a badge batch and 8 badges, collect their IDs
  • Extend unit creation to accept a badge_id and assign the unit's id to that badge_id
  • Wire each seeded unit to a corresponding badge via badge_id
  • Maintain existing unit fields and descriptions

• spec/factories/units.rb

  • Add a new :with_badge trait to seed a unit with an associated badge
  • Trait creates or uses a badge batch and a badge, then links to the unit (unit.id is set to badge.id per seed convention)

• spec/seeds/assessment_seed_data_completeness_spec.rb

  • Include id in the system_columns to reflect system-managed IDs

• spec/services/seed_data_service_spec.rb

  • Update seeding to create two inspections per user (was previously one)

Why

• Enables badges to be created as part of seed data and linked to units, supporting tests and scenarios that rely on badge records. Also broadens seed coverage by generating two inspections per user.

How to test

• Run seeds in the development/test environment and verify:
  • 8 Badge records exist (from the seed batch)
  • 8 Unit records seeded with their corresponding badge linkage
  • Seed data completeness spec passes and system_columns include id
  • SeedDataService tests seed two inspections per user

Notes

• This change follows the existing seed convention where a badge_id is wired into unit creation. If you prefer a separate relation field (instead of setting Unit.id equal to Badge.id), we can adjust accordingly.

🌿 Generated by Terry

---

ℹ️ Tag @terragon-labs to ask questions and address PR feedback

📎 Task: https://www.terragonlabs.com/task/dd8e705f-466b-412d-ae63-7f3a469a56c6