feat: add community publishing and news syndication

.impeccable/critique/2026-07-26T15-49-23Z__src-routes.md

@@ -2,29 +2,30 @@
 target: application route system
 total_score: 28
 max_score: 40
-na_heuristics: 
+na_heuristics:
 p0_count: 0
 p1_count: 2
 timestamp: 2026-07-26T15-49-23Z
 slug: src-routes
 ---
+
 # SHD.build route-system critique
 
 ## Design Health Score
 
-| # | Heuristic | Score | Key issue |
-|---|---|---:|---|
-| 1 | Visibility of system status | 4 | ISAC exposes environment, access, mode, active navigation, and filter state clearly. |
-| 2 | Match system / real world | 3 | SHD vocabulary is authentic, but codes such as OSPR and WMOD need plain-language support. |
-| 3 | User control and freedom | 3 | Navigation and cancellation patterns are strong; empty destinations and filter clearing are less explicit. |
-| 4 | Consistency and standards | 3 | Shared patterns are cohesive, but live search plus Search, static-looking KPI links, and Edit-only rows diverge. |
-| 5 | Error prevention | 3 | Guardrails are extensive, but Add/Edit consequence language is not visible before entry. |
-| 6 | Recognition rather than recall | 2 | Seventeen ISAC destinations, code labels, and visually identical category cards create scanning burden. |
-| 7 | Flexibility and efficiency | 3 | Search, filtering, page sizes, and grouped navigation help experts; one-page registries expose unnecessary controls. |
-| 8 | Aesthetic and minimalist design | 2 | The system is disciplined, but cinematic hero scale and equally weighted bordered blocks compete with the task. |
-| 9 | Error recovery | 3 | The application has designed error and preservation patterns, though recovery was not exercised in the inspected states. |
-| 10 | Help and documentation | 2 | Microcopy exists, but ISAC terms, permissions, and proposal consequences lack contextual help. |
-| **Total** |  | **28/40** | **Good foundation; focused hierarchy and disclosure work needed.** |
+| #         | Heuristic                       |     Score | Key issue                                                                                                                |
+| --------- | ------------------------------- | --------: | ------------------------------------------------------------------------------------------------------------------------ |
+| 1         | Visibility of system status     |         4 | ISAC exposes environment, access, mode, active navigation, and filter state clearly.                                     |
+| 2         | Match system / real world       |         3 | SHD vocabulary is authentic, but codes such as OSPR and WMOD need plain-language support.                                |
+| 3         | User control and freedom        |         3 | Navigation and cancellation patterns are strong; empty destinations and filter clearing are less explicit.               |
+| 4         | Consistency and standards       |         3 | Shared patterns are cohesive, but live search plus Search, static-looking KPI links, and Edit-only rows diverge.         |
+| 5         | Error prevention                |         3 | Guardrails are extensive, but Add/Edit consequence language is not visible before entry.                                 |
+| 6         | Recognition rather than recall  |         2 | Seventeen ISAC destinations, code labels, and visually identical category cards create scanning burden.                  |
+| 7         | Flexibility and efficiency      |         3 | Search, filtering, page sizes, and grouped navigation help experts; one-page registries expose unnecessary controls.     |
+| 8         | Aesthetic and minimalist design |         2 | The system is disciplined, but cinematic hero scale and equally weighted bordered blocks compete with the task.          |
+| 9         | Error recovery                  |         3 | The application has designed error and preservation patterns, though recovery was not exercised in the inspected states. |
+| 10        | Help and documentation          |         2 | Microcopy exists, but ISAC terms, permissions, and proposal consequences lack contextual help.                           |
+| **Total** |                                 | **28/40** | **Good foundation; focused hierarchy and disclosure work needed.**                                                       |
 
 ## Design Specificity Verdict
 
@@ -36,11 +37,12 @@ blocks flatten into a generic dark administrative grid.
 
 The deterministic scan found seven source findings across `src/routes`: one
 warning for the two-pixel semantic notification rail in
-`src/routes/account/+page.svelte`, and six advisory colors outside the documented
-palette in the homepage and account route. The rail is largely a detector false
-positive because it conveys semantic message state, but its colors should still
-come from named tokens. The homepage build colors are data-like values rather
-than structural CSS, yet they also bypass the maintained palette.
+`src/routes/account/+page.svelte`, and six advisory colors outside the
+documented palette in the homepage and account route. The rail is largely a
+detector false positive because it conveys semantic message state, but its
+colors should still come from named tokens. The homepage build colors are
+data-like values rather than structural CSS, yet they also bypass the maintained
+palette.
 
 Mutable browser injection was unavailable, so no visual overlay is claimed.
 Fresh Chrome tabs, screenshots, DOM snapshots, and computed styles instead
@@ -72,8 +74,8 @@ its complexity according to the operator's current task and role.
 
 The Attributes screen simultaneously presents 17 sidebar destinations, four
 system-state blocks, four KPI filters, search, pagination, row-size controls,
-six table columns, and repeated Edit actions. Experienced operators can scan
-it, but contributors and new Oversight users must decode the whole information
+six table columns, and repeated Edit actions. Experienced operators can scan it,
+but contributors and new Oversight users must decode the whole information
 architecture before acting.
 
 **Fix:** make sidebar groups collapsible, prioritize modules by role and recent
@@ -109,8 +111,8 @@ to a clear secondary path.
 
 ### P2 — Empty registries promise the same value as populated registries
 
-Four of eight Database cards show zero records and “Awaiting contributions,”
-but look and behave like full destinations. That creates repeated anticipation
+Four of eight Database cards show zero records and “Awaiting contributions,” but
+look and behave like full destinations. That creates repeated anticipation
 followed by a low-value endpoint.
 
 **Fix:** give empty registries an explicit empty-state anatomy with expected
@@ -121,10 +123,10 @@ not imply the same outcome as populated data.
 
 ### P2 — Functional contrast and interaction grammar remain uneven
 
-Muted database descriptions, inactive navigation, unit sublabels, and
-pagination text recede heavily. KPI filters resemble static metrics, table rows
-look selectable while only the small Edit action works, and a Search button
-remains beside an input that searches as the user types.
+Muted database descriptions, inactive navigation, unit sublabels, and pagination
+text recede heavily. KPI filters resemble static metrics, table rows look
+selectable while only the small Edit action works, and a Search button remains
+beside an input that searches as the user types.
 
 **Fix:** reserve the dimmest tone for nonessential metadata, raise informative
 copy and available navigation one contrast step, make KPI filter state
@@ -147,9 +149,9 @@ seven-plus pagination/search controls, and 22 repeated Edit actions.
 The Database hero creates a confident, premium entry peak. Populated cards
 promise useful intelligence, but visually equal empty categories produce a
 disappointment valley. ISAC's “Online / Authorized / Admin” state reassures
-operators, then the uniform density creates fatigue with little calm focus.
-The most important missing reassurance is a plain statement of what Add/Edit
-will do to live data.
+operators, then the uniform density creates fatigue with little calm focus. The
+most important missing reassurance is a plain statement of what Add/Edit will do
+to live data.
 
 ## Persona Red Flags