Context
In the keyless signing flow, the publicKey.content field currently contains a raw public key instead of the expected short-lived Fulcio certificate. This deviates from the intended design where the certificate should be included for proper verification.

Version
v0.26.0

To Reproduce
Steps to reproduce the behavior:

1. Initiate a keyless signing operation.
2. Inspect the publicKey.content field in the resulting signature.
3. Observe that it contains a raw public key rather than the Fulcio certificate.

Actual behavior

The publicKey.content holds a public key string instead of the Fulcio-issued short-lived certificate.

Expected behavior

The publicKey.content should include the short-lived Fulcio certificate as part of the keyless signing flow.

Screenshots (optional)
If applicable, add screenshots to help explain your problem.

N/A

Environment

• windows
• linux
• mac

Additional Comments
Any observation, gut feeling or other information you think help the community to troubleshoot the problem?

This mismatch may cause issues with downstream verification processes that expect the Fulcio certificate rather than just the raw public key. Investigating the signing flow to ensure the certificate is correctly embedded would help resolve potential verification failures.