docs: record two prose-budget guard gaps the final review found

Both are deferred with the reason: the Args-then-narrative placement case needs an indentation-aware walk plus false-positive triage, and restricting pointer targets to .claude/notes/ is a design decision, not a mechanical guard. The two cheap gaps from the same review were closed in e71a16f0. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
uipreliga · Sep 16, 2026 · Sep 15, 2026 · Sep 15, 2026 · Sep 15, 2026 · Sep 15, 2026
commit c821fd8e12a742f2fe6b07845909ba62ae0dbfc3
@@ -975,3 +975,20 @@ re-derive from scratch.
   `tests/test_harbor_packager.py:163` and `:187`,
   `tests/lint/rules/ce064_turn_bracket_on_the_clock.py:40`. Caught in: tests
   prose slimming, Phases 3 and 7.
+
+- [ ] **Narrative after a docstring's `Args:`/`Returns:` block that follows a
+  `Rationale:` pointer.** `check_pointer_placement` accepts any tail that STARTS
+  with a trailing section, so pointer → `Args:` → an indented entry → a new
+  base-indented paragraph passes although the pointer is no longer the last prose
+  line. Guarding it means walking section blocks by indentation (the shape
+  `prose_words` already uses), plus false-positive triage over every src/ and
+  tests/ docstring that ends in a section — more than a quick add. Caught in:
+  tests prose slimming, final review (gpt-5.6-sol).
+
+- [ ] **A `Rationale:` pointer whose target is not under `.claude/notes/`.**
+  `check_pointers` joins the captured path onto the repo root, so an absolute
+  path, a `..` segment or any other Markdown file resolves, while CLAUDE.md and
+  `.claude/notes/README.md` define the pointer as a repo-relative notes path. No
+  such pointer exists today. Deferred because restricting the target is a design
+  decision (a `docs/` guide heading is a plausible SSOT target) rather than a
+  mechanical guard. Caught in: tests prose slimming, final review (gpt-5.6-sol).