Repository navigation
fix: preserve caller paths in the standalone operation runner - #765
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 42 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (4)
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Adversarial Independent Review: PR #765
1. Findings and Identified BoundariesVerified Defects (P0–P3)None. Line-by-line inspection of the diff between Hardening & Informational Observations (P4–P5)
Missing Evidence and Review Limitations
2. Mandatory Verification ChecklistPart A: Code Paths Traced
Part B: Merges and Ancestry Audited
Part C: Constants and Numeric Claims Checked Against Evidence
Part D: Documentation and Standards Compliance
3. Verification Posture
4. Final VerdictAPPROVE |
|
Code Lawyer activity summary at
All 12 operation-runner tests, workspace rustfmt, and strict Clippy for the changed binary/integration-test targets pass in Docker. Exact committed files match both candidate manifests. Broader all-targets Clippy fails on an unchanged unit-test expression; CI uses the binary route. That unrelated failure remains disclosed, not silently greened. The clean-tree fetch, entire diff, caller paths, documentation, all paginated review discussions, current-head CI, and independent agy checklist were reviewed. No actionable PR finding remains. Independent agy verdict: APPROVE for this exact head. The already authorized merge still requires the final live head/CI check below. |
Closes #755.
The standalone operation runner previously required a Git repository and changed into its root before parsing arguments. It now preserves the caller directory, so absolute artifacts work outside Git and relative artifact/WAL paths keep their intended meaning. Repository maintenance commands retain Git-root discovery. The README and CHANGELOG describe this boundary.
Docker RED: both new runner-directory tests failed at the expected behavior assertions on main
da929ca6; the repository-command control passed. Docker GREEN: all 12 operation-runner tests passed, including the two new cases and the repository-command control. Workspace rustfmt and strict Clippy for the changed binary and integration-test targets passed.A broader
xtask --all-targetsClippy run failed on the existing, unchangedmap(...).unwrap_or(0)expression in an unrelated xtask unit test. CI checks xtask binaries; the changed binary and witness targets are clean. This unrelated failure is retained as a validation limit and is not absorbed into this repair.Canonical documentation review: README now names caller-directory behavior; operation/WAL semantics and artifact/receipt boundaries remain unchanged. No new product binary or application-specific core branch is added.