feat(db): add header/footer config foundation

[thewrz]

Summary

• add open Zod schemas for header/footer composition payloads
• add header_footer_configs with client/project/package/revision scoped overrides
• add DB query surface for upsert/find/delete and effective resolution from client -> project -> package -> revision
• update ADR-017 to keep DOCX Header/Footer rendering out of the manual assembly engine

Design decisions

• Header/footer configs are JSONB with typed known keys and JSON-safe extension keys, matching the ADR-021 open-schema posture.
• Client scope is limited to libraries.tier = 'client'; project context resolves the first client project source by priority.
• Resolution performs deep object override by layer. Arrays and scalar values replace rather than merge.
• No DOCX output is produced here. Rendering remains a later sprint, per feat(db): header/footer composition model — fields + per-scope overrides (no DOCX render) #208.

Verification

• pnpm exec eslint src/ast/header-footer-schemas.ts src/db/queries/header-footer.ts src/db/queries/header-footer.integration.test.ts src/db/migrations/030_header_footer_configs.ts src/ast/index.ts src/db/index.ts
• pnpm exec tsc --noEmit
• pnpm exec prettier --check src/ast/header-footer-schemas.ts src/db/queries/header-footer.ts src/db/queries/header-footer.integration.test.ts src/db/migrations/030_header_footer_configs.ts src/ast/index.ts src/db/index.ts docs/adr/017-project-manual-publishing.md
• NODE_ENV=test DATABASE_URL=postgres://specr:specr@localhost:5432/specr_issue208 pnpm migrate:down
• NODE_ENV=test DATABASE_URL=postgres://specr:specr@localhost:5432/specr_issue208 pnpm migrate
• NODE_ENV=test DATABASE_URL=postgres://specr:specr@localhost:5432/specr_issue208 pnpm exec vitest --project integration src/db/queries/header-footer.integration.test.ts

Note: full pnpm lint on the origin/main base is blocked by the existing src/ast/schemas.ts line-cap failure, tracked separately in #220.

Closes #208

[coderabbitai]

Warning

Review limit reached

@thewrz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 41 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e5f32dfa-d320-4a0d-a000-da3b99887461

📥 Commits

Reviewing files that changed from the base of the PR and between 6018654 and 61acde7.

📒 Files selected for processing (7)

• docs/adr/017-project-manual-publishing.md
• src/ast/header-footer-schemas.ts
• src/ast/index.ts
• src/db/index.ts
• src/db/migrations/030_header_footer_configs.ts
• src/db/queries/header-footer.integration.test.ts
• src/db/queries/header-footer.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/issue-208

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thewrz]

CI triage note: the current failing Lint (ESLint + tsc + prettier) check is inherited from the base branch, not from this PR's diff. The failure is src/ast/schemas.ts exceeding the 400-line cap; this PR does not touch that file.

The base fix is already open and green in #220 (fix(ast): extract revision schemas to restore 400-line cap). After #220 merges, rerun/rebase this PR and the lint check should clear. CodeRabbit produced no review threads or actionable inline comments on this PR; its top-level comment was a rate-limit/usage notice.