Publish reviewed Fall 2026 officer profiles

Author: Hilo-Hilo

.agents/skills/pre-production-checklist/SKILL.md

@@ -35,6 +35,20 @@ Run this gate whenever public routes, the canonical domain, page purpose, contac
 
 This gate passes only when the file accurately describes the current public site, all listed destinations are intentional, and the deployed copy is reachable without authentication.
 
+## Gate 3 — Officer profile publication
+
+Run this gate whenever the officer roster, a form-response snapshot, profile links, bios, or officer-data build logic changes.
+
+1. Run `npm test` and `npm run validate:officers`.
+2. Confirm `src/data/officersFa26Roster.json` is the only authority for cohort membership, roles, order, stable IDs, and fallback portraits.
+3. Confirm `src/data/officerProfilesFa26.json` contains the real Notion response page ID for provenance and only public profile fields copied from reviewed form responses. Never add email addresses, phone numbers, birthdays, or other private form answers.
+4. Review every unmatched submission, invalid profile link, and officer without a current response reported by the validator. An officer without a response may retain only the roster fallback; do not invent a bio or personal link.
+5. On the rendered page, open at least one complete profile and confirm its full bio and Website, LinkedIn, GitHub, and ORCID destinations are labeled, keyboard accessible, and correct.
+6. Confirm every added or replaced headshot path resolves in a clean build, and complete Gate 1 for its framing.
+7. Confirm the Fall 2025 and Spring 2026 archive tabs load from the tracked files under `public/officers/archive/`; a build must not require Notion, Google Sheets, or a prior production deployment.
+
+This gate passes only when the published roster matches the approved cohort, current public submissions enrich the correct people, invalid or private form values cannot leak through, and all officer tabs work from a clean checkout.
+
 ## Release discipline
 
 - Run checks against the public staging URL after pushing `dev`.

.github/workflows/deploy.yml

@@ -37,11 +37,10 @@ jobs:
           cache: 'npm'
       - name: Install dependencies
         run: npm ci
+      - name: Test
+        run: npm test
       - name: Build
         run: npm run build
-        env:
-          NOTION_API_KEY: ${{ secrets.NOTION_API_KEY }}
-          NOTION_OFFICERS_DB_ID: ${{ secrets.NOTION_OFFICERS_DB_ID }}
       - name: Setup Pages
         uses: actions/configure-pages@v5
       - name: Upload artifact

.github/workflows/staging-pages.yml

@@ -34,8 +34,8 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
-      - name: Mirror public officer data
-        run: node scripts/sync-preview-data.js
+      - name: Test
+        run: npm test
 
       - name: Build staging site
         run: npm run build:preview

.gitignore

