[rmcdaniel]

Part of #325.

The Shared Server fixtures workflow has failed on main since #561. In main run 39671560431, every native cancellation cell (codec-deadline-health on all databases, execution-and-codec, mysql-execution, postgres-storage) fails the same assertion, cleanup closes at persisted terminal time:

• expected 2026-10-21T23:12:52.433000Z: the run's closed_at;
• actual 2026-10-21T23:12:52.433Z: the WorkflowCancelled payload's cancellation_cleanup.finished_at.

Native wrote finished_at as a raw chrono time, which prints as few fractional digits as the value needs. Published Workflow writes it as closed_at->toISOString() (six digits), and CancellationCascadeView treats a different string as a mismatch. It now uses the six-digit form, like the cleanup_deadline_at and requested_at beside it.

Verification

• The cooperative cleanup integration test compared the two values only as parsed instants. It now also compares them as text. It fails without the change (…22.519Z against …22.519000Z) and passes with it.
• The SQLite cleanup, cancellation and cooperative tests pass (54).

Not fixed here
postgres-storage (postgres-17) in the same run stopped earlier, in the operator metrics waiting_after_redispatch stage. Its health snapshot warned durable_resume_paths while the metrics snapshot just before it counted no run needing repair. That is a timing difference between two requests. It is diagnosed separately once this assertion no longer hides it.

Checkpoint: docs/rust-server-port-checkpoints/2026-10-22-cleanup-finished-at.md.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud