Adding YSWS Review and Guardians of Integrity Tables, and Dashboards

[vandorena]

Adds Review Pages

Still TODO: Commit Graph + Ship Cert Integration + Airtable Sync

YSWS.Review.1.-.Stardance.-.Google.Chrome.2026-05-20.15-29-34.mp4

[vandorena]

YSWS.Review.4.-.Stardance.-.Google.Chrome.2026-05-14.11-48-10.mp4

What it's looking like so far

[vandorena]

Brakeman Failing isn't due to anything I've touched.

[Copilot]

Pull request overview

Copilot reviewed 47 out of 52 changed files in this pull request and generated 12 comments.

Comments suppressed due to low confidence (2)

db/migrate/20260512000003_add_devlog_review_id_to_post_devlogs.rb:1

• devlog_reviews already has post_devlog_id (i.e., the review points to the devlog). Adding post_devlogs.devlog_review_id plus an FK back to devlog_reviews creates a redundant/cyclic relationship that can easily drift or block deletes (FK prevents deleting a devlog_review if any post_devlog still points at it). Pick a single direction: either (a) keep devlog_reviews.post_devlog_id and remove post_devlogs.devlog_review_id + its FK migrations, or (b) remove post_devlog_id from devlog_reviews and make Post::Devlog belongs_to :devlog_review.
  db/migrate/20260514191951_add_status_to_devlog_reviews.rb:1
• The model declares status as an enum with default :pending, but this migration allows NULLs and does not set a DB default. That can lead to status = NULL rows (e.g., legacy data/backfills/SQL inserts) that don't behave like pending. Consider setting default: \"pending\" and null: false, and backfilling existing rows before applying the constraint.

[Copilot]

Pull request overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 14 comments.

[Copilot]

Pull request overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 19 comments.

[Copilot]

Pull request overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 8 comments.

[Copilot]

Pull request overview

Copilot reviewed 35 out of 35 changed files in this pull request and generated 10 comments.

Comments suppressed due to low confidence (1)

db/schema.rb:1

• This changes an existing FK to validate: false, which means the constraint may remain unvalidated indefinitely and can hide referential-integrity problems in production. If this is intentional for a zero-downtime rollout, follow up with a dedicated validate_foreign_key migration (similar to what you did for post_devlogs.devlog_review_id) to ensure the FK is eventually validated.