From 19dda0db81de5aba7e579e8b8f5d6d178d4164f7 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Tue, 4 Aug 2026 11:49:03 -0400 Subject: [PATCH] docs(prompts): add model-deprecation trigger to loop-lane re-resolve list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Models section's re-resolve trigger list fired only on family GA or an observed alias flip — both reactive. A deprecation/retirement announcement for a model a lane alias resolves to precedes the alias move and is the earliest re-check signal, so add it as a third trigger, pointing at the upstream model-deprecations page rather than copying any dates or lifecycle tables. Resolved against the live page 2026-08-04 (raw .md capture 12,764 B, MD5 783f0a320e3c4a544103a8f163c8be79). Repo-root prompts surface — no plugin version bump. Co-authored-by: Claude Fable 5 --- prompts/loops/loop-lane-prompts.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/prompts/loops/loop-lane-prompts.md b/prompts/loops/loop-lane-prompts.md index d221b4dcac..d703585c3d 100644 --- a/prompts/loops/loop-lane-prompts.md +++ b/prompts/loops/loop-lane-prompts.md @@ -348,8 +348,12 @@ knowledge cutoff — are upstream-owned and are not restated here. Both orderings resolved as written against that page on 2026-08-04. Both are *derived* comparisons rather than quoted figures, so either can flip while every underlying number still reads -correctly: re-resolve them when a new Claude model family reaches GA, or -when one of the aliases above starts resolving to a different model. +correctly: re-resolve them when a new Claude model family reaches GA, +when one of the aliases above starts resolving to a different model, or +when a model one of them resolves to is announced deprecated or retired +([model deprecations](https://platform.claude.com/docs/en/about-claude/model-deprecations) +— the announcement leads the alias move, and upstream warns deprecated +models are likely to be less reliable than active ones). **The implementer tier is enforced structurally at the dispatch seam (#1649).** `/implementation:implement-dispatch` dispatches workers and