wtclaude c57310c505 feat(guilds): a third place on the guild page, and where that page lives ...

Two lines only core cannot supply for itself.

`uo.guild.header` is a third declared slot, at the top of the page, for core's
per-Team notification control. A third rather than a corner of the feed because a
slot holds one component and the first fill wins: the control is an action ON this
page and the other two are content IN it, and separate slots are what let this
module say so.

`pageUrlTemplate` tells core where a guild page actually is. Teams are a contract
primitive with no core surface — core owns the tables and the access rules, this
module owns the word "guild" and therefore the page — which leaves core unable to
write a link to one. A notification email that cannot take you to the thread it is
about is most of the way to useless. Core substitutes `{externalId}` and does
nothing else with it; a template naming its own host is refused at registration.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-18 14:35:36 -05:00

..

api.test.js

test(client): assert the URLs this module calls

2026-08-11 21:31:49 -05:00

build.test.js

test(client): check what the chunk registers, and fix two defects in the checks

2026-08-11 18:00:50 -05:00

regionBuckets.test.js

test(client): check what the chunk registers, and fix two defects in the checks

2026-08-11 18:00:50 -05:00

registration.test.js

feat(guilds): a third place on the guild page, and where that page lives

2026-08-18 14:35:36 -05:00

shardEvents.test.js

test(client): check what the chunk registers, and fix two defects in the checks

2026-08-11 18:00:50 -05:00