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

Keep committed release note reads offline

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-10 15:20:03 +00:00
parent 80d88a0352
commit 6c7b77970b
5 changed files with 106 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/internal/validation.md
View File

@@ -107,6 +107,7 @@ Committed-tree metadata and blob reads disable lazy fetching and Git transports
for those child commands. Missing local objects produce inspection errors;
source preparation retains its separate network-capable operations. See Git's
[lazy-fetch controls](https://git-scm.com/docs/git) for the command mechanism.
Candidate and delivery release-note reads use the same local object boundary.
Public validation errors convert their diagnostic fields to the internal
failure model for shared formatting. Converted failures retain their original

13
docs/roadmap/remediation.md
View File

@@ -1,6 +1,6 @@
# Remediation: module release implementation review
Status: open; issues 1–13 are complete, and issues 14–15 require remediation.
Status: open; issues 1–14 are complete, and issue 15 requires remediation.
The initial review examined `90559fe`, compared with planning baseline `dbfae9e`.
The follow-up repository audit examined `6b0b8ce`, including those corrections.
@@ -504,7 +504,16 @@ local path without timing thresholds or additional source guarantees.
## Issue 14: Keep committed release-note inspection within the local object boundary (P2)
Status: open. Category: incomplete earlier offline-inspection correction.
Status: complete. Category: incomplete earlier offline-inspection correction.
**Completion:** Committed-file reads now use the shared local-only Git object
runner. Filtered-clone regressions cover direct reads plus public check and
delivery with an unavailable note, preserving the note path, Git cause, and
captured identity while making no hosted request, transport attempt, or object
database change. Both regressions exposed transport before the correction.
The Git/candidate suites and focused source, page-delivery, and explicit tagged
checkout preparation cases pass offline; ordinary note bytes and cancellation
handling retain their existing command boundary.
**Evidence:** [ReadCommitFile](../../internal/git/source.go), used by candidate
capture and delivery for release notes, executes `git show` through the ordinary