fix(todo): move task #15 PROPERTIES drawer above sub-headings

The dated sub-entry added in the audit pass left the LAST_REVIEWED line
below the first level-3 heading, where the staleness checker can't see it
(it scans only between the level-2 heading and the next heading of any
depth). The fix moves the PROPERTIES drawer to its standard org-mode
placement, immediately after the level-2 heading.

1 files changed, 4 insertions, 4 deletions

diff --git a/todo.org b/todo.org
index 2595ec6..24bc9ae 100644
--- a/todo.org
+++ b/todo.org
@@ -1184,6 +1184,10 @@ Reference (dotemacs): =scripts/coverage-summary.el=, =modules/coverage-core.el=,
 Origin: handoff from the .emacs.d session, 2026-05-25.
 
 ** TODO [#B] Cross-project pattern catalog :spec:thinking:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-05-28
+:END:
+
 From pearl handoffs [[file:docs/design/2026-05-27-pattern-catalog-pearl-notes.org][2026-05-27]] + [[file:docs/design/2026-05-28-pattern-catalog-no-empty-input.org][2026-05-28 follow-up]].
 
 Meta-question: how do good patterns travel from project A to project B? Pearl shipped three worked examples worth capturing — one-prompt picker with typed prefix (pearl-pick-source), magit-transient state buttons, and "no empty input as meaningful" (none-sentinel as first candidate). Each is a small principle with wide surface area; without a catalog, every project re-derives them from scratch.
@@ -1200,10 +1204,6 @@ Pearl recommends a one-page spec (problem + design + open questions + acceptance
 *** 2026-05-28 Thu @ 08:12:55 -0500 Pearl shipped patterns 4-6, filed alongside the prior two
 Three more pearl handoffs landed and were filed during this audit. Filed: [[file:docs/design/2026-05-28-pattern-catalog-prompt-labels-and-defaults.org][prompt-labels-and-defaults]] (patterns 4-5: label-matches-behavior, default-most-common with friction-proportional-to-consequence) and [[file:docs/design/2026-05-28-pattern-catalog-prompt-collapse.org][prompt-collapse]] (pattern 6: collapse N orthogonal prompts into one enriched prompt). The catalog's evidence base is now four pearl notes in =docs/design/= covering six patterns plus the synthesizing principle Pearl articulated — "choices on screen, accurately labeled, ordered by what the user most often wants, friction sized to the cost of being wrong."
 
-:PROPERTIES:
-:LAST_REVIEWED: 2026-05-28
-:END:
-
 ** TODO [#C] Generic agent runtime support — Codex spec v0 :spec:design:
 Codex drafted a v0 design doc for making rulesets runtime-neutral rather than Claude-Code-specific. Motivating cases: offline operation with a local LLM, and two LLMs running in the same project at the same time without trampling each other's session-context.