docs(6210): acceptance sweep — src, scripts and frontend leftovers described in the present tense

The acceptance greps found what the per-area passes missed:

- src/scribe: "Phase 7/8" removal notes in projects, settings and
  user_profile; a paragraph promising an auto-summary side effect that no
  longer exists; user_profile's claim that "upcoming MCP profile tools" read
  the profile, which nothing does; an instance count and instance rule
  titles in plugin_context; "MILESTONE 323 DECIDED" in rulebooks.
- scripts/: check_plugin's header and inline comments were a history of
  the incidents behind each guard, with issue numbers in two failure
  messages; check_dangling_styles named this app's classes as its examples;
  check_design_tokens, measure_duplication and mint_plugin_version cited
  issues and checklists.
- frontend/src: forty-odd comments with four-digit issue numbers that the
  earlier frontend scan filtered out as hex colours, plus "used to" and
  "Phase N" notes.

Kept: illustrative ids (`#4181` as a bare-id example, `PR #198`), migration
Create Date headers and one migration's dated data floor, and the plugin
skills' worked examples of how to cite a record.

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

frontend/src/components/AppHeader.vue

@@ -132,11 +132,10 @@ router.afterEach(() => {
 }
 /* Three tracks, not a flex row with an absolutely-centred overlay.
  *
- * The pill bar used to be `position: absolute; left: 50%`, which meant it did
- * not participate in layout: when the header ran out of room it OVERLAPPED the
- * brand and the utility cluster rather than pushing them, and nothing wrapped
- * or scrolled to signal it. A sixth link reached that point at ~1270px, which
- * is an ordinary window on any monitor.
+ * A pill bar at `position: absolute; left: 50%` does not participate in
+ * layout: when the header runs out of room it OVERLAPS the brand and the
+ * utility cluster rather than pushing them, and nothing wraps or scrolls to
+ * signal it — at an ordinary window width on any monitor.
  *
  * `1fr auto 1fr` fixes it structurally. A `1fr` track has an AUTO minimum, so
  * neither side can be squeezed below its content, and the two side tracks stay
@@ -327,7 +326,7 @@ router.afterEach(() => {
   margin-top: 0.25rem;
 }
 
-/* The grid above means running out of room can no longer cause a collision —
+/* The grid above means running out of room cannot cause a collision —
    but it can still make the header wider than the window, and a horizontally
    scrolling header is its own defect. So shed width before that happens. The
    wordmark goes first: the logo beside it says the same thing and is still the

frontend/src/components/LessonsTaughtPanel.vue

@@ -12,8 +12,7 @@
  * A COMPONENT rather than markup inside the task editor, because the same
  * question is worth answering on any record a lesson can cite — an issue, a
  * spike, a dev-log. One panel, mounted wherever that is true, instead of the
- * shape being written a second time the first time someone wants it on notes
- * (#3207).
+ * shape being written a second time the first time someone wants it on notes.
  *
  * SILENT WHEN EMPTY. Most records taught no lesson, and a panel that renders
  * "None yet" on every page is a panel people learn to skip — which costs the

frontend/src/components/ProjectDesignTab.vue

@@ -1,6 +1,6 @@
 <script setup lang="ts">
 /**
- * A project's own code, checked against the design system it is bound to (#2432).
+ * A project's own code, checked against the design system it is bound to.
  *
  * This is what the design surface is FOR: a project's recorded components
  * measured against the sheet they are supposed to use. The check itself is not
@@ -38,7 +38,7 @@ async function run() {
   } catch {
     // Said out loud rather than rendered as an empty result. "Couldn't check"
     // and "nothing to report" look identical if you let them, and that is how
-    // a check comes to sit dead without anyone noticing (#2419).
+    // a check comes to sit dead without anyone noticing.
     failed.value = true;
   } finally {
     loading.value = false;

frontend/src/components/ProjectStatusBadge.vue

@@ -4,7 +4,7 @@
  *
  * Deliberately not StatusBadge. That component is typed to TaskStatus and
  * speaks a different vocabulary; these two only ever shared a CSS class name,
- * which is what made them look like one shape that had drifted (#3132).
+ * which is what makes them look like one shape that has drifted.
  *
  * Extracted because ProjectView and ProjectListView really were spelling the
  * same pill twice, with the differences you get from two hands rather than

frontend/src/components/StarterRolePicker.vue

@@ -1,6 +1,6 @@
 <script setup lang="ts">
 /**
- * The starter token ROLES offered when a design system is created (#2349).
+ * The starter token ROLES offered when a design system is created.
  *
  * WHY THIS IS A COMPONENT
  * DesignSystemsView has two creation forms — the empty state and the one inside
@@ -11,7 +11,7 @@
  * WHAT IT OFFERS
  * Names and purposes, never values. A role is a question the operator answers
  * with their own palette; a default palette would be one install's taste
- * shipped as product (rule #115). Every group is individually skippable —
+ * shipped as product. Every group is individually skippable —
  * an operator who wants three tokens should get three.
  *
  * All groups are checked by default. That default lives HERE rather than in the

frontend/src/components/StatusBadge.vue

@@ -4,7 +4,7 @@ import type { TaskStatus } from "@/types/task";
 const props = defineProps<{
   status: TaskStatus;
   clickable?: boolean;
-  /** Dense surfaces — smaller, unshouted. The canon (#2960) names compact a
+  /** Dense surfaces — smaller, unshouted. The canon names compact a
       VARIANT of this component rather than a reason to re-spell it. */
   compact?: boolean;
 }>();

