Repository navigation
chore: P0 consolidation — two-plane architecture + content-contract hard gate - #69
Conversation
…contract hard gate Documentation and CI debt cleanup after the Hugo migration (no runtime change to the shipped site except a stricter publishing contract). Content Contract (P0 #1/#3): - scripts/ci-content-contract.cjs: split into ADDED (hard gate, exit 1 on invalid new post) vs MODIFIED (report-only) tiers. New publications in content/blog/ MUST satisfy schema/post-metadata.schema.json. - .github/workflows/hugo.yml: drop `|| true` — an invalid new post now blocks the Hugo build/deploy (it was only a warning before). CI/CD consolidation (P0 #2): - .github/workflows/deploy-ipfs.yml: DISABLED (legacy Jekyll build + compromised Pinata credentials; tag pre-phase7-legacy keeps the Jekyll state). - .github/workflows/security.yml: drop Ruby/Jekyll steps (broken post-Phase-7), pin aquasecurity/trivy-action@v0 (was @master). - Fix stale `master` branch refs -> `main` in analytics.yml, security.yml, sync_gists.yml. Docs: - AGENTS.md rewritten for the Hugo + Blowfish reality (was describing Jekyll). - README.md: tests badge, hard-gate wording, explicit CI/CD workflow table (single publisher = hugo.yml), link to the new ADR. - docs/adr/0002-two-plane-architecture.md: formal Publishing vs Engineering plane boundary, integration points, DAO lifecycle (separate track). Local: hugo build 155 HTML, validate-frontmatter exits 1 on invalid / 0 on valid, ci-content-contract vacuous on no-new-posts, hard gate wired.
|
|
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Stabilize after Hugo migration (no site runtime change except stricter publishing contract).
Local: hugo 155 HTML, validate-frontmatter exits 1 on invalid / 0 on valid, ci-content-contract vacuous.