docs(link): the panel, and the two deletions it could see and no test could (Phase 8) #243
Reference in New Issue
Block a user
No description provided.
Delete Branch "docs/asset-bridge-p8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records the Asset Bridge's phase 8 — the admin surface — as built. Pairs with Module-uo#41.
What's here
link/v8.md§12.2 (new) — the panel as built: one page (Admin → Client Files) over the creature catalogue, item and land art, and the cliloc table, because they come off one client install and change on one event. The four decisions are written down, including the one that kept the phase to a single repo: §14's "activity view" is the last import's own summary rather than a filtered feed — the alternative was a core activity filter, actx.activity.listhelper and aMODULE_APIbump, to re-read rows the panel can keep itself.needsReviewreturning each vanished key with the picture the site serves for it.website/CLILOCS.md,website/SPAWN_ATLAS.md— both said "Admin → Shard → Import". That button is nowAdmin → Client Files → Update.modules/uo/API.md— theneedsReviewreply shape.The part worth reading twice
Two of the three defects the walk found were deletions, both predate phase 8, and neither was reachable by a test that did not already suspect it:
The rule they share is now stated in §12.2: after phase 5,
shard_assetsis three collections in one table, and every read of it that feeds a decision has to say which one it means. Two of the three that did not were deletions.AI-assisted contribution
Written with Claude Code (Claude Opus 5). The commit carries the
Co-Authored-Bytrailer.🤖 Generated with Claude Code
https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4
v8.md section 12.2 records the admin surface as built: one page, Admin -> Client Files, over the creature catalogue, item and land art, and the cliloc table -- one page because they come off one client install and change on one event. The four decisions are written down, including the one that kept the phase to a single repo: section 14's "activity view" is the last import's own summary rather than a filtered feed, which would have needed a core activity filter, a `ctx.activity.list` helper and a MODULE_API bump to re-read rows the panel can keep itself. The part worth reading twice is what the walk found. Two of the three defects were DELETIONS, both predate phase 8, and neither was reachable by a test that did not already suspect them: * the body import diffing its manifest against every family's rows, so 313 item pictures were staged for deletion under a sentence that was wrong about what had happened; * an approved vanish unlinking the sprite and keeping the row, so the key came back for review forever and the count never moved. The rule they share is now stated: after phase 5, `shard_assets` is three collections in one table, and every read of it that feeds a decision has to say which one it means. Two of the three that did not were deletions. CLILOCS.md and SPAWN_ATLAS.md now name the button that exists (Admin -> Client Files) instead of the one they promised, and modules/uo/API.md records that a `needsReview` reply carries each vanished key's picture. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4