eric/ReleaseKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Distinguish asset read failures from unknown writes

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-06 00:54:49 +00:00
parent 91712fd900
commit b744346210
5 changed files with 66 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/roadmap/remediation.md
View File

@@ -131,6 +131,8 @@ followed by failed asset inspection. Both affected suites pass.
### R3 — Medium: Read-only asset failures are classified as unknown writes
Status: Resolved.
Category: Divergence from the selected outcome contract.
**Evidence:** [UploadMissing](../../internal/gitea/upload.go), around line 102,
@@ -153,6 +155,12 @@ as selected in the plan. Adjust tests and documentation consistently.
read-only invocation must not return unknown-write state or exit 3. A genuinely
ambiguous upload must continue to do so.
**Resolution:** Unverifiable preflight assets now return an inspection failure
with `not_attempted`, retaining partial page progress when creation preceded
the read failure. CLI tests cover existing and newly created pages, no asset
writes, and exit 1. Existing ambiguous-upload regressions still verify unknown
write outcomes. Both affected suites pass.
### R4 — Medium: Local artifact regeneration is prohibited
Category: Inadvertently strengthened prohibition.