Format declaration paths only for issues

This commit is contained in:
2026-11-07 15:56:25 +00:00
parent 83386217db
commit 0a81be84f6
3 changed files with 15 additions and 4 deletions

View File

@@ -1,6 +1,6 @@
# Consolidated audit catalog
Status: **9 distinct open findings: 9 P3**, consolidated from 30
Status: **8 distinct open findings: 8 P3**, consolidated from 30
numbered entries in seven audit documents. Reviewed audit state:
`db732e3a1de55c844f77870e1c6db683c2685d5d`.
@@ -479,6 +479,9 @@ Also discussed in the [responsibility assessment](A1-responsibility.md#machinery
## F22 — P3: Successful declaration validation eagerly formats every full path
**Complete.** The walk reuses a scratch path and formats it only for retained
issues or root-only placement errors. Focused declaration and registry tests pass.
`collectDeclarationIssues` copies and formats each ancestral path before knowing
whether a diagnostic is needed. A valid depth-N declaration chain incurs Θ(N²)
cumulative path work and allocation while producing no errors.