Consume fjord-core for stack review summarization #187
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/consume-fjord-core-reviews"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First ADR-0001 Phase 3 slice: fj now depends on the shared
fjord-corecrate (resolved from the Forgejo cargo registry) and delegates stack review-state aggregation tofjord_core::workflows::stack::summarize_reviews.The reduction (request-changes > approved > commented > none) and the ship-gate tokens it emits (
changes_requested/approved/commented/none) now live in one place, so fj and the GUI clients can't drift on the verdict. Behavior is unchanged and fj's existing stack tests cover it.Mechanics:
.cargo/config.tomlregisters thefjordregistry (reads are open, so CI resolves without a token).rust-versionrises to 1.95 (CI already builds on 1.95) since core requires it;serde_jsonbumped to 1.0.150 for core's floor.uniffi(bincode RUSTSEC-2025-0141, paste RUSTSEC-2024-0436), matching the existing proc-macro-error exception. No direct dependency on either.This is the validate-first-by-fj step before the GUI surfaces adopt the same workflow.