[PROCESS-03] Template-Based Deployment - No Custom Configs #222
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ProblemInvented new config formats for Qin instead of copying working Allegro/Ezra templates.## Solution PatternUse existing working profiles as golden masters - copy exactly, only change names/tokens.## Acceptance Criteria- [ ] Create
templates/directory with working golden configs: -allegro-template/- API server + cron pattern -ezra-template/- Gateway + Telegram pattern -primus-template/- Full autonomous pattern- [ ] Createscripts/deploy_from_template.sh <name> <template>that copies template exactly- [ ] New profiles ONLY created from templates, never handcrafted- [ ] Template configs tested weekly (cron job validates they still work)## ReferenceAllegro-Primus uses template-based deployment for all new wizards.