chore: purge legacy prd, properly scope NPM payloads, and inject active Gemini compilation workflow mappings natively

Author: Corey B

PRD-OpenFDD.md

@@ -41,7 +41,7 @@ The OpenFDD ecosystem provides a full suite of typescript/javascript libraries t
 To build an `.fdd` file from your backend, you pack your Cryptographic JSON, your Mutable JSON, and your HTML template securely into the unified `.fdd` document wrapper:
 ```bash
 # Install the Official OpenFDD CLI globally
-npm install -g node-fdd
+npm install -g @coreyburns/node-fdd
 
 # Pack the payload securely into the FDD container
 fdd-pack template.html fdd-data.json user-notes.json output.fdd
@@ -70,6 +70,9 @@ The success of OpenFDD relies entirely on community pushback against static PDFs
 
 **Share the Standard on Social Media:**
 <p align="left">
+  <a href="https://open-fdd.org">
+    <img src="https://img.shields.io/badge/Read%20The%20Web%20Manifesto-002147?style=for-the-badge&logo=read-the-docs&logoColor=white" alt="Read the Manifesto" />
+  </a>
   <a href="https://twitter.com/intent/tweet?text=Stop%20sending%20dead%20PDFs.%20Documents%20should%20be%20data-first,%20not%20pictures%20of%20data.%20Learn%20why%20%23OpenFDD%20and%20Zero-JS%20interactive%20JSON-LD%20containers%20are%20the%20future%20of%20files!%20%20%0A%0A%F0%9F%93%84%20https://github.com/Spuds0588/open-fdd">
     <img src="https://img.shields.io/badge/Share%20on%20X-000000?style=for-the-badge&logo=x&logoColor=white" alt="Share on X" />
   </a>

README.md

@@ -0,0 +1,24 @@
+---
+description: OpenFDD System Version Bumping Workflow
+---
+
+# Updating OpenFDD Versions
+
+As an Agent maintaining the pristine layout of the OpenFDD project, any time we deploy a major logic upgrade that necessitates an `npm publish` or a native `git tag` push affecting CDN endpoints, you MUST execute the following cascade in order to prevent fractured dependency versions:
+
+1. **Update `lib/node-fdd/package.json`**:
+   Ensure `version` is properly bumped matching SEMVER standards (e.g. `"1.2.0"`).
+
+2. **Update the Global `jsDelivr` CDN Maps**:
+   Cross-reference `site/index.html` and `README.md`. You must parse for `cdn.jsdelivr.net/gh/Spuds0588/open-fdd@v[VERSION]` and rigidly adjust that embedded marker in the code so all public instructions route to your brand new release.
+
+3. **Verify the NPM Scoped Install Commands**:
+   Ensure all install code blocks accurately suggest `npm install -g @coreyburns/node-fdd` globally.
+
+4. **Verify The Executables**:
+   If CLI logic logic shifts, ensure `package.json` > `bin` explicitly maps `fdd-pack` and `fdd-sign` pipelines accurately. 
+
+5. **Commit, Tag, and Publish**:
+   - `git add . && git commit -m "chore: bump ecosystem verions"`
+   - Prompt the explicit User to invoke `npm publish --access=public` inside `/lib/node-fdd`.
+   - Prompt the User to issue an official git tag mirroring the release boundary via `git tag v1.x.x` and pushing `git push origin v1.x.x` to force native CDN hydration.

_agents/workflows/version-bump.md

@@ -1,5 +1,5 @@
 {
-  "name": "node-fdd",
+  "name": "@coreyburns/node-fdd",
   "version": "1.1.0",
   "description": "Server-side utility for OpenFDD signing and packing",
   "main": "src/pack.js",

lib/node-fdd/package.json

@@ -125,7 +125,7 @@ <h2>The End of the Static PDF</h2>
                 OpenFDD replaces static, "visual-first" documents with data-first interactive containers. 
                 Our architecture provides documents that are natively human-readable, cryptographically verifiable, and locally persistent without the need for complex infrastructure.
             </p>
-            <a href="https://github.com/open-fdd" class="button">Read the Specification</a>
+            <a href="https://github.com/Spuds0588/open-fdd" class="button">Read the Specification on GitHub</a>
         </section>
 
         <hr>
@@ -178,7 +178,7 @@ <h2>Tooling & Ecosystem Guide</h2>
             <ul class="points-list">
                 <li>
                     <strong>1. Composing & Building (<code>node-fdd</code>)</strong>
-                    To build an `.fdd` file natively on your backend, utilize the official <code>npm install -g node-fdd</code> library. You seamlessly pass your Cryptographic JSON, your Mutable JSON, and your HTML template securely via the <code>fdd-pack</code> CLI pipeline.
+                    To build an `.fdd` file natively on your backend, utilize the official <code>npm install -g @coreyburns/node-fdd</code> library. You seamlessly pass your Cryptographic JSON, your Mutable JSON, and your HTML template securely via the <code>fdd-pack</code> CLI pipeline.
                 </li>
                 <li>
                     <strong>2. Cryptographic Signing</strong>