@tamyla/clodo-framework 4.5.0 → 4.6.0

package/dist/validation/configSchemas.js

@@ -0,0 +1,236 @@
+/**
+ * Configuration File Schemas
+ * Zod schemas for all CLI config file types (--config-file)
+ * 
+ * Builds on existing infrastructure:
+ * - service-schema-config.js for canonical serviceTypes/features enums
+ * - payloadValidation.js patterns for validation style
+ * 
+ * Supported config types:
+ * - create: Service creation configuration
+ * - deploy: Deployment configuration
+ * - validate: Validation configuration
+ * - update: Service update configuration
+ */
+
+import { z } from 'zod';
+import { getConfig } from '../config/service-schema-config.js';
+
+// ─── Reusable Schema Components ──────────────────────────────────────────────
+
+const EnvironmentSchema = z.enum(['development', 'staging', 'production']).optional();
+const CloudflareCredentialsSchema = z.object({
+  token: z.string().optional(),
+  accountId: z.string().optional(),
+  zoneId: z.string().optional()
+}).optional();
+const DomainSchema = z.string().regex(/^([a-z0-9]+(-[a-z0-9]+)*\.)+[a-z]{2,}$/, 'Must be a valid domain name (e.g., api.example.com)').optional();
+
+// ─── Create Config Schema ────────────────────────────────────────────────────
+
+export const CreateConfigSchema = z.object({
+  // Core fields
+  projectName: z.string().min(1, 'projectName is required').optional(),
+  serviceName: z.string().min(3, 'serviceName must be at least 3 characters').max(50, 'serviceName must be at most 50 characters').regex(/^[a-z0-9-]+$/, 'serviceName must be lowercase letters, numbers and hyphens only').optional(),
+  serviceType: z.string().refine(v => getConfig().serviceTypes.includes(v), {
+    message: `Invalid serviceType. Use one of: ${getConfig().serviceTypes.join(', ')}`
+  }).optional(),
+  description: z.string().max(500, 'description must be at most 500 characters').optional(),
+  domain: DomainSchema,
+  domainName: DomainSchema,
+  // Environment and infrastructure
+  environment: EnvironmentSchema,
+  region: z.string().optional(),
+  template: z.string().optional(),
+  typescript: z.boolean().optional(),
+  outputPath: z.string().optional(),
+  templatePath: z.string().optional(),
+  middlewareStrategy: z.enum(['contract', 'legacy']).optional(),
+  // Features
+  features: z.array(z.string().refine(v => getConfig().features.includes(v), {
+    message: `Invalid feature. Use one of: ${getConfig().features.join(', ')}`
+  })).optional(),
+  // Credentials
+  cloudflareToken: z.string().optional(),
+  cloudflareAccountId: z.string().optional(),
+  cloudflareZoneId: z.string().optional(),
+  // Advanced options
+  advanced: z.object({
+    customRoutes: z.boolean().optional(),
+    workerType: z.string().optional(),
+    compatibilityDate: z.string().regex(/^\d{4}-\d{2}-\d{2}$/, 'Must be YYYY-MM-DD format').optional(),
+    compatibilityFlags: z.array(z.string()).optional()
+  }).passthrough().optional(),
+  // Metadata
+  metadata: z.object({
+    author: z.string().optional(),
+    version: z.string().optional(),
+    tags: z.array(z.string()).optional()
+  }).passthrough().optional()
+}).passthrough().describe('Configuration for clodo create command');
+
+// ─── Deploy Config Schema ────────────────────────────────────────────────────
+
+export const DeployConfigSchema = z.object({
+  // Core fields
+  domain: DomainSchema,
+  serviceName: z.string().optional(),
+  servicePath: z.string().optional(),
+  environment: EnvironmentSchema,
+  // Credentials (can also use env vars)
+  cloudflareToken: z.string().optional(),
+  cloudflareAccountId: z.string().optional(),
+  cloudflareZoneId: z.string().optional(),
+  token: z.string().optional(),
+  accountId: z.string().optional(),
+  zoneId: z.string().optional(),
+  // Deployment options
+  dryRun: z.boolean().optional(),
+  force: z.boolean().optional(),
+  skipDoctor: z.boolean().optional(),
+  doctorStrict: z.boolean().optional(),
+  // Deployment strategy
+  deployment: z.object({
+    strategy: z.enum(['direct', 'blue-green', 'canary', 'rolling']).optional(),
+    replicas: z.number().int().min(1).max(100).optional(),
+    timeout: z.number().int().min(1000).optional(),
+    healthCheckPath: z.string().optional(),
+    healthCheckTimeout: z.number().int().min(1000).optional()
+  }).passthrough().optional(),
+  // Routing configuration
+  routing: z.object({
+    customDomains: z.array(z.string()).optional(),
+    routes: z.array(z.string()).optional(),
+    fallback: z.string().optional()
+  }).passthrough().optional(),
+  // Monitoring
+  monitoring: z.object({
+    enabled: z.boolean().optional(),
+    healthCheck: z.boolean().optional(),
+    alerting: z.boolean().optional(),
+    metricsEndpoint: z.string().optional()
+  }).passthrough().optional(),
+  // Security
+  security: z.object({
+    headers: z.record(z.string(), z.string()).optional(),
+    cors: z.boolean().optional(),
+    rateLimit: z.number().int().optional(),
+    waf: z.boolean().optional()
+  }).passthrough().optional()
+}).passthrough().describe('Configuration for clodo deploy command');
+
+// ─── Validate Config Schema ─────────────────────────────────────────────────
+
+export const ValidateConfigSchema = z.object({
+  // Core fields
+  environment: EnvironmentSchema,
+  servicePath: z.string().optional(),
+  deepScan: z.boolean().optional(),
+  exportReport: z.string().optional(),
+  // Checks to run
+  checks: z.object({
+    structure: z.boolean().optional(),
+    configuration: z.boolean().optional(),
+    dependencies: z.boolean().optional(),
+    security: z.boolean().optional(),
+    performance: z.boolean().optional()
+  }).passthrough().optional(),
+  // Validation rules
+  validation: z.object({
+    strictMode: z.boolean().optional(),
+    ignoreWarnings: z.boolean().optional(),
+    customRules: z.array(z.string()).optional(),
+    excludePaths: z.array(z.string()).optional()
+  }).passthrough().optional(),
+  // Requirements
+  requirements: z.object({
+    minNodeVersion: z.string().optional(),
+    requiredFiles: z.array(z.string()).optional(),
+    requiredDependencies: z.array(z.string()).optional()
+  }).passthrough().optional(),
+  // Reporting
+  reporting: z.object({
+    format: z.enum(['json', 'text', 'html', 'markdown']).optional(),
+    outputFile: z.string().optional(),
+    verbose: z.boolean().optional(),
+    includeTimestamps: z.boolean().optional()
+  }).passthrough().optional()
+}).passthrough().describe('Configuration for clodo validate command');
+
+// ─── Update Config Schema ────────────────────────────────────────────────────
+
+export const UpdateConfigSchema = z.object({
+  // Core fields
+  domain: DomainSchema,
+  environment: EnvironmentSchema,
+  cloudflareToken: z.string().optional(),
+  servicePath: z.string().optional(),
+  // Behavior flags
+  preview: z.boolean().optional(),
+  force: z.boolean().optional(),
+  interactive: z.boolean().optional(),
+  // What to update
+  updates: z.object({
+    updateDependencies: z.boolean().optional(),
+    updateConfiguration: z.boolean().optional(),
+    updateScripts: z.boolean().optional(),
+    updateWorkerConfig: z.boolean().optional()
+  }).passthrough().optional(),
+  // Migration settings
+  migration: z.object({
+    runMigrations: z.boolean().optional(),
+    backupBeforeUpdate: z.boolean().optional(),
+    backupLocation: z.string().optional(),
+    rollbackOnError: z.boolean().optional()
+  }).passthrough().optional(),
+  // Validation settings
+  validation: z.object({
+    validateBeforeUpdate: z.boolean().optional(),
+    validateAfterUpdate: z.boolean().optional(),
+    runTests: z.boolean().optional()
+  }).passthrough().optional(),
+  // Notification settings
+  notification: z.object({
+    notifyOnStart: z.boolean().optional(),
+    notifyOnComplete: z.boolean().optional(),
+    notifyEmail: z.string().email('Must be a valid email address').optional(),
+    notifySlack: z.boolean().optional(),
+    slackWebhook: z.union([z.string().url('Must be a valid URL'), z.literal('')]).optional()
+  }).passthrough().optional(),
+  // Performance settings
+  performance: z.object({
+    parallelUpdates: z.number().int().min(1).max(10).optional(),
+    timeout: z.number().int().min(1000).optional(),
+    retryOnFailure: z.boolean().optional(),
+    maxRetries: z.number().int().min(0).max(10).optional()
+  }).passthrough().optional()
+}).passthrough().describe('Configuration for clodo update command');
+
+// ─── Schema Registry ─────────────────────────────────────────────────────────
+
+/**
+ * Registry mapping command types to their Zod schemas
+ */
+export const CONFIG_SCHEMAS = {
+  create: CreateConfigSchema,
+  deploy: DeployConfigSchema,
+  validate: ValidateConfigSchema,
+  update: UpdateConfigSchema
+};
+
+/**
+ * Get the schema for a given command type
+ * @param {string} commandType - Command type (create, deploy, validate, update)
+ * @returns {z.ZodObject|null} Zod schema or null if not found
+ */
+export function getConfigSchema(commandType) {
+  return CONFIG_SCHEMAS[commandType] || null;
+}
+
+/**
+ * Get all registered command types
+ * @returns {string[]} Array of command type names
+ */
+export function getRegisteredConfigTypes() {
+  return Object.keys(CONFIG_SCHEMAS);
+}

