base-layer/releasekit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

Report JSON output failures from recovery commands

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-02 22:23:15 +00:00
parent 648c87bb8a
commit 19a14bfeb6
4 changed files with 57 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/cli.md
View File

@@ -188,6 +188,11 @@ using current supported transport settings for its recorded remote name.
| Discovery completes without record diagnostics, including an existing empty store | 0 |
| Discovery is incomplete or fails, including cancellation | 1 |
| Discovery argument or usage error | 2 |
| Either command cannot write its JSON output | 1 |
A JSON write failure reports a local output diagnostic on standard error. This
status describes reporting failure and leaves the observed publication state
unchanged.
The CLI JSON schema and safe evidence fields are documented in the
[publication record format](integrations/publication-records.md). Recovery

5
docs/roadmap/remediation.md
View File

@@ -210,6 +210,11 @@ endpoint-only case. No new credential-storage policy is needed.
## R06: Propagate structured-output write failures — P2
**Completed:** Both recovery commands now report JSON encoder failures on
standard error and return status 1. Failing-writer regressions passed alongside
ordinary recovery status tests; observed publication state remains unchanged.
The CLI reference records the reporting-failure status.
**Relevant code:** `cmd/releasekit/recovery.go:242` and its two `writeJSON`
call sites.