prizmkit 1.1.39 → 1.1.41

package/bundled/dev-pipeline/templates/sections/phase-deploy-verification.md

@@ -1,31 +0,0 @@
-### Local Deploy Verification
-
-You just implemented this feature — you know the project's tech stack and build tools.
-
-1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
-2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
-3. **Assess and record** — append to context-snapshot.md:
-   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
-   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
-   - **Cannot build locally** (missing system-level deps you cannot install) → Record: `## Deploy Verification: PARTIAL — missing system deps (see below)`
-
-Deploy verification does NOT block the commit, but you MUST attempt it.
-
-**Smoke test** (only if build passed and project can be started):
-1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
-2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
-3. Stop the server process you started — do NOT leave it running
-4. Record smoke test results in `## Deploy Verification` section
-
-If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
-
-**Deploy documentation update** — Run `/prizmkit-deploy` ONLY if this feature introduced new infrastructure or deployment-affecting changes:
-- New database, cache, message queue, or external service dependency
-- New environment variables required
-- New build steps or deployment configuration (Dockerfile, CI/CD, cloud config)
-- Changed ports, protocols, or service topology
-
-If none of the above apply (pure application logic change), skip `/prizmkit-deploy`.
-
-
-**Checkpoint update**: Update `workflow-checkpoint.json` — set step `deploy-verification` to `"completed"`.

package/bundled/skills/prizmkit-deploy/assets/deploy-template.md

@@ -1,187 +0,0 @@
-# Deployment Guide: [PROJECT_NAME]
-<!-- Replace [PROJECT_NAME] with: name from package.json, or the project root directory name -->
-
-> Generated by PrizmKit Deploy
-
-## Prerequisites
-
-| Tool | Version | Install |
-|------|---------|---------|
-| [tool] | [version] | [install command or link] |
-
-## Environment Variables
-
-| Variable | Required | Description | Default | Example |
-|----------|----------|-------------|---------|---------|
-| [VAR_NAME] | yes/no | [Purpose] | [default or n/a] | [example value] |
-
-**Setup:**
-```bash
-cp .env.example .env
-# Edit .env with your values
-```
-
-## Local Development
-
-### First-time Setup
-```bash
-# [Clone + install steps]
-```
-
-### Run Locally
-```bash
-# [Start command]
-```
-
-### Local Services
-<!-- If docker-compose or similar is used for local dependencies -->
-```bash
-# [Local services startup]
-```
-
-## Database Setup
-<!-- Skip if project does not use a database -->
-
-### Database Type
-[PostgreSQL / MySQL / MongoDB / SQLite / etc.]
-
-### Initial Setup
-```bash
-# [Database creation commands]
-# [Initial migration or schema setup]
-```
-
-### Run Migrations
-```bash
-# [Migration command, e.g., npx prisma migrate deploy, alembic upgrade head]
-```
-
-### Seed Data
-```bash
-# [Seed command if applicable, or "No seed data configured"]
-```
-
-### Database Conventions
-<!-- Auto-populated from CLAUDE.md ### Infrastructure → #### Database -->
-<!-- Filled progressively: basic info from prizmkit-init, detailed conventions from app-planner, verified by prizmkit-deploy -->
-- Table naming: [convention]
-- Migration directory: [path]
-- Migration naming: [rule]
-
-## Testing
-
-### Run Tests
-```bash
-# [Test commands]
-```
-
-### Staging / Pre-production
-<!-- How to test against a staging environment -->
-- Staging URL: [URL or "not configured"]
-- Deploy to staging: [command or process]
-
-## Build
-
-```bash
-# [Build command]
-```
-
-**Output:** [where build artifacts go, e.g. `dist/`, `build/`, binary path]
-
-## Production Deployment
-
-### Deployment Method
-<!-- Filled from deploy_strategy in config -->
-[Description of production deployment approach]
-
-### Step-by-step
-1. [Step 1]
-2. [Step 2]
-3. [Step 3]
-
-### Post-deployment Verification
-```bash
-# [Health check or smoke test command]
-```
-
-## CI/CD
-<!-- Skip if no CI/CD config detected -->
-
-| Pipeline | Trigger | Action |
-|----------|---------|--------|
-| [pipeline name] | [trigger event] | [what it does] |
-
-## Rollback
-
-### How to Rollback
-1. [Rollback step 1]
-2. [Rollback step 2]
-
-### When to Rollback
-- [Criteria that warrant a rollback]
-
-## Health Check
-
-| Check | Endpoint / Command | Expected Result |
-|-------|-------------------|-----------------|
-| [check name] | [endpoint or command] | [expected output] |
-
-## Platform-Specific Deploy Commands
-<!-- Auto-populated based on deployment target from CLAUDE.md ### Infrastructure → #### Deployment -->
-<!-- Filled progressively: basic target from prizmkit-init, detailed config from app-planner, verified by prizmkit-deploy -->
-
-### [Platform Name]
-```bash
-# Pre-flight
-[version check command]
-[auth check command]
-
-# Deploy
-[deploy command]
-
-# Verify
-[post-deploy verification command]
-```
-
-## AI Deploy Playbook
-<!-- Used by prizmkit-deploy Phase 4 when AI-assisted deploy is enabled -->
-<!-- This section is auto-generated — do not edit manually unless you want to customize the sequence -->
-
-### Pre-flight Checklist
-- [ ] CLI tool installed: [tool name + version command]
-- [ ] Authentication verified: [auth check command or "logged in via [method]"]
-- [ ] Environment variables set: [list of required env vars for deployment]
-- [ ] Build successful: [build command]
-
-### Command Sequence
-<!-- Ordered list of commands AI will execute step-by-step with user confirmation -->
-1. `[command 1]` — [what it does]
-2. `[command 2]` — [what it does]
-3. `[command 3]` — [what it does]
-
-### Post-Deploy Verification
-- [ ] Health check: [command or URL]
-- [ ] Smoke test: [manual or automated check]
-
-### Rollback (if deploy fails)
-```bash
-# [Rollback command specific to the platform]
-```
-
-## Deployment Credentials Reference
-<!-- This information is stored in CLAUDE.md / CODEBUDDY.md ### Infrastructure → #### Deployment Credentials Reference -->
-<!-- Listed here for quick reference during deployment execution -->
-
-| Platform | Auth Method | Location |
-|----------|------------|----------|
-| [platform] | [method, e.g., API token, SSH key, CLI login] | [where stored, e.g., VERCEL_TOKEN env var] |
-
-## Troubleshooting
-
-| Symptom | Cause | Fix |
-|---------|-------|-----|
-| [symptom] | [likely cause] | [resolution steps] |
-
-## TODO
-<!-- Auto-generated: items that need manual attention -->
-- [ ] [items prizmkit-deploy could not auto-fill]