Refactor application and runtime boundaries #61
Reference in New Issue
Block a user
Delete Branch "linux-refactoring-base"
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?
Summary
This branch makes the behavior-preserving portions of
REFACTOR.mdconcrete while making the project buildable and testable on Linux. DS4 behavior remains the oracle, and the high-risk Metal execution path is left untouched.Linux build and test support
REFACTOR.md work
NewMessageconstructors for system, user, tool-result, assistant, and compaction database rows.App::updatematch into the existing preferences domain module.ResponseKindenum and derive matching failure events directly fromOperation.The high-risk Metal FFI wrapper work and broad argument-count cleanup are intentionally not included:
REFACTOR.mdrequires dedicated DS4 parity coverage before changing those execution paths.Validation
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo test --all-features(118 passed before the recovery test; the branch now includes 120 tests, with the Chrome-dependent test ignored)cargo build --release --all-targets --all-featuresviamake bundlePackaging itself was not completed in the Linux environment because
cargo-packageris not installed.Pushed commit
8390569after reviewing and testing the shared refactor paths on macOS. It preserves completed DSML invocations when generation truncates a later structurally incomplete invocation while still rejecting invalid JSON, and makes Operation the single source of truth for runtime metrics tracking so queue, start, rejection, and completion accounting remain balanced. Regression tests cover both changes. Validation passed: cargo fmt check, Clippy with all targets and features and warnings denied, make bundle including app signing, and cargo test with 158 passed and 13 fixture-dependent tests ignored.