🐛 Classify the own tokens status change type develop added

develop gained :set-own-tokens-status on 2026-10-26, after this branch's
last rebase, and the-classification-table-names-every-change-type fails
by name on it.

It is a no-op for the overlay. The change writes :own-tokens-status, the
status a file keeps aside for its own tokens-lib while it points at an
external tokens source, and the builder indexes no active status, own or
otherwise.

AI-assisted-by: deepseek-v4.1-flash
Signed-off-by: Álvaro Tejero Cantero <alvorithm@teje.ro>
This commit is contained in:
Álvaro Tejero Cantero 2026-11-11 17:46:59 +01:00
parent e205a0002b
commit 00cbdc5608
No known key found for this signature in database

View File

@ -645,6 +645,7 @@
:del-media {:coverage :no-op :why "the same reason as an add's"}
:set-token-theme {:coverage :no-op :why "themes are not indexed"}
:set-tokens-status {:coverage :no-op :why "the active theme and set status is not indexed"}
:set-own-tokens-status {:coverage :no-op :why "the status a file keeps aside for its own tokens-lib is not indexed"}
:set-base-font-size {:coverage :no-op :why "file options are not indexed"}
:set-tokens-source {:coverage :no-op :why "the builder reads the file's own `:tokens-lib` whatever the source, so pointing the file at a library writes no datom"}})