🧹 [Code Health] Refactor status function in src/lib.rs

[undivisible]

🎯 What: Extracted the logic for generating an interrupted ActionAck in OperationLedger::status into a new helper function generate_interrupted_ack.
💡 Why: The status function in src/lib.rs was overly long and complex. Extracting the initialization of the ActionAck object makes the status function much shorter and more readable, improving the maintainability of the codebase.
✅ Verification: Verified the refactoring is safe and behavior-preserving by running cargo test --lib, cargo fmt, and cargo clippy. All checks pass successfully.
✨ Result: The status function is now much cleaner, fulfilling the code health objective while preserving existing logic exactly.

---

PR created automatically by Jules for task 4522980260323203654 started by @undivisible

---

Note

Low Risk
Mechanical extract-function refactor with identical acknowledgement shape; no new logic paths beyond formatting in tests.

Overview
Interrupted-operation acknowledgements are now built via a new generate_interrupted_ack helper instead of a large inline ActionAck block in the ledger status/recovery path. The helper takes the same claim metadata (operation id, hash, timestamps, optional action name, delivery route, session isolation, interaction mode) and still emits a terminal OutcomeUnknown receipt with interrupted_outcome_message() and the same Unknown defaults for missing fields.

OperationLedger::status (or equivalent) is shorter and delegates to that helper; behavior is unchanged. tests/cli.rs only fixes indentation in the CLI test harness’s stdin write block.

^{Reviewed by Cursor Bugbot for commit 0a35894. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.