The public catalog still served the September team draft, titled "The CommunityRule Project." This writes the Rule the team adopted on 30 Oct — title CommunityRule Creative Team, the Home-hero summary, and the remade-deck cards — into that featured row, including at container start, so a deploy cannot keep serving the old body.
Changes
Build the adopted Rule from the Home hero chips and remade-deck presets (lib/create/teamRule.ts).
Upsert that row as public and featured; if a second featured copy exists under either title, take it private (prisma/seed/teamRule.ts). Full seed calls the same helper.
Bundle scripts/seed-team-rule.ts into the image and run it in start.sh after prisma migrate deploy, before the server listens, so title, summary, and document land together.
Ops deploy and runbook notes: this one seed is the exception to “seed is not every deploy.”
Unit tests for the payload (no old-draft title or summary) and for the upsert / extra-row behavior.
Screenshots
How to Test
From repo root, with local Postgres: node --env-file=.env --import tsx scripts/seed-team-rule.ts (or npx prisma db seed). Confirm the log line Seeded team Rule: … CommunityRule Creative Team.
GET /api/rules — the featured list includes CommunityRule Creative Team and does not include The CommunityRule Project. The summary is “We build and maintain CommunityRule for the communities that use it…” Open the Rule’s document and check it has none of the old draft phrases (for example “Skill-Based Contribution”, “Conflict Resolution Council”).
Open / at 1440, 1024, 768, and 390. The hero card title and summary should match that catalog row. Chips should match the Home set; Consensus may read “Consensus” on the hero and “Consensus decision-making” from the catalog name.
After a staging deploy, container logs should show the seed line beforeListening on port 3000. Reload /api/rules on staging and repeat step 2.
Notes
Home still paints the card from messages/en/components/heroBanner.json, not from GET /api/rules. This PR makes the catalog row match that copy; wiring the hero to the API is leftover.
The word-for-word copy file was not in the repo. The published body is the remade-deck presets for the chips the Home hero already shows.
Re-running the seed is safe (idempotent upsert).
## Overview
The public catalog still served the September team draft, titled "The CommunityRule Project." This writes the Rule the team adopted on 30 Oct — title **CommunityRule Creative Team**, the Home-hero summary, and the remade-deck cards — into that featured row, including at container start, so a deploy cannot keep serving the old body.
## Changes
- Build the adopted Rule from the Home hero chips and remade-deck presets (`lib/create/teamRule.ts`).
- Upsert that row as public and featured; if a second featured copy exists under either title, take it private (`prisma/seed/teamRule.ts`). Full seed calls the same helper.
- Bundle `scripts/seed-team-rule.ts` into the image and run it in `start.sh` after `prisma migrate deploy`, before the server listens, so title, summary, and document land together.
- Ops deploy and runbook notes: this one seed is the exception to “seed is not every deploy.”
- Unit tests for the payload (no old-draft title or summary) and for the upsert / extra-row behavior.
## Screenshots

## How to Test
1. From repo root, with local Postgres: `node --env-file=.env --import tsx scripts/seed-team-rule.ts` (or `npx prisma db seed`). Confirm the log line `Seeded team Rule: … CommunityRule Creative Team`.
2. `GET /api/rules` — the featured list includes **CommunityRule Creative Team** and does not include **The CommunityRule Project**. The summary is “We build and maintain CommunityRule for the communities that use it…” Open the Rule’s document and check it has none of the old draft phrases (for example “Skill-Based Contribution”, “Conflict Resolution Council”).
3. Open `/` at 1440, 1024, 768, and 390. The hero card title and summary should match that catalog row. Chips should match the Home set; Consensus may read “Consensus” on the hero and “Consensus decision-making” from the catalog name.
4. After a staging deploy, container logs should show the seed line **before** `Listening on port 3000`. Reload `/api/rules` on staging and repeat step 2.
## Notes
- Home still paints the card from `messages/en/components/heroBanner.json`, not from `GET /api/rules`. This PR makes the catalog row match that copy; wiring the hero to the API is leftover.
- The word-for-word copy file was not in the repo. The published body is the remade-deck presets for the chips the Home hero already shows.
- Re-running the seed is safe (idempotent upsert).
Staging still listed the September draft under the old project name. Seed now
upserts the adopted title, summary, and remade-deck cards, and a data migration
renames the existing row so the public catalog picks it up on deploy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
The public catalog still served the September team draft, titled "The CommunityRule Project." This writes the Rule the team adopted on 30 Oct — title CommunityRule Creative Team, the Home-hero summary, and the remade-deck cards — into that featured row, including at container start, so a deploy cannot keep serving the old body.
Changes
lib/create/teamRule.ts).prisma/seed/teamRule.ts). Full seed calls the same helper.scripts/seed-team-rule.tsinto the image and run it instart.shafterprisma migrate deploy, before the server listens, so title, summary, and document land together.Screenshots
How to Test
node --env-file=.env --import tsx scripts/seed-team-rule.ts(ornpx prisma db seed). Confirm the log lineSeeded team Rule: … CommunityRule Creative Team.GET /api/rules— the featured list includes CommunityRule Creative Team and does not include The CommunityRule Project. The summary is “We build and maintain CommunityRule for the communities that use it…” Open the Rule’s document and check it has none of the old draft phrases (for example “Skill-Based Contribution”, “Conflict Resolution Council”)./at 1440, 1024, 768, and 390. The hero card title and summary should match that catalog row. Chips should match the Home set; Consensus may read “Consensus” on the hero and “Consensus decision-making” from the catalog name.Listening on port 3000. Reload/api/ruleson staging and repeat step 2.Notes
messages/en/components/heroBanner.json, not fromGET /api/rules. This PR makes the catalog row match that copy; wiring the hero to the API is leftover.