itd-130's press release says 'now the next line is abcd update' and that the eight schema-too-new error sites 'now have a verb they can name'. Delivered: version --check still prints only 'update available: X -> Y' with no next step, and the schema-too-new sites (for example lifeboat/embark.go and release/ingest.go) still say 'upgrade abcd' without naming the verb. The verb exists; the surfaces that motivated it were not re-pointed. Surfaced by the itd-130 fidelity audit (receipt rcp-264f7b144576) as a diverged item. Fix is one string per site plus a test that greps the tree for 'upgrade abcd' outside the update verb's own remedy text.

itd-130's press release says 'now the next line is abcd update' and that the eight schema-too-new error sites 'now have a verb they can name'. Delivered: version --check still prints only 'update available: X -> Y' with no next step, and the schema-too-new sites (for example lifeboat/embark.go and release/ingest.go) still say 'upgrade abcd' without naming the verb. The verb exists; the surfaces that motivated it were not re-pointed. Surfaced by the itd-130 fidelity audit (receipt rcp-264f7b144576) as a diverged item. Fix is one string per site plus a test that greps the tree for 'upgrade abcd' outside the update verb's own remedy text.

Grounds

• pursued: one primitive (update.NextStep) rendering the verb the update dispatch already owns keeps every surface pointing at the same text; a second hand-written remedy string appearing, or a user still asking what to run after 'update available', would show it wrong