We agree to develop tooling to better observe and manage the use of assets within wiki sides and possibly pods. Step one is to find an example of a probe that falls short and suggest variations moving in the desired direction.
As we use more and more Frame plugin html scripts in our day to day workflows we have ever increasing need to keep track of them and from where they are loaded. github 
.
This variation of Eric's jq script prints results in markdown.
ls | while read FILE; do items=$(jq '.journal|group_by(.id)|.[]|select(any(.type=="remove") and any(.item.type=="assets"))' $FILE;) if [ -n "$items" ]; then echo "1. $FILE"; fi done
1. aspects-of-recent-changes 1. cartesian-icosahedron 1. collaborating-community-hubs 1. editorjs-workflow 1. evidence-and-corroboration 1. example-sofi-assessment 1. food-web-unbound 1. fox-hunting 1. generate-a-rectangular-grid 1. geocoding-street-view 1. graphs 1. ideal-sapience 1. import-from-arrow 1. markov-monkey-script 1. mechanisms-progress 1. mountainstorm-cors-issue 1. need-help-with-git 1. pandemic-wandering 1. photo-to-wiki 1. portland-bridge-pedal 1. quest-for-beauty-in-ical-records 1. showcase-wiki 1. squeezed-picture-as-asset 1. table-top-augmented-reality 1. test-m1 1. the-privileged-and-their-servants 1. timberline-lodge 1. visitor-revisited 1. welcome-visitors 1. where-jeff-lives 1. wikidata-demo-places 1. wine-labels-released 1. world-modeled
The next step is to duplicate this with a script. github
pages/better-admin-with-mechs
Counts match. Hover to see action json.
http://ward.dojo.fed.wiki/assets/pages/better-admin-with-mechs/phantom-assets.html HEIGHT 400