esedre 1.0.0 → 1.0.1

package/CHANGELOG.md

@@ -5,6 +5,15 @@ All notable changes to Esedre are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.1] - 2026-09-28
+
+### Added
+- **Public Open-Source Readiness & Repository Sanitization**:
+  - Decoupled and gitignored local development tunnel credentials and endpoint configurations (`tools/tunnel/config.yml`), providing `tools/tunnel/config.yml.example` reference template for public contributors.
+  - Dynamically resolve Vite allowed hostnames (`resolveAllowedHosts`) from local tunnel configurations and `ESEDRE_ALLOWED_HOSTS` environment variable, eliminating hardcoded domains.
+  - Dynamically resolve development build artifact bridge destinations (`scripts/bridge.js`) via local gitignored `.bridge-dest` file or `ESEDRE_BRIDGE_DEST` environment variable.
+  - Genericized documentation, agent skills, and built-in skill templates (`AGENTS.md`, `esedre_storage_engine`, `src/upgrade.ts`) to eliminate proprietary repository paths and internal domain references.
+
 ## [1.0.0] - 2026-09-27
 
 ### Added
@@ -69,7 +78,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 - **Smart npm Publish Lifecycle Wrapper (`npm run pub`)**: Upfront authentication pre-check (`npm whoami`) with automatic interactive login before compilation, executing full prepublish test/lint/build lifecycle.
-- **Multi-Layer Zero-Crawl Protection**: Edge and Vite middleware security preventing search spiders and AI crawler cataloging on development tunnels (`esedre.aroomwithamoose.com`).
+- **Multi-Layer Zero-Crawl Protection**: Edge and Vite middleware security preventing search spiders and AI crawler cataloging on development Cloudflare tunnels.
 - **Canonical Apex Ecosystem Links**: Standardized all portfolio ecosystem references to canonical apex `https://arwam.com`.
 
 ## [0.1.8] - 2026-09-11

package/dist/esedre.mjs

@@ -10,7 +10,7 @@ import path3 from "node:path";
 import os2 from "node:os";
 
 // src/types.ts
-var CURRENT_ESEDRE_VERSION = "1.0.0";
+var CURRENT_ESEDRE_VERSION = "1.0.1";
 var INVERSE_RELATIONS = {
   "relates-to": "relates-to",
   "blocks": "blocked-by",
@@ -4583,7 +4583,7 @@ If the host application declares any or all of the 12 core design tokens on \`:r
 - **Never delete tickets** directly via filesystem.
 - **Workspace Scoping**: An LLM coding partner operates strictly within the authorized project scope declared in the local repository configuration. Central repository linking and system-level configuration are managed separately; focus roadmap work, implementation plans, and verification notes on this project.
 - **Secret Developer Hash Route (\`#/planner\`, \`#/plan\`, \`#planner\`, \`#plan\`)**:
-  - In web applications embedding Esedre (such as Professor Arwam), \`#/planner\` and \`#/plan\` serve as direct secret developer entry routes.
+  - In web applications embedding Esedre (such as your host web app), \`#/planner\` and \`#/plan\` serve as direct secret developer entry routes.
   - **SEO Invariant**: These developer routes are private and MUST NEVER be exposed in \`sitemap.xml\`, \`robots.txt\`, \`llms.txt\`, or public navigation links.
   - The URL hash is preserved across hard page refreshes (F5) without falling back to \`#/chat\` or other views.
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "esedre",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Esedre: Developer roadmap, ticketing, and LLM coding partner coordination platform",
   "homepage": "https://esedre.com",
   "repository": {