docs(6208): ProjectView, KnowledgeView, SnippetListView and components.css comments drop citations and stories

components.css says why shared recipes live there without the five-copy
.btn-primary count; KnowledgeView's editor-routing and chip comments state
the present reason instead of the bug that once routed snippets wrong.

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

frontend/src/assets/components.css

@@ -3,11 +3,10 @@
  *
  * WHY THIS FILE EXISTS
  *
- * `.btn-primary` was defined five times, in five scoped stylesheets, and all
- * five had drifted: three paddings, three font sizes, three disabled opacities,
- * and one view with no disabled style at all (#2273). Nothing detected that,
- * because a scoped duplicate is invisible to every tool — it isn't a rule
- * violation, isn't a broken reference, and isn't a recorded snippet.
+ * A recipe copied into several scoped stylesheets drifts — paddings, font
+ * sizes, disabled states — and nothing detects it, because a scoped duplicate
+ * is invisible to every tool: it isn't a rule violation, isn't a broken
+ * reference, and isn't a recorded snippet. Shared recipes live here instead.
  *
  * GEOMETRY LIVES HERE. Every value is a design-system token, so a palette or
  * scale change moves the buttons rather than stranding a copy that no longer
@@ -301,9 +300,7 @@
 /* ── Page container ─────────────────────────────────────────────────────────
    The one wrapper a top-level view sits in: page width from the layout
    tokens, centred, clipped horizontally so a wide child (a kanban, a table)
-   scrolls inside itself instead of the page. ProjectListView, ProjectView and
-   SnippetListView each carried this rule under their own name until #2903
-   (milestone 299). */
+   scrolls inside itself instead of the page. */
 .page-container {
   max-width: var(--fs-layout-page-max);
   margin: 2rem auto;
@@ -311,12 +308,11 @@
   overflow-x: clip;
 }
 
-/* ── Form input (fs-surfaces, snippet #2336) ────────────────────────────────
+/* ── Form input (fs-surfaces) ───────────────────────────────────────────────
    Inputs sit DARKER than the page they're on — an inset well rather than a
    raised panel; that inversion is what makes a field read as writable. The
    design system's recipe, verbatim; width/box-sizing stay the caller's
-   (an inline select and a full-width textarea differ there). Three scoped
-   copies of an older input recipe were folded into this in #2903. */
+   (an inline select and a full-width textarea differ there). */
 .fs-input {
   background: var(--fs-surface-page);
   border: var(--fs-border);
@@ -331,8 +327,8 @@
 .fs-input:focus { outline: none; box-shadow: var(--fs-focus-ring); }
 .fs-input:disabled { opacity: var(--fs-disabled-opacity); cursor: not-allowed; }
 
-/* Page scaffold + feedback text recipes (milestone 302, note 2917): name
-   families the consumer map showed to be one recipe living in many views.
+/* Page scaffold + feedback text recipes: families that are one recipe
+   living in many views.
    A view keeps only its deviation as a scoped remainder/override. */
 .page-header {
   display: flex;
@@ -355,9 +351,8 @@
 /* --- usage badge ----------------------------------------------------------
    "surfaced N×, opened M×" on a list row, for any record kind the retrieval
    surfaces can choose: snippets and notes from note_usage_events, rules from
-   rule_usage_events. Promoted here from SnippetListView's scoped block when
-   the rule list needed the same chip (milestone 333 step 5) — a second scoped
-   copy is how the ninth duplicated CSS family starts (#3207).
+   rule_usage_events. Shared here because a second scoped copy is how a
+   duplicated CSS family starts.
 
    Geometry and colour only. A view keeps its own spacing as a scoped
    remainder, the way it does for every other recipe in this file. */