Export V4.6 review log and mark the architecture review as historical

Preserves the traceability the V4.7 plan depends on ahead of starting implementation in a fresh session. Documentation only. The V4.6 review log was maintained in a session-scoped database and cited by number throughout the V4.6, V4.7, and V4.8 planning documents as "review log [N]". Those citations were unresolvable outside the session that produced them. The log is now exported verbatim to docs/ver4.6/review_log_v4_6.md: 70 entries, of which 8 remain open, each mapped to its disposition (V4.7 phase, accepted risk, or operator judgement). The architecture review report is retained rather than deleted. It is the canonical registry of the 32 finding IDs cited across six documents, so removing it would orphan every CRIT/HIGH/MED/LOW reference in the planning corpus. Instead it now carries a status banner marking it as a pre-V4.6 snapshot, warning that its paths, line numbers, and baseline metrics are stale, recording that all 32 findings were dispositioned in V4.6 with only MED-14 and HIGH-06 carrying into V4.7, and noting the two recommendations later revised on evidence - the cancelled services/artifacts.py extraction and the assumption that job_source and execution_attempt were complementary rather than duplicated. Co-authored-by: Copilot App <[email protected]>
2026-08-18 09:09:26 -05:00
parent 4488280097
commit 22d47574f2
4 changed files with 508 additions and 0 deletions
@@ -195,6 +195,7 @@ Every item in the scope boundary's Acceptance Criteria is satisfied, the suite i

 - [V4.7 Scope Boundary](scope_boundary_v4_7.md)
 - [Architecture & Code Review Report](../architecture_code_review_2026-08-17.md)
+- [V4.6 Review Log](../ver4.6/review_log_v4_6.md) - resolves the `review log [N]` citations used throughout this document
 - [V4.6 Implementation Plan](../ver4.6/implementation_plan_v4_6.md)
 - [V4.8 Feature Backlog](../ver4.8/feature_backlog_v4_8.md)
 - `.github/instructions/services.instructions.md`
@@ -184,6 +184,7 @@ This boundary is frozen. Adding an item requires a finding ID or a review-log en

 - [V4.7 Implementation Plan](implementation_plan_v4_7.md)
 - [Architecture & Code Review Report](../architecture_code_review_2026-08-17.md) - finding IDs
+- [V4.6 Review Log](../ver4.6/review_log_v4_6.md) - resolves the `review log [N]` citations used throughout this document
 - [V4.6 Scope Boundary](../ver4.6/scope_boundary_v4_6.md) - the baseline this release builds on
 - [V4.6 Implementation Plan](../ver4.6/implementation_plan_v4_6.md)
 - [V4.8 Feature Backlog](../ver4.8/feature_backlog_v4_8.md) - where deferred feature work is parked