Correct reporting and release navigation
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Consolidated audit catalog
|
||||
|
||||
Status: **3 distinct open findings: 3 P3**, consolidated from 30
|
||||
Status: **no open findings**, consolidated from 30
|
||||
numbered entries in seven audit documents. Reviewed audit state:
|
||||
`db732e3a1de55c844f77870e1c6db683c2685d5d`.
|
||||
|
||||
@@ -539,6 +539,9 @@ assertions without new exported test hooks.
|
||||
|
||||
## F25 — P3: The reporting ADR mixes implemented status with stale planning language
|
||||
|
||||
**Complete.** ADR status identifies its future-tense lifecycle language as
|
||||
historical and points to current GoDoc and CLI contracts.
|
||||
|
||||
ADR 0006 marks shared reporting implemented but still directs implementation
|
||||
status and format choices to a retired roadmap and describes the extension as
|
||||
planned. Readers can mistake completed work for a pending prerequisite.
|
||||
@@ -551,6 +554,9 @@ does not need a replacement ADR.
|
||||
|
||||
## F26 — P3: The README duplicates volatile module compatibility guidance
|
||||
|
||||
**Complete.** README keeps module orientation and links to the consumer guide
|
||||
as the owner of exact compatibility and installation guidance.
|
||||
|
||||
The root README repeats exact version combinations and candidate dependency
|
||||
details already maintained by the consumer guide. The facts currently agree, but
|
||||
two owners create policy and maintenance drift risk.
|
||||
@@ -563,6 +569,10 @@ consolidation, not a dependency change.
|
||||
|
||||
## F27 — P3: A historical release note points to a nonexistent section
|
||||
|
||||
**Complete.** A discoverable forward-only erratum links the corrected section,
|
||||
verified against the locally tagged consumer guide. The historical note and tag
|
||||
were not changed.
|
||||
|
||||
The ckprompt v0.2.0 release note uses the wrong consumer-guide fragment at its
|
||||
immutable tag. The file exists, but the requested section does not.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Audit remediation implementation plan
|
||||
|
||||
Status: in progress; Stages 1–21 complete.
|
||||
Status: in progress; Stages 1–22 complete.
|
||||
|
||||
Baseline: `d492c7747175c01a53261206c2b4356e53453621`. Before this sprint,
|
||||
intervening changes recorded decisions and retired the completed older
|
||||
@@ -685,6 +685,11 @@ validation or a new public pointer utility.
|
||||
|
||||
## Stage 22 — Correct current documentation and historical navigation
|
||||
|
||||
**Complete.** ADR status identifies historical lifecycle language, README links
|
||||
to the consumer guide's compatibility owner, and the forward-only ckprompt
|
||||
v0.2.0 erratum links the corrected pinned section. The heading was verified in
|
||||
the tagged Git object and Markdown whitespace checks passed.
|
||||
|
||||
Findings: F25, F26 and F27.
|
||||
|
||||
1. In ADR 0006's Status section, explicitly mark remaining pre-implementation
|
||||
|
||||
Reference in New Issue
Block a user