Artifact database branches also left the classifier and summary paths, moving behind a delegate.
What's wrong with this entry?
The read and write database branches in the artifact tool's classifier-input, description and summary functions are also gone from that handler, while the database section of the prompt and its batch-write limit remain. This reads as a move behind the per-action delegate those functions already consult, not a loss of functionality.
Artifact database: A published artifact's page code can keep a small shared database
Strings lifted out of the shipped bundle, so the claim above can be checked against them.