feat: add community publishing and news syndication

PRODUCT.md

@@ -8,7 +8,7 @@ web
 
 ## Users
 
-SHD.build serves active *The Division Resurgence* players who need reliable game
+SHD.build serves active _The Division Resurgence_ players who need reliable game
 data, accurate loadout planning, build sharing, and community guides.
 
 Registered players can save and share builds, publish guides, participate in
@@ -21,8 +21,8 @@ administrators manage users, roles, system configuration, and operations.
 
 ## Product Purpose
 
-SHD.build is an independent community intelligence platform for *The Division
-Resurgence*. It includes a public game database, calculated loadout builder,
+SHD.build is an independent community intelligence platform for _The Division
+Resurgence_. It includes a public game database, calculated loadout builder,
 shared builds, guides, news, and community participation.
 
 Players should understand game systems, create accurate loadouts, learn from
@@ -41,7 +41,8 @@ Player-facing planning and reference experiences use the same moderated data.
 
 Players use the site to plan characters, compare drops, reproduce in-game
 equipment, browse community recommendations, and respond to game updates. The
-interface must work from mobile devices through high-resolution desktop displays.
+interface must work from mobile devices through high-resolution desktop
+displays.
 
 The principal public channels are News, Database, Builds, Guides, and Builder.
 Account management includes authentication methods, profile identity, avatars,
@@ -58,12 +59,12 @@ connect proposed records to pending records before approval.
 - The application is built with SvelteKit and Svelte.
 - Persistent application data uses the embedded `@tursodatabase/database`
   package. Turso Cloud is not required.
-- Development, staging, and production use distinct databases. Embedded
-  database files and uploaded assets are persistent user data and must survive
+- Development, staging, and production use distinct databases. Embedded database
+  files and uploaded assets are persistent user data and must survive
   deployments and additive schema migrations.
 - Authentication supports passkeys, emailed magic links, Discord OAuth, and
-  optional username/password credentials. An account must always retain at
-  least one usable sign-in method.
+  optional username/password credentials. An account must always retain at least
+  one usable sign-in method.
 - Anonymous builder drafts may use local storage. Database-backed sharing
   requires an account.
 - Saved builds support private, unlisted, and public visibility.
@@ -78,13 +79,13 @@ connect proposed records to pending records before approval.
 - Major data changes preserve contributor-entered data through verified backups
   and additive migrations with minimal development-server downtime.
 - SHD.build is an independent fan site. Ubisoft and the relevant owners retain
-  rights to *Tom Clancy's The Division*, *The Division Resurgence*, and their
+  rights to _Tom Clancy's The Division_, _The Division Resurgence_, and their
   associated intellectual property and assets.
 
 ## Brand Commitments
 
 The product name is `SHD.build`, with `SHD` capitalized. The product serves the
-full *The Division Resurgence* community, including loadout planning.
+full _The Division Resurgence_ community, including loadout planning.
 
 Use restrained in-universe operational language such as agent, ISAC, Oversight,
 intelligence, access, transmission, and registry when it improves comprehension.
@@ -134,8 +135,8 @@ identity controls must follow their respective provider requirements.
 
 SHD.build targets WCAG 2.2 AA. Interfaces must support keyboard navigation,
 clear focus-visible states, screen-reader semantics, sufficient contrast,
-reduced-motion preferences, and layouts that work from mobile screens through
-4K desktop displays.
+reduced-motion preferences, and layouts that work from mobile screens through 4K
+desktop displays.
 
 State and meaning cannot depend on color, icons, hover, or motion alone.
 Controls need usable touch targets. User identity must support non-ASCII display