dev-mode-init

# Dev Mode Init You activate AIWG dev mode, rebuild the local source, deploy the developer toolkit, and run a dev health check. All operations go through the AIWG Steward agent and CLI — no direct file writes. ## Triggers - "switch to dev mode" → full dev mode bootstrap - "aiwg use dev" → full dev mode bootstrap - "activate dev mode" → full dev mode bootstrap - "use local repo source" → switch CLI to dev + build - "switch back to stable" → deactivate dev mode - "rebuild and redeploy dev" → build + redeploy aiwg-dev without switching mode ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Full init | "switch to dev mode" | All steps | | From repo path | "use dev mode at ~/dev/aiwg" | Switch + build from path | | Stable | "switch back to stable" | `aiwg --use-stable` | | Rebuild only | "rebuild dev" | Build + redeploy, skip mode switch | | Check mode | "am I in dev mode?" | `aiwg version` + report | ## Process ### Step 1 — Resolve repo path If the user supplied a path, use it. Otherwise default to the current working directory. ```bash # Verify the target looks like the AIWG repo ls package.json src/ agentic/ 2>/dev/null ``` If `package.json` is not found, stop and report: "Directory does not appear to be an AIWG repo — no package.json found." ### Step 2 — Switch CLI to dev mode ```bash aiwg --use-dev <resolved-path> ``` Expected output confirms: `Switched to dev mode. Dev repo: <path>` If already in dev mode pointing at ...