Correct specificity figure and rewrite README styling conventions for accuracy

Re-review of the final-review fixes found two text-only errors:

- .nav-links a's specificity was given as (0,4,1); the compiled selector
  (.nav-links[data-astro-cid-*] a[data-astro-cid-*]) is actually (0,3,1).
  The conclusion is unchanged (it still outranks .nav-github's (0,2,0)),
  only the arithmetic in the comment and deferred-findings.md was wrong.
- The README's styling-conventions bullets described a consistency the
  code doesn't have: utilities aren't reserved for "simple" outer-element
  rules (7 of 9 components use scoped CSS even for 1-3 declaration rules),
  and "never set the same property both ways" is contradicted by Hero's
  deliberate utility-base-plus-scoped-media-override pattern. Rewrote the
  section to state plainly that the split is by component, not by rule
  complexity, that the codebase isn't uniform, and to recommend the
  majority (scoped-CSS) pattern for new sections.

11/11 parity tests pass, astro build clean, astro check clean.

Author: muhammetsafak

README.md

@@ -11,16 +11,24 @@ npm run dev
 
 ## Styling conventions
 
-- Use Tailwind utilities for simple layout and spacing on a component's outer
-  elements.
-- Write a scoped `<style>` rule for anything with more than about four
-  declarations, or that deserves a name worth reading.
+- Two approaches exist today, split by component rather than by rule
+  complexity: `Navbar.astro` and `Hero.astro` put Tailwind utilities on
+  their outer markup; the other seven components (`Stats`, `FeaturedCard`,
+  `CategoryCard`, `LibCard`, `Footer`, `Install`, `ScrollTop`) and the page
+  section shells in `index.astro` are scoped-CSS-only, even for
+  one-declaration rules. The codebase is not uniform.
+- For new sections, follow the majority pattern: a scoped `<style>` rule per
+  component, named for what it styles. Reserve utilities for one-off
+  arbitrary values on an element that doesn't need a named rule.
 - Rules shared across multiple files go in `src/styles/global.css`, under
   `@layer components`.
 - Never set the same property both ways on the same element. Astro's scoped
   styles are unlayered, so they beat both `@layer base` and Tailwind
-  utilities — a utility and a scoped rule targeting the same property do not
-  resolve by specificity the way you'd expect; pick one per property.
+  utilities — a utility and a scoped rule targeting the same property
+  resolve by rule type, not by specificity the way you'd expect.
+  `Hero.astro`'s utility padding (`pt-40 pb-24`) overridden by a scoped
+  `@media` rule for mobile is the one deliberate use of that pattern here;
+  keep it commented if you add another.
 
 ## Test
 

src/components/Navbar.astro

@@ -75,7 +75,7 @@ import { Icon } from 'astro-icon/components';
   }
 
   /* .nav-github, baseline.html:172-182. !important is required here:
-     .nav-links a (0,4,1) outranks .nav-github (0,2,0), both unlayered, so
+     .nav-links a (0,3,1) outranks .nav-github (0,2,0), both unlayered, so
      specificity — not layering — decides. Verified: removing it renders
      #94a3b8 (--color-text-secondary) instead of #e2e8f0
      (--color-text-primary). Do not drop it. */