frontend/src/components/SystemsSection.vue

@@ -72,7 +72,7 @@ function areaName(system: System): string | null {
   return canon.byId(system.canonical_id)?.name ?? null;
 }
 
-/** How many times this area's rulings reached a session (#4769). Not the
+/** How many times this area's rulings reached a session. Not the
  *  UsageBadge: its "N/M used" reads opens over showings, and rulings are
  *  delivered in full in the line, so an unopened System is the arm working,
  *  not dead weight. */
@@ -721,16 +721,16 @@ async function confirmDelete() {
   word-break: break-all;
 }
 
-/* RESTORED (#2444). Both lost their base rule to a CSS sweep; only the
-   `--archived` modifier and the `:hover .system-actions` reveal survived.
-   The card WAS a flex row and every child still says so — `.system-swatch`
+/* BASE RULES for the card and the list. Without them only the `--archived`
+   modifier and the `:hover .system-actions` reveal would remain.
+   The card is a flex row and every child says so — `.system-swatch`
    and `.system-actions` are `flex-shrink: 0`, `.system-body` is `flex: 1`,
    and `.system-form--inline` is `flex: 1`. `align-items: flex-start` is why
    the swatch carries `margin-top: 0.3rem`: it is nudged onto the first line
    of text rather than centred against the whole card.
 
-   The list had no rule at all, so it rendered with browser bullets and
-   indent — invisible to the dangling-style check, which can only see a class
+   Without its rule the list renders with browser bullets and indent —
+   invisible to the dangling-style check, which can only see a class
    that is PARTLY styled. A class with no rules anywhere looks exactly like a
    semantic-only hook.
 

frontend/src/components/TokenPreview.vue

@@ -1,6 +1,6 @@
 <script setup lang="ts">
 /**
- * A design system's tokens, drawn rather than listed (#2431).
+ * A design system's tokens, drawn rather than listed.
  *
  * WHAT MAKES THIS WORK FOR A SYSTEM YOU AREN'T RUNNING
  * Every value is resolved on an offscreen probe carrying only this system's
@@ -14,7 +14,7 @@
  * SPECIMENS ARE CHOSEN BY VALUE SHAPE, NEVER BY NAME
  * A colour is drawn as a swatch, a length as a rule of that length, a font
  * stack as text set in it. Nothing here matches `--fs-space-*` or any other
- * naming convention, because the convention is the install's (rule #115) — a
+ * naming convention, because the convention is the install's — a
  * system that calls its spacing `--gap-N` gets the same treatment.
  *
  * A token with no value for the chosen mode is shown as undecided rather than

frontend/src/components/rules/RuleHistoryPanel.vue

@@ -13,8 +13,8 @@
  * fields moved".
  *
  * What was genuinely shared is shared: DiffView.vue takes DiffLine[] and
- * nothing note-shaped, and the LCS walk now lives in utils/diff.ts, which
- * this file uses rather than copying a fourth time (#3207).
+ * nothing note-shaped, and the LCS walk lives in utils/diff.ts, which this
+ * file uses rather than carrying a copy of its own.
  */
 import { computed, onMounted, ref, watch } from "vue";
 import DiffView from "@/components/DiffView.vue";

frontend/src/components/rules/RulebookDetailPane.vue

@@ -62,7 +62,7 @@ ul { list-style: none; padding: 0; margin: 1rem 0; }
 li { padding: 0.5rem; cursor: pointer; border-radius: 6px; }
 li.active { background: var(--fs-accent-soft); }
 li:hover { background: var(--fs-surface-hover); }
-/* `.new-topic` is deliberately bare (#2444): it wraps a button-or-form whose
+/* `.new-topic` is deliberately bare: it wraps a button-or-form whose
    children style themselves, and namespaces the descendant rule below. */
 .new-topic input {
   width: 100%; margin-bottom: 0.5rem;