Description of problem:

The hammer job-template info command does not display the locked field for job templates. This makes it difficult for users to determine from the CLI whether a job template is locked or editable. The lock status is visible in the WebUI and API, but not in the CLI output, leading to inconsistent behavior across interfaces.

How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Create or use an existing job template (locked or unlocked).

2. Run:

hammer job-template info --id <id> 

3. Review the output fields.

Actual behavior:
The output does not show whether the job template is locked.

Expected behavior:
The output should include the lock status of the template, consistent with the UI and API.

Business Impact / Additional info:

• CLI users cannot verify the lock status of job templates without switching to the UI or API.

• Increases the risk of failed modification attempts when users unknowingly try to edit locked templates.

• Including locked in the CLI output would ensure consistent visibility across all interfaces.