nx_galx_viewadd.nx

nx_galx_viewadd.nx -- put a cid into the gallery's VIEW index, so the image actually APPEARS. THE THIRD INDEX. Operator, 2026-08-07: *"i also dont see your new gens in nishifamily.com/gallery in the gens area"* -- after I had verified 10/10 served over /img/<cid> and called it done. Both claims were true at once, because the gallery keeps THREE separate indexes: 1. galx_cid_paths.tsv -> galx_cid.idx/.blob RESOLVER (/img/<cid> finds the bytes) 2. galx_view_index.txt ENUMERATOR (what the grid lists) 3. galx_search.tsv SEARCH I fixed (1), proved (1), and shipped. An image in (1) but not (2) is fetchable by anyone who already knows its cid and INVISIBLE to everyone else -- which is the same as not existing. ★★★★★★ "IS IT IN THE INDEX" IS THE WRONG QUESTION. THE QUESTION IS "HOW MANY INDEXES ARE THERE, AND IS IT IN EACH ONE THAT A USER'S PATH GOES THROUGH?" ★ I ASKED WHETHER THE READER COULD RESOLVE IT, NEVER WHETHER ANY READER WOULD EVER ASK. Format, measured not assumed: FIXED-WIDTH 70-byte records = 69-char cid + '\n', and the order is NEWEST-FIRST (verified by resolving record[0] and record[last] to their files and comparing mtimes: 2026-06-14 vs 2026-03-15). So a new gen PREPENDS. Appending would file it as the oldest image in the gallery and bury it under 226,576 others -- technically "added", never seen. Usage: nx_galx_viewadd <view_index> <cid> [<cid> ...] [--apply] license_tier: ORIGINAL