Feature/preconfirmation parity

[MitchTurner]

Linked Issues/PRs

#3160

Description

Checklist

• Breaking changes are clearly marked as such in the PR description and changelog
• New behavior is reflected in tests
• The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

• I have reviewed the code myself
• I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

[Add or remove entries as needed]

• Rust SDK
• Sway compiler
• Platform documentation (for out-of-organization contributors, the person merging the PR will do this)
• Someone else?

[cursor]

PR Summary

Medium Risk
Expands the GraphQL transaction status surface area and adds extra per-status storage reads (resolvedOutputs), which may affect API consumers and query performance if not handled carefully.

Overview
Improves parity between preconfirmation and finalized transaction statuses by expanding the GraphQL schema and client models.

SuccessStatus and FailureStatus now expose transactionId and optional resolvedOutputs, while PreconfirmationSuccessStatus/PreconfirmationFailureStatus add a time field; client queries/snapshots and TransactionStatus conversions are updated accordingly.

On the server, resolvedOutputs is computed from the stored transaction outputs (change outputs plus non-zero variable outputs), and preconfirmation statuses now stamp time at creation; preconfirmation-related tests were updated to match the new fields.

^{Written by Cursor Bugbot for commit dbd779f. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Preconfirmation time uses Tai64::now() instead of actual timestamp

High Severity

The time field for PreconfirmationSuccessStatus and PreconfirmationFailureStatus is set to Tai64::now() inside TransactionStatus::new(). This means every time a preconfirmation status is constructed — including when retrieved from storage via a query — the timestamp reflects the current wall-clock time, not when the preconfirmation actually occurred. Normal SuccessStatus and FailureStatus correctly use self.status.block_timestamp from persisted data, but the underlying PreConfirmationSuccess/PreConfirmationFailure structs lack a timestamp field entirely, so Tai64::now() was used as a stand-in. This yields non-deterministic, incorrect timestamps on repeated queries.

Additional Locations (1)

• crates/fuel-core/src/schema/tx/types.rs#L468-L469