Consume fjord-core for stack review summarization #187

Merged
stephen merged 1 commit from feat/consume-fjord-core-reviews into main 2026-06-19 16:07:22 +00:00
Owner

First ADR-0001 Phase 3 slice: fj now depends on the shared fjord-core crate (resolved from the Forgejo cargo registry) and delegates stack review-state aggregation to fjord_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.toml registers the fjord registry (reads are open, so CI resolves without a token).
  • rust-version rises to 1.95 (CI already builds on 1.95) since core requires it; serde_json bumped to 1.0.150 for core's floor.
  • cargo-audit ignores two unmaintained-only advisories that arrive transitively through 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.

First ADR-0001 Phase 3 slice: fj now depends on the shared `fjord-core` crate (resolved from the Forgejo cargo registry) and delegates stack review-state aggregation to `fjord_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.toml` registers the `fjord` registry (reads are open, so CI resolves without a token). - `rust-version` rises to 1.95 (CI already builds on 1.95) since core requires it; `serde_json` bumped to 1.0.150 for core's floor. - cargo-audit ignores two unmaintained-only advisories that arrive transitively through `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.
Consume fjord-core for stack review summarization
All checks were successful
ci / check (pull_request) Successful in 12m55s
ci / coverage (pull_request) Successful in 2m27s
ci / live-e2e (pull_request) Successful in 2m52s
4a0b60c428
First ADR-0001 Phase 3 slice: fj depends on the shared fjord-core crate from
the Forgejo cargo registry and delegates stack review-state aggregation to
fjord_core::workflows::stack::summarize_reviews. The reduction (request-changes
> approved > commented > none) and the ship-gate tokens it emits now live in one
place, so fj and the GUI clients can't drift on the verdict. Behavior is
unchanged; fj's existing stack tests cover it.

Raises fj's rust-version to 1.95 (CI already builds on 1.95) since core requires
it, and bumps serde_json to 1.0.150 to satisfy core's floor.
stephen deleted branch feat/consume-fjord-core-reviews 2026-06-19 16:07:22 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rasterstate/fj!187
No description provided.