feat: modified agent behavior for a more test centric workflow

.agents/rules/blog-system.md

@@ -74,14 +74,17 @@
 ---
 
 ## 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.
-2. **Adversarial Test Coverage Required:**
-   - **Data & Configuration:** Test that missing required environment variables (e.g. `SITE_DOMAIN`) throw fatal errors.
-   - **Filters:** Test edge cases: empty strings, undefined values, single-word inputs, massive word counts, non-date objects.
-   - **Content Schemas:** Validate all Markdown files in `src/posts/` against frontmatter schemas.
-   - **Design Spec Compliance:** Automate regex/AST assertions on `src/assets/css/` ensuring zero violations of the "Do Not Use" list (`backdrop-filter`, `box-shadow`, `text-shadow`, gradients, floaty transitions).
-   - **Link & Anchor Integrity:** Verify that every compiled page has zero broken internal links and that all Table of Contents anchor links resolve to valid heading IDs.
-3. **Execution Invariant:**
-   - Always run `npm test` before committing. All tests must pass cleanly with 0 failures.
+1. **Strict Pre-Implementation Testing (Tests Before Functional Code):**
+   - Test cases MUST ALWAYS be written in `test/*.test.js` before writing or modifying any functional code (filters, templates, server routes, ingestion pipeline, data loaders, scripts).
+   - Never implement or modify functional or production code prior to writing and establishing corresponding automated tests.
+2. **Mandatory Adversarial Test Coverage:**
+   - Standard behavior for any functional change MUST ALWAYS include adversarial testing specifically designed to stress assumptions and break the system:
+     - **Data & Configuration:** Test that missing required environment variables (e.g. `SITE_DOMAIN`) throw fatal errors.
+     - **Filters & Logic:** Test edge cases: empty strings, undefined/null values, unexpected types, single-word inputs, massive word counts, non-date objects.
+     - **Security & Integrity:** Test path traversals, malformed JSON, unauthorized tokens, malicious payloads.
+     - **Content Schemas:** Validate all Markdown files in `src/posts/` against frontmatter schemas.
+     - **Design Spec Compliance:** Automate regex/AST assertions on `src/assets/css/` ensuring zero violations of the "Do Not Use" list (`backdrop-filter`, `box-shadow`, `text-shadow`, gradients, floaty transitions).
+     - **Link & Anchor Integrity:** Verify that every compiled page has zero broken internal links and that all Table of Contents anchor links resolve to valid heading IDs.
+3. **Pre-Presentation Verification Gate:**
+   - Before presenting the final output to the user, run `npm test`.
+   - All test cases must pass before presenting the final output. Presenting unverified output or code with failing tests is strictly prohibited.

.agents/skills/eleventy-tiling-blog/SKILL.md

@@ -98,9 +98,14 @@ When writing or modifying Eleventy files:
 ---
 
 ## 4. Validation & Verification
+ 
+Always follow the project TDD standard: write automated tests (including adversarial edge cases) in `test/` before modifying functional templates, filters, or configuration. Ensure all test cases pass before presenting the final output.
 
-Run these commands to test Eleventy builds:
+Run these commands to test and verify builds:
 ```bash
+# Run complete test suite (unit tests, filters, server, design rules, build integrity)
+npm test
+
 # Validate Eleventy configuration and build static output
 npx @11ty/eleventy --dryrun
 
@@ -110,3 +115,4 @@ npx @11ty/eleventy
 # Launch local dev server with auto-refresh
 npx @11ty/eleventy --serve
 ```
+

.agents/skills/obsidian-sync/SKILL.md

@@ -100,3 +100,13 @@ The Obsidian plugin runs inside Obsidian desktop/mobile and interacts with the O
 If using CouchDB-based self-hosted LiveSync:
 - A local watcher or CouchDB change listener daemon can be configured to detect updates to notes marked with `published: true` or in a dedicated `Blog/` folder.
 - When an update event fires, the daemon pulls the latest revision from the CouchDB database, runs the normalization pipeline, and saves it to `src/posts/`.
+
+---
+
+## 6. Validation & Verification
+
+Always write automated test cases in `test/ingestion-api.test.js` before modifying or adding any functional synchronization or endpoint code:
+- **Mandatory Adversarial Testing:** Include adversarial tests covering unauthorized tokens, invalid/missing frontmatter schemas, path traversals in slugs, and malformed base64 asset payloads.
+- **Pre-Presentation Verification:** Run `npm test` and ensure all test cases pass before presenting the final output.
+
+