@@ -38,9 +38,8 @@ my-vite-app/*
 # others
 dev/
 
-## EXTREMELEY IMPORTANT: DO NOT COMMIT THE FOLDER BELOW.
-## It doesn't contain sensitive data but it's fetched at build time, and
-## it may be quite heavy so there is no point in keeping it committed to the repository.
+## Legacy importer scratch output. Builds use the reviewed, tracked snapshots
+## under public/officers/ instead.
 public/fetched
 
 # Local deployment and TypeScript build state

README.md

@@ -1,53 +1,39 @@
 # Computational Biology at Berkeley
 
-## How to edit the code
+The public website for Computational Biology at Berkeley, built with Vite, React, TypeScript, shadcn/ui, and Tailwind CSS.
 
-**Use your preferred IDE**
-
-If you want to work locally using your own IDE, you can clone this repo and push changes. Pushed changes will also be reflected in Lovable.
-
-The only requirement is having Node.js & npm installed - [install with nvm](https://github.com/nvm-sh/nvm#installing-and-updating)
-
-Follow these steps:
+## Local development
 
 ```sh
-# Step 1: Clone the repository using the project's Git URL.
-git clone <YOUR_GIT_URL>
-
-# Step 2: Navigate to the project directory.
-cd <YOUR_PROJECT_NAME>
-
-# Step 3: Install the necessary dependencies.
-npm i
-
-# Step 4: Start the development server with auto-reloading and an instant preview.
+npm ci
+npm test
 npm run dev
 ```
 
-**Edit a file directly in GitHub**
+Run `npm run build` for the same credential-free production build used by GitHub Pages. The build validates officer data before compiling the site.
+
+## Officer data
 
-- Navigate to the desired file(s).
-- Click the "Edit" button (pencil icon) at the top right of the file view.
-- Make your changes and commit the changes.
+Fall 2026 deliberately separates approved roster decisions from submitted public profile content:
 
-**Use GitHub Codespaces**
+- `src/data/officersFa26Roster.json` owns cohort membership, roles, order, stable IDs, and fallback portraits.
+- `src/data/officerProfilesFa26.json` is a reviewed, public-only snapshot of the latest officer form responses.
+- `src/data/compileOfficerDirectory.js` matches responses to the roster, keeps the newest nonblank public fields, normalizes links, and ignores unmatched people.
+- `public/officers/fa26/` stores stable headshot assets.
+- `public/officers/archive/` stores immutable Fall 2025 and Spring 2026 snapshots so historical tabs work in a clean checkout.
 
-- Navigate to the main page of your repository.
-- Click on the "Code" button (green button) near the top right.
-- Select the "Codespaces" tab.
-- Click on "New codespace" to launch a new Codespace environment.
-- Edit files directly within the Codespace and commit and push your changes once you're done.
+Never copy private form fields such as email, phone number, or birthday into the repository. Run:
 
-## What technologies are used for this project?
+```sh
+npm test
+npm run validate:officers
+```
 
-This project is built with:
+The validator reports unmatched responses, invalid public links, missing assets, and officers still waiting for a current profile response. See `scripts/README.md` for the update workflow and `.agents/skills/pre-production-checklist/SKILL.md` before a production promotion.
 
-- Vite
-- TypeScript
-- React
-- shadcn-ui
-- Tailwind CSS
+## Deployment
 
-## How can I deploy this project?
+- Pushes to `dev` deploy the staging GitHub Pages site from the `Hilo-Hilo` staging repository.
+- Pushes to `main` deploy production from `CompbioAtBerkeley/compbioatberkeley.github.io`.
 
-Everything is automatically deployed once pushed so make sure to test the project before pushing.
+Neither build reads Notion or Google Sheets credentials. Form intake is reviewed and versioned before publication, so the same commit produces the same site in local, staging, and production environments.

package.json

@@ -6,11 +6,11 @@
   "scripts": {
     "assets:partners": "node scripts/build-partner-logos.mjs",
     "dev": "vite",
-    "prebuild": "npm run fetch-data",
-    "build": "vite build",
-    "build:dev": "vite build --mode development",
-    "build:preview": "vite build",
-    "fetch-data": "node scripts/fetch-officers-fa25.js && node scripts/fetch-officers-notion.js",
+    "test": "node --test scripts/lib/*.test.js",
+    "validate:officers": "node scripts/validate-officer-data.js",
+    "build": "npm run validate:officers && vite build",
+    "build:dev": "npm run validate:officers && vite build --mode development",
+    "build:preview": "npm run validate:officers && vite build",
     "lint": "eslint .",
     "preview": "vite preview"
   },

public/llms.txt

@@ -10,7 +10,7 @@ The organization welcomes students at all experience levels. Use the pages below
 - [About](https://compbioatberkeley.github.io/about): Mission and work across education, research, professional networking, and community impact.
 - [Calendar](https://compbioatberkeley.github.io/calendar): Current workshops, meetings, and special events in Pacific time.
 - [Collaborations](https://compbioatberkeley.github.io/collaborations): Partnership opportunities for students, faculty, alumni, research groups, and industry.
-- [Officers](https://compbioatberkeley.github.io/officers): Current and previous student leadership rosters.
+- [Officers](https://compbioatberkeley.github.io/officers): Fall 2026 and previous student leadership rosters, including submitted public bios and profile links.
 - [Join](https://compbioatberkeley.github.io/signup): Interest form, newsletter signup, and community channels.
 
 ## Contact and community