Repository navigation
chore: sync upstream and refresh Buzz self-hosting guidance - #25
Conversation
Signed-off-by: jeremylongshore <jeremylongshore@users.noreply.github.com>
Signed-off-by: jeremylongshore <jeremylongshore@users.noreply.github.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Warning Review limit reachedNext included review available in 7 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (16)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (16)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PR revises public fork and deployment documentation to describe a manual, digest-pinned operating posture, adds reviewer guidance, and updates fork governance checks. The additive-only gate now distinguishes exact paths from directory prefixes, with regression coverage wired into local and CI checks. ChangesPublic fork governance
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other Merge Risk: ⚪ Minimal · up to The governance and deployment guidance appears consistent with the updated fork checks. No actionable merge-blocking issue is identified; normal checks can complete before merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 3 files. (13 skipped: 13 unsupported.) ✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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 |
Signed-off-by: jeremylongshore <jeremylongshore@users.noreply.github.com>
…cleanup Signed-off-by: jeremylongshore <jeremylongshore@users.noreply.github.com> # Conflicts: # .harness-hash
What: regenerates .harness-hash after the merge combined main's 009 audit entry in 000-docs/000-INDEX.md with this branch's FORK.md/REVIEW.md edits. Why: the pinned hashes for 000-INDEX.md and FORK.md changed only because of the reviewed merge; verify must match the merged surface. How verified: scripts/audit-harness verify OK; fork gates (additive-only, must-survive, additive-only regression test) all pass on the merged tree.
Summary
This PR combines the already-prepared upstream synchronization with the fork-governance cleanup that followed it. The large upstream-owned diff is intentional: those paths are byte-for-byte from current
block/buzzupstream, while Intent Solutions changes remain confined to the additive fork allowlist.block/buzzupstreamAGENTS.mdis byte-identical toupstream/mainand document that authority boundaryintent-os/ops/buzz/Supersedes #23, whose useful content is incorporated here on top of the synchronized branch.
Validation
scripts/fork-gates/check-additive-only.shscripts/fork-gates/test-additive-only.shscripts/fork-gates/check-must-survive.shscripts/audit-harness verifygit diff --checksha256sum AGENTS.mdmatchesgit show upstream/main:AGENTS.mdTracked by closed beads
buzz-31bandbuzz-1ga;buzz-v2pis superseded.Summary by CodeRabbit