docs(teams): phase 11 as built, and what the rig walk found #166
Reference in New Issue
Block a user
No description provided.
Delete Branch "docs/teams-phase11-record"
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?
The "as built" record for Phase 11 — the integration kit, which ran before the cutover as Part 12 planned. Missed the merge window on docs#165 by a few minutes; same branch, one commit.
Four notes beside the phase entry:
module-uoand nobody else, and the kit is what proved it. Core filled three literaluo.guild.*names, so a second game declared its places under its own id and core filled none of them — empty page, no error, nothing logged. Settled the same day and amended into 1.6.0 in place (website#160 / Module-uo#15 / docs#165). The kit could not have taught the shape honestly without it, which is the argument for writing the book before the cutover rather than after./clansprefix — deliberately not/teams, which is core's and which the loader would refuse./public/teams/<slug>/membersansweredprojected: true, and the clan page rendered core's activity feed and forum in the module's own declared slots.module-uo's guild page walked unchanged on the same core. The walk found the one defect no test could —PageHeadertakeslead, notsubtitle, and React drops an unknown prop in silence.The kit's own PR (
RunicGateway/Integration-kit) is written and held:checkCoreApiis an equality against a core onmain, and 1.6.0 does not reachmainuntil the cutover, so the pin move rides in that PR.AI disclosure
Written with Claude Code (Opus 5). Commits carry the
Co-Authored-Bytrailer.