From 321edf4e65f79b837b2cb5889163629a5ca71684 Mon Sep 17 00:00:00 2001 From: Anthony Johnson II Date: Wed, 17 Jun 2026 17:11:41 -0700 Subject: [PATCH] docs(changelog): record planned-sibling link classification (PR #51) Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7d1aafc..0da929f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -32,6 +32,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Fixed +- Hooks: the post-write internal-link check in `doc_post_write.py` no longer + reports links to planned-but-not-yet-generated suite siblings as broken + links. During incremental suite generation a document can legitimately link + to a sibling that is declared in a suite manifest but not yet written; + `check_internal_links()` flagged every missing target as a `Broken link` + consistency issue, producing false positives. The check now loads every + manifest `output_path` via the new `hook_utils.load_suite_output_paths()` + helper and routes missing-but-planned targets to non-blocking suggestions + ("Planned sibling not yet generated"), while genuinely unknown missing + targets remain broken-link issues so real mistakes are still caught. Smoke + tests cover both the planned-sibling and genuine-broken cases (PR \#51) - Hooks: the pre-write code-block language-hint check in `doc_pre_write.py` now flags tilde (`~~~`) fences, not just backtick (` ``` `) fences. `check_code_blocks()` previously split content into lines and only matched