Phase-1 PR review sprint — pick a PR (#68–#73) and review

[SaharPak]

What's blocking

The Phase-1 stack has been ready to merge for two weeks. Six PRs sit open and unmerged since 2026-06-07:

• feat(schemas): add Zod contract package #68 — feat(schemas): add Zod contract package
• feat(intelligence): add rubric v1, archetypes, and validators #69 — feat(intelligence): add rubric v1, archetypes, and validators
• feat(prompts): add extract, score, and validate-claims pack #70 — feat(prompts): add extract, score, and validate-claims pack
• feat(cli): add power-user pack — Claude Code skill, commands, welcome #71 — feat(cli): add power-user pack — Claude Code skill, commands, welcome
• test(eval): add golden fixtures and pnpm eval harness #72 — test(eval): add golden fixtures and pnpm eval harness
• docs: add power-user quickstart and update structure #73 — docs: add power-user quickstart and update structure

The bottleneck is review bandwidth, not code quality. Until these merge, new contributors cloning main get a different product than what the README documents.

What we need

One reviewer per PR. The bar is not deep familiarity with the codebase — it's:

• TypeScript comfort
• Familiarity with zod (or willingness to learn the basics)
• ~30 minutes to read the diff and comment

How to claim

Comment on the PR you want to review: "I'll review this one." If you find issues, comment on specific lines. If it's good, approve.

Suggested priority order

If you can only review one, start with #68 (schemas) — it's the foundation, smallest in scope, and unblocks all the others.

After #68, #69 (intelligence) is the next dependency.

#70, #71, #72, #73 can be reviewed in any order.

Why this matters

This is the single highest-leverage contribution opportunity for TypeScript-comfortable contributors this week. 30 minutes of your time unblocks the entire Phase-1 stack and signals to the rest of the contributor base that the project is moving.