package/dist/validation/index.js

@@ -1,6 +1,10 @@
 /**
  * Clodo Framework - Validation Module
- * Payload validation and parameter discovery
+ * Payload validation, parameter discovery, and config schema validation
  */
 
-export { validateServicePayload, getAcceptedParameters, getParameterDefinitions } from './payloadValidation.js';
+export { validateServicePayload, getAcceptedParameters, getParameterDefinitions } from './payloadValidation.js';
+
+// Config schema validation
+export { ConfigSchemaValidator } from './ConfigSchemaValidator.js';
+export { CreateConfigSchema, DeployConfigSchema, ValidateConfigSchema, UpdateConfigSchema, CONFIG_SCHEMAS, getConfigSchema, getRegisteredConfigTypes } from './configSchemas.js';

package/docs/00_START_HERE.md

@@ -45,8 +45,20 @@ const result = await createService({
 ### 3. **CLI** (Interactive)
 
 ```bash
+# Create a new service
 npx clodo-service create
-# Follow the interactive prompts
+
+# Deploy a service
+npx clodo-service deploy
+
+# Run preflight health checks
+npx clodo-service doctor
+
+# Scan for leaked secrets
+npx clodo-service secrets scan
+
+# Validate config files against schemas
+npx clodo-service config-schema validate clodo-deploy.json
 ```
 
 ## 🔧 Core Concepts
@@ -75,6 +87,17 @@ npx clodo-service create
 | **[Migration Guide](MIGRATION.md)** | CLI to programmatic | Upgrading existing code |
 | **[Error Reference](errors.md)** | Error codes & solutions | Troubleshooting |
 | **[Simple API Guide](SIMPLE_API_GUIDE.md)** | Quick examples | Getting started |
+| **[Security](SECURITY.md)** | Security features & secret scanning | Security review |
+
+## 🩺 Validate Your Setup
+
+Before deploying, run the doctor command to check your environment:
+
+```bash
+npx clodo-service doctor
+```
+
+This checks Node.js version, dependencies, environment variables, Cloudflare connectivity, config schemas, and secret baselines.
 
 ## 🛠️ Development Workflow
 
@@ -179,346 +202,11 @@ domain: 'api.example.com'
 2. **Try the [Simple API Guide](SIMPLE_API_GUIDE.md)** for examples
 3. **Check the [Programmatic API Guide](api/PROGRAMMATIC_API.md)** for advanced usage
 4. **Review [Security](SECURITY.md)** considerations
+5. **Run `clodo-service doctor`** to validate your environment
+6. **Run `clodo-service secrets scan`** to check for leaked secrets
 
 ---
 
 **Happy coding with Clodo Framework! 🎉**
 
-6. **ARCHITECTURE_CONNECTIONS.md** ⭐ FOR ARCHITECTS
-   - Current architecture diagram
-   - Target architecture diagram
-   - Data flow examples
-   - Dependency graph
-   - Integration examples
-   - Testing strategy
-
-7. **COMPREHENSIVE_ROADMAP.md** ⭐ COMPLETE SPEC
-   - Full project specification
-   - 4-phase breakdown
-   - 14 major tasks
-   - Implementation strategy
-   - Success metrics
-   - File inventory
-
-### Plus: 1 Previously Created
-- **IMPLEMENTATION_AUDIT_COMPLETE.md** (from earlier session)
-  - Detailed audit of current implementation
-  - Proof that all 6 commands are complete
-  - Identified missing 15% (polish work)
-
----
-
-## 🎯 The Complete Todo System
-
-### 15 Actionable Tasks (All Mapped & Connected)
-
-**Phase 1: Standardization** (12-16 hours)
-- ✏️ Task 1.1: StandardOptions class → All commands use same global options
-- ✏️ Task 1.2: OutputFormatter class → Unified output handling
-- ✏️ Task 1.3: ProgressManager class → Consistent spinners/progress
-- ✏️ Task 1.4: ConfigLoader class → JSON configuration support
-
-**Phase 2: Feature Parity** (8-12 hours)
-- ✏️ Task 2.1: Shared utility functions → Eliminate code duplication
-- ✏️ Task 2.2: Error handling & exit codes → Consistency
-- ✏️ Task 2.3: Feature parity → All commands equivalent
-
-**Phase 3: Quality Assurance** (6-10 hours)
-- ✏️ Task 3.1: Integration tests → Test each command
-- ✏️ Task 3.2: Utilities tests → Test shared code
-- ✏️ Task 3.3: E2E scenario tests → Test workflows
-
-**Phase 4: Professional Edition** (4-8 hours)
-- ✏️ Task 4.1: New commands (help, version, login)
-- ✏️ Task 4.2: Advanced logging (file output, log levels)
-- ✏️ Task 4.3: Legacy aliases (backward compatibility)
-
----
-
-## 📊 Comprehensive Coverage
-
-### What's Documented
-
-| Aspect | Documented | Where |
-|--------|-----------|-------|
-| Tasks | ✅ All 15 | ACTIONABLE_TODO_LIST.md |
-| Dependencies | ✅ Complete | ARCHITECTURE_CONNECTIONS.md, TASK_QUICK_REFERENCE.md |
-| Code examples | ✅ 45+ | ACTIONABLE_TODO_LIST.md, ARCHITECTURE_CONNECTIONS.md |
-| Timeline | ✅ 30-48 hrs | EXECUTIVE_SUMMARY.md, TASK_QUICK_REFERENCE.md |
-| Success criteria | ✅ Each phase | ACTIONABLE_TODO_LIST.md, TASK_QUICK_REFERENCE.md |
-| File inventory | ✅ Complete | COMPREHENSIVE_ROADMAP.md, ACTIONABLE_TODO_LIST.md |
-| Test strategy | ✅ Complete | ARCHITECTURE_CONNECTIONS.md, ACTIONABLE_TODO_LIST.md |
-| Architecture | ✅ Detailed | ARCHITECTURE_CONNECTIONS.md |
-| Data flows | ✅ Examples | ARCHITECTURE_CONNECTIONS.md |
-| Troubleshooting | ✅ Guide | ARCHITECTURE_CONNECTIONS.md |
-
-### What's Provided
-
-- ✅ **Step-by-step instructions** for each task
-- ✅ **Code examples** showing implementation
-- ✅ **File lists** (what to create/modify)
-- ✅ **Test coverage requirements** for each piece
-- ✅ **Success criteria** at every phase
-- ✅ **Visual diagrams** (dependency map, architecture)
-- ✅ **Effort estimates** per task (2-4 hours each)
-- ✅ **Timeline breakdown** (week-by-week)
-- ✅ **Risk assessment** (all low/medium risk)
-- ✅ **Before/after examples** (compare old vs new)
-
----
-
-## 🚀 How to Use This System
-
-### 5-Minute Quick Start
-1. Read README_COMPLETE_TODOLIST.md
-2. Pick your role (developer/architect/manager)
-3. Know what to do next
-
-### 30-Minute Overview
-1. Read EXECUTIVE_SUMMARY.md (15 min)
-2. Skim TASK_QUICK_REFERENCE.md (10 min)
-3. Decide: Do all 4 phases or subset?
-
-### 1-Hour Planning
-1. Read EXECUTIVE_SUMMARY.md (15 min)
-2. Read ARCHITECTURE_CONNECTIONS.md (30 min)
-3. Review COMPREHENSIVE_ROADMAP.md (15 min)
-
-### Implementation (Ready to Code)
-1. Open ACTIONABLE_TODO_LIST.md
-2. Start with Task 1.1
-3. Follow step-by-step
-4. Reference ARCHITECTURE_CONNECTIONS.md if stuck
-5. Mark complete, move to next task
-
----
-
-## 📋 At-a-Glance Summary
-
-| Question | Answer | Source |
-|----------|--------|--------|
-| What's missing? | 15% polish work | EXECUTIVE_SUMMARY.md |
-| How much work? | 30-48 hours, 4 weeks | EXECUTIVE_SUMMARY.md |
-| How many tasks? | 15 tasks across 4 phases | ACTIONABLE_TODO_LIST.md |
-| Where to start? | Task 1.1: StandardOptions | ACTIONABLE_TODO_LIST.md |
-| How long per task? | 2-4 hours | ACTIONABLE_TODO_LIST.md |
-| What are the pieces? | 19+ new files | COMPREHENSIVE_ROADMAP.md |
-| How do they fit? | See dependency graph | ARCHITECTURE_CONNECTIONS.md |
-| How to verify? | Success criteria per phase | TASK_QUICK_REFERENCE.md |
-| What's the timeline? | Week-by-week breakdown | TASK_QUICK_REFERENCE.md |
-
----
-
-## ✨ Quality of This System
-
-### Document Quality
-- ✅ Comprehensive (3000+ lines)
-- ✅ Interconnected (documents link to each other)
-- ✅ Visual (diagrams and tables)
-- ✅ Practical (code examples)
-- ✅ Actionable (step-by-step instructions)
-- ✅ Complete (nothing left out)
-
-### Task Quality
-- ✅ Clear objectives (what to build)
-- ✅ Detailed instructions (how to build)
-- ✅ Code examples (what it looks like)
-- ✅ Test requirements (how to verify)
-- ✅ Dependencies (what to do first)
-- ✅ Effort estimates (realistic time)
-
-### System Quality
-- ✅ All pieces connected
-- ✅ No missing information
-- ✅ Multiple entry points (different roles)
-- ✅ Progressive detail (executive → detailed)
-- ✅ Easy to follow (clear structure)
-- ✅ Ready to implement (no research needed)
-
----
-
-## 📁 Files Created Today
-
-All in the root directory of clodo-framework:
-
-```
-README_COMPLETE_TODOLIST.md       ⭐ Start here!
-DOCUMENTATION_INDEX.md             📚 Navigation hub
-EXECUTIVE_SUMMARY.md               👔 For decision makers
-ACTIONABLE_TODO_LIST.md            👨‍💻 For developers
-TASK_QUICK_REFERENCE.md            📊 For tracking
-ARCHITECTURE_CONNECTIONS.md        🏗️ For architects
-COMPREHENSIVE_ROADMAP.md           📋 Complete spec
-
-Plus from earlier session:
-IMPLEMENTATION_AUDIT_COMPLETE.md   ✅ Proof of work
-```
-
----
-
-## 🎓 What You Now Know
-
-### Before This Session
-- All 6 commands are working (v3.1.14)
-- Architecture is sound (modular)
-- Some utilities exist (but underutilized)
-- Tests are passing (39 tests)
-- Still ~15% incomplete
-
-### After This Session
-- ✅ Exactly what 15% is missing
-- ✅ How to fix it (15 specific tasks)
-- ✅ How long it will take (30-48 hours)
-- ✅ The right order to do it (dependency graph)
-- ✅ How to verify it's working (success criteria)
-- ✅ Architecture of the final solution (diagrams)
-- ✅ Code examples for implementation
-- ✅ Test requirements for each piece
-
----
-
-## 🏆 This System Provides
-
-1. **Clarity**: Exactly what's missing and why
-2. **Direction**: Clear 4-phase roadmap
-3. **Details**: Code examples and step-by-step instructions
-4. **Timeline**: Realistic 30-48 hour estimate
-5. **Verification**: Success criteria for each phase
-6. **Confidence**: All pieces mapped and connected
-7. **Flexibility**: Do all 4 phases or subsets
-8. **Accessibility**: Documents for all roles
-
----
-
-## 🎯 Your Next Steps
-
-### Right Now (Choose One)
-- [ ] Read README_COMPLETE_TODOLIST.md (5 min)
-- [ ] Read EXECUTIVE_SUMMARY.md (15 min)
-- [ ] Read DOCUMENTATION_INDEX.md (10 min)
-
-### Short Term (1 hour)
-- [ ] Review TASK_QUICK_REFERENCE.md
-- [ ] Understand the 4 phases
-- [ ] Decide: Do all 4 or subset?
-
-### Implementation (Ready to code)
-- [ ] Open ACTIONABLE_TODO_LIST.md
-- [ ] Start with Task 1.1
-- [ ] Follow the step-by-step guide
-- [ ] Reference other docs as needed
-
----
-
-## ✅ Verification Checklist
-
-Have we delivered?
-
-- [x] Complete todo system documented (19 tasks)
-- [x] All pieces interconnected (documents link to each other)
-- [x] Multiple entry points (for all roles)
-- [x] Code examples (45+ snippets)
-- [x] Test requirements (for each task)
-- [x] Success criteria (for each phase)
-- [x] Effort estimates (per task)
-- [x] Timeline (30-48 hours, 4 weeks)
-- [x] Visual diagrams (dependency, architecture)
-- [x] File inventory (30+ new files)
-- [x] Risk assessment (all low/medium)
-- [x] Release schedule (v3.2.0 → v4.0.0)
-
-**Result**: 🎉 **100% Complete**
-
----
-
-## 🎓 Final Stats
-
-```
-Documentation Created Today:
-  - 7 comprehensive documents
-  - 3000+ lines of content
-  - 45+ code examples
-  - 15 actionable tasks
-  - 4 phases
-  - 30-48 hours of work
-  - All interconnected
-
-Completeness:
-  - Current: 85% (v3.1.14)
-  - Missing: 15% (documented)
-  - After implementation: 100% (v4.0.0)
-
-Testing:
-  - Current: 39 tests passing
-  - Target: 95+ tests passing
-  - Coverage: >90% (from ~70%)
-
-Documentation Quality:
-  - Comprehensive: ✅
-  - Clear: ✅
-  - Actionable: ✅
-  - Complete: ✅
-```
-
----
-
-## 📞 Any Questions?
-
-**Where do I start?**
-→ README_COMPLETE_TODOLIST.md (this document)
-
-**What's the big picture?**
-→ EXECUTIVE_SUMMARY.md (30 min read)
-
-**Show me the tasks**
-→ ACTIONABLE_TODO_LIST.md (detailed guide)
-
-**How do they connect?**
-→ ARCHITECTURE_CONNECTIONS.md (technical deep-dive)
-
-**What's the timeline?**
-→ TASK_QUICK_REFERENCE.md (week-by-week)
-
-**Which document should I read?**
-→ DOCUMENTATION_INDEX.md (navigation hub)
-
-**I'm ready to code, where do I start?**
-→ ACTIONABLE_TODO_LIST.md, Task 1.1
-
----
-
-## 🎉 Success Criteria: Have We Met It?
-
-- ✅ **Comprehensive**: 3000+ lines, all topics covered
-- ✅ **Connected**: All documents link to each other
-- ✅ **Actionable**: Code examples and step-by-step instructions
-- ✅ **Complete**: 15 tasks, all dependencies mapped
-- ✅ **Clear**: Multiple entry points for different roles
-- ✅ **Practical**: Realistic timelines and effort estimates
-- ✅ **Verifiable**: Success criteria for each phase
-- ✅ **Ready**: Can start implementation immediately
-
-**Result**: 🎊 **READY FOR IMPLEMENTATION**
-
----
-
-## 🚀 You Are Ready!
-
-Everything you need to take @tamyla/clodo-framework from v3.1.14 to v4.0.0 is now documented.
-
-**Start with**: README_COMPLETE_TODOLIST.md (you are here!)
-
-**Next**: Pick your role and follow the recommended reading order
-
-**Then**: Choose a task and start coding!
-
-**Timeline**: 4 weeks to complete
-
-**Result**: Professional-grade CLI with zero technical debt
-
----
-
-**Created**: October 28, 2025
-**Status**: ✅ COMPLETE AND READY
-**Next**: Your move! Pick a task and build! 🚀
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tamyla/clodo-framework",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "Reusable framework for Clodo-style software architecture on Cloudflare Workers + D1",
   "type": "module",
   "sideEffects": [