Consume fjord-core for stack split planning #188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/consume-core-split"
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?
Second slice of ADR-0001 Phase 3 (fj consumes the shared core), after review summarization in #187.
fj's split planning now delegates to
fjord_core::workflows::stack:Commitbecomes a re-export of core's canonical record (pub-field shape, identical layout).parse_commitsandvalidate_splitcall straight through; the validation error is mapped back to fj's bare message (core'sDisplayprefixesinvalid request:).plan_splitcalls core and converts the planned items back to fj'sStackItemvia a newFromimpl, narrowing core's i64 PR number to fj's u64 (PR numbers are positive).Pure planning only, no behavior change: all split tests pass verbatim (
parse_commits,validate_split,plan_splitchaining/fallback, the render and JSON-shape assertions). 605 tests green, clippy-D warningsand fmt clean.