fix(css): explicit coloration on dark-mode inputs and formalize 'hidden ink' architectural guidelines

Author: Corey B

examples/personal_crm.fdd

@@ -51,7 +51,7 @@
         .main-panel h2 { color: #0f172a; margin-top: 0; }
 
         form { display: flex; flex-direction: column; gap: 15px; max-width: 400px; margin-top: 20px; }
-        input, textarea { padding: 10px; border: 1px solid #cbd5e1; border-radius: 6px; font-family: sans-serif; background: #fdfdfd;}
+        input, textarea { padding: 10px; border: 1px solid #cbd5e1; border-radius: 6px; font-family: sans-serif; background: #fdfdfd; color: #0f172a;}
         textarea { resize: vertical; }
         .btn-submit { background: #10b981; color: white; padding: 12px; font-size: 1rem; }
 

spec/SPEC.md

@@ -43,5 +43,14 @@ An `.fdd` file acts as its own state database. Updates to the DOM natively sync
 
 ## 4. No-JS Security Model
 Since executable scripts are blocked, interactions scale through:
-*   **Declarative Binding:** The underlying `FDD.js` parser maps JSON to `{{mustache}}` template targets.
-*   **CSS Logic:** Advanced interactions (filtering, charting) use `CSS Grid`, `:has()`, `:checked`, and `:contains()` constructs.
+*   **CSS Pseudo Types:** Hover actions, transitions, toggle elements (`:checked`).
+*   **Declarative Extensions:** Custom native UI parsers implementing explicit handlers like `[autosave]` or `[fdd-push]`.
+
+### 4.1 The "Hidden Ink" Presentation Risk
+Because OpenFDD relies on declarative CSS for structural templating, there exists an inherent UI spoofing vector (e.g., matching text color to background color or using `display: none` to conceal contractual terms from the reader). 
+
+To proactively mitigate this, OpenFDD formally separates the **Integrity Layer** (`#fdd-data`) from the **Presentation Layer** (`<template>`). 
+*   Authoritative `.fdd` viewers, parsing libraries, and browser extensions **SHOULD** proactively implement accessibility contrast safeguards (evaluating stylesheets to prevent exact background-hex mappings), OR they must provide a baseline "Raw Data Inspector" UI. This guarantees users can definitively read the pristine, un-styled JSON presentation block.
+*   If a discrepancy arises between the layout masking and the JSON block, the guiding principle of the specification dictates: **The Presentation is merely a convenience; the raw cryptographically signed data block remains the indisputable source of truth.**
+
+## 5. Deployment Ecosystem