docs(rules): enforce User Content Sovereignty and remove specific content bias from guidelines and skills

.agents/rules/blog-system.md

@@ -1,13 +1,29 @@
 # Technical Blog System Rules & Architecture Directives
 
-## 1. Pedagogical Explanations (Interactive Learning)
+## 1. Core Invariant: User Content Sovereignty (Highest Priority)
+1. **User Edits Are Absolute Ground Truth:**
+   - The user's edits, custom writing, post titles, navigation labels, terminology, and naming choices are the absolute highest level of truth in this codebase.
+   - They strictly take precedence over any background content description, sample design mockup (`sample-designs/*`), skill instructions, or default boilerplate.
+2. **Strict Prohibition on Unsolicited Rewriting or Renaming:**
+   - You must **NEVER** revert, alter, overwrite, or substitute user-authored text, titles, navigation labels, tags, or naming conventions unless the user directly and explicitly requests that specific modification.
+   - Do not reintroduce removed text or names from prior mockups or commits.
+3. **Mandatory Clarification Gate:**
+   - If you notice a potential inconsistency, typo, or naming ambiguity in user-authored content, you must **NOT** unilaterally modify it.
+   - You must ask the user for specific clarification before altering any user-authored writing or naming.
+4. **Sample Designs Are Layout References Only:**
+   - Files in `sample-designs/` serve solely as visual, CSS, and structural layout references.
+   - Never extract or re-inject titles, domain names, service labels, or technical copy from `sample-designs/` into active templates or site data without explicit instruction.
+
+---
+
+## 2. Pedagogical Explanations (Interactive Learning)
 1. **Explain the Code:** Whenever creating or refactoring code (Eleventy configuration, Nunjucks templates, CSS modules, build scripts), provide a clear, educational breakdown.
 2. **Break Down Key Concepts:** Explain *why* a particular Eleventy filter, Nunjucks tag, or CSS variable structure was used so the user learns the foundational concepts.
 3. **No Magic:** Avoid opaque or overly clever abstractions; prioritize readable, idiomatic code with commentary explaining tricky points.
 
 ---
 
-## 2. CSS Architecture & Isolation
+## 3. CSS Architecture & Isolation
 1. **Zero Monolithic Inlines:** Do not inject raw `<style>` blocks into HTML templates.
 2. **Modular File Structure:**
    - Put global tokens in `src/assets/css/tokens.css`.
@@ -30,7 +46,7 @@
 
 ---
 
-## 3. Templating Guidelines (Eleventy + Nunjucks)
+## 4. Templating Guidelines (Eleventy + Nunjucks)
 1. **Layout Hierarchy:**
    - Root template: `src/_includes/layouts/base.njk` (contains HTML structure, `<head>`, metadata, scripts, stylesheets).
    - Content layouts: `src/_includes/layouts/post.njk` (for articles), `src/_includes/layouts/page.njk` (for landing/catalog).
@@ -40,7 +56,7 @@
 
 ---
 
-## 4. Obsidian Content Pipeline
+## 5. Obsidian Content Pipeline
 1. **Frontmatter Specification:** Every post ingested from Obsidian must adhere to:
    ```yaml
    title: "Article Title"
@@ -57,7 +73,7 @@
 
 ---
 
-## 5. Test-Driven Development (TDD) & Adversarial Verification
+## 6. Test-Driven Development (TDD) & Adversarial Verification
 1. **Red-Green-Refactor Lifecycle:**
    - Write tests in `test/*.test.js` using Node's native test runner (`node:test`, `node:assert/strict`).
    - Test inputs before implementing filters, data loaders, or template macros.