Support configurable TOTP in credential commands

[masnwilliams]

Summary

• Add TOTP algorithm, digits, and period flags to credential create/update.
• Use typed Go SDK v0.116.0 request fields; preserve omitted values on updates.
• Document provisioning URI input and remove the six-digit assumption from code help.

Checks

• go test ./... passed locally.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​github.com/​kernel/​kernel-go-sdk@​v0.114.1-0.20260930182635-e746d9980b83 ⏵ v0.116.0	+1

View full report

[akxue]

looks good! comments are around help text and making the new totp flags a bit clearer. additionally, as a note, get/create don't output the new totp settings

• cmd/credentials.go:496-497 — on credentials update --help, --totp-digits and --totp-period show (6) / (30), which reads like leaving them off sets 6/30. the API actually keeps whatever's already stored when you rotate a base32 secret. maybe register these with default 0 so the default isn't printed, and add a line saying omitted settings are kept? (on create the help also prints (default 6) (6) since cobra appends the default automatically)
• cmd/credentials.go:185-206 — if --totp-secret is an otpauth:// URI that has its own digits/algorithm/period, the API uses the URI's values and silently ignores the --totp-* flags. i think we should warn here rather than reject
• cmd/credentials.go:165-175, cmd/credentials.go:268-278 — note: get/create only print Has TOTP Secret: Yes, so there's no way to confirm which algorithm/digits/period got stored. the sdk response includes these now, so they could be added as rows