amadan
settings-2 final review: the authorize write-failed draft no longer claims nothing was signed
Astra final A4, ruling R18. The record is signed before the Put, and a failed response does not prove the bucket refused the write, so the draft now says the write could not be confirmed and that a rerun checks (Authorize is idempotent: it reports "already" or signs). Still a draft under Paul's copy review.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+2
−2
internal/updatewords/words_authorize.go+2 −2
diff --git a/internal/updatewords/words_authorize.go b/internal/updatewords/words_authorize.go| index dc4c43d41..fb2ad946a 100644 |
| --- a/internal/updatewords/words_authorize.go |
| +++ b/internal/updatewords/words_authorize.go |
| @@ -40,8 +40,8 @@ func init() { |
| Text: "this console has no release key, so it cannot sign a promotion record", |
| Context: "Returned by the console's authorize door when the console was started without the deployment's release key. Shown by carlos releases authorize."}, |
| Draft{ID: "settings.authorize.write-failed", |
| - Text: "could not write the promotion record. Nothing was signed. Try again", |
| - Context: "Returned by the console's authorize door when the bucket refused the record write. Shown by carlos releases authorize."}, |
| + Text: "could not confirm the promotion record was written. Run the command again to check", |
| + Context: "Returned by the console's authorize door when the record write failed or its outcome is unknown. Running the command again reports \"already\" if the record was written, or signs it. Shown by carlos releases authorize."}, |
| Draft{ID: "settings.authorize.usage", |
| Text: "usage: carlos releases authorize [--app <a>] [--account <sqid-or-name>] [--yes] <version>", |
| Context: "Printed when carlos releases authorize is run with the wrong arguments."}, |