API vocabulary: deprecations owed, scope not recorded

open   by a73x

Labels: backlog

[claude 2026-08-18] Carried in notes as an item of the v0.0.7 structural list
("API-vocab deprecations") with no surviving description — filing it so it is not
lost, but the scope needs restating before it can be worked. Best guess from context:
names on the API surface the code has outgrown (teardown vs delete, "unrecorded",
managed CA) that want a deprecation path rather than a silent rename.
Needs a decision from the human on what is actually in scope.