Updated hooks and steering

Author: phate999

.kiro/hooks/auto-deploy-app.kiro.hook

@@ -1,14 +1,14 @@
 {
   "enabled": true,
   "name": "Auto Deploy on Code Change",
-  "description": "Automatically deploys the SDK app to the router after Kiro finishes making code changes. Uses make.py deploy.",
+  "description": "Automatically deploys the SDK app to the router after Kiro finishes making code changes. Uses .kiro/steering/deploy.md.",
   "version": "1",
   "when": {
     "type": "agentStop"
   },
   "then": {
     "type": "askAgent",
-    "prompt": "If you already ran a deploy this session, do nothing — the app is already deployed. Otherwise, if you created or modified any SDK app Python files during this session, read sdk_settings.ini to get the app_name, then deploy using the correct Python: if .venv exists, use '.venv/Scripts/python make.py deploy <app_name>' on Windows or '.venv/bin/python make.py deploy <app_name>' on Mac/Linux. If no .venv exists, fall back to 'python3 make.py deploy <app_name>' or 'python make.py deploy <app_name>' whichever is available. After the command completes, review the output for errors. Check that log timestamps are AFTER the deploy started. If logs show the app started successfully, report success briefly. If there are errors, diagnose and suggest fixes. If no app code was changed, do nothing."
+    "prompt": "If you already ran a deploy this session, do nothing — the app is already deployed. Otherwise, if you created or modified any SDK app Python files during this session, read .kiro/steering/deploy.md and follow its instructions. Read sdk_settings.ini to get the app_name. If no app code was changed, do nothing."
   },
   "workspaceFolderName": "sdk-samples",
   "shortName": "auto-deploy-app"

.kiro/hooks/setup-dev-env.kiro.hook

@@ -1,12 +1,12 @@
 {
   "name": "Setup Dev Environment",
   "version": "1.0.0",
-  "description": "Creates a Python virtual environment and installs all SDK dependencies from requirements.txt",
+  "description": "Automatically creates a Python virtual environment and installs SDK dependencies if .venv is missing",
   "when": {
-    "type": "userTriggered"
+    "type": "promptSubmit"
   },
   "then": {
     "type": "runCommand",
-    "command": "python3 make.py setup 2>/dev/null || python make.py setup"
+    "command": "test -d .venv || (python3 make.py setup || python make.py setup)"
   }
 }

.kiro/steering/coding-standards.md

@@ -34,7 +34,7 @@ Applications run on Cradlepoint routers using Python 3.8.
 
 ## Local Development (Running on Your Computer)
 
-- **Apps can run locally** - `python3 my_app/my_app.py` runs the app on your computer. cp.py auto-detects it's not on a router and uses HTTP REST to communicate with the dev router specified in `sdk_settings.ini`
+- **Apps can run locally** - `.venv/bin/python my_app/my_app.py` (Mac/Linux) or `.venv\Scripts\python my_app/my_app.py` (Windows) runs the app on your computer. cp.py auto-detects it's not on a router and uses HTTP REST to communicate with the dev router specified in `sdk_settings.ini`
 - **cp.get/put/post/delete work locally** - all API calls route through REST to the dev router
 - **cp.log() prints to stdout locally** - output goes to your terminal instead of syslog
 - **cp.alert() does NOT work locally** - logs the alert text to console but does not send to NCM
@@ -46,8 +46,8 @@ Applications run on Cradlepoint routers using Python 3.8.
 
 ## Python Libraries and Dependencies
 
-- **Install libraries directly to app folder**: `pip3 install -t path/to/app_folder library_name`
-- **Example**: `pip3 install -t gpio_modem_control requests`
+- **Install libraries directly to app folder**: `.venv/bin/pip install -t path/to/app_folder library_name` (Mac/Linux) or `.venv\Scripts\pip install -t path/to/app_folder library_name` (Windows)
+- **Example**: `.venv/bin/pip install -t gpio_modem_control requests` (Mac/Linux) or `.venv\Scripts\pip install -t gpio_modem_control requests` (Windows)
 - **CRITICAL: No .pyc or .so files** - routers only support pure Python (.py) files
 - Libraries are packaged with the app and deployed to the router
 - Keep dependencies minimal - routers have limited storage

.kiro/steering/deploy.md

@@ -6,9 +6,11 @@ description: "Deploy SDK app to Cradlepoint router via make.py deploy (cross-pla
 
 Deploy the SDK app to the router:
 
-```bash
-python3 make.py deploy {app_name}
-```
+1. Read `sdk_settings.ini` to get the `app_name`
+2. Run the deploy command:
+
+- Windows: `.venv\Scripts\python make.py deploy {app_name}`
+- Mac/Linux: `.venv/bin/python make.py deploy {app_name}`
 
 This will:
 1. Purge all apps from router
@@ -18,4 +20,4 @@ This will:
 
 After deployment, verify the app started successfully by checking the logs.
 
-**Note:** Ensure sdk_settings.ini has correct router IP and credentials before deploying.
+**Note:** Before deploying, read `sdk_settings.ini` and check that `dev_client_password` is not the default `mypassword`. If it is, open `sdk_settings.ini` and tell the user to update it with their router credentials before proceeding.

.kiro/steering/learn.md

@@ -35,7 +35,10 @@ description: "Review learnings and update rules and documentation"
 ## Explore APIs before documenting:
 
 ```bash
-python3 docs/ncos-api/explore_status.py status/wan/devices
+# Mac/Linux:
+.venv/bin/python docs/ncos-api/explore_status.py status/wan/devices
+# Windows:
+.venv\Scripts\python docs/ncos-api/explore_status.py status/wan/devices
 ```
 
 This shows the ACTUAL API response with all fields - use it to verify structures before updating docs.

.kiro/steering/rtfm.md

@@ -11,8 +11,8 @@ description: "API verification workflow — read docs before writing API code"
 1. **STOP** - Do NOT assume fields exist
 2. **SEARCH docs FIRST**: `grep -r "keyword" docs/ncos-api/ --include="*.md"`
 3. **READ relevant docs** - Understand proper usage patterns and examples
-4. **CHECK DTD**: `curl -s -u admin:pass http://router/api/dtd/config/path | python3 -m json.tool`
-5. **TEST with curl**: `curl -s -u admin:pass http://router/api/status/path | python3 -m json.tool`
+4. **CHECK DTD**: `curl -s -u admin:pass http://router/api/dtd/config/path | .venv/bin/python -m json.tool` (Mac/Linux) or `curl -s -u admin:pass http://router/api/dtd/config/path | .venv\Scripts\python -m json.tool` (Windows)
+5. **TEST with curl**: `curl -s -u admin:pass http://router/api/status/path | .venv/bin/python -m json.tool` (Mac/Linux) or `curl -s -u admin:pass http://router/api/status/path | .venv\Scripts\python -m json.tool` (Windows)
 6. **VERIFY fields** - Only use fields that actually exist in the response
 7. **THEN code** - Write code based on verified, documented structure
 

.kiro/steering/setup.md

@@ -4,8 +4,6 @@ inclusion: always
 
 # Dev Environment Check
 
-If the user asks to build, deploy, or run an app and `.venv` does not exist in the workspace root, do NOT auto-run setup. Instead, let the user know:
+The `check-venv` hook automatically runs `make.py setup` if `.venv` is missing at the start of every prompt. No manual intervention needed.
 
-> It looks like the Python environment hasn't been set up yet. Click the Kiro ghost icon in the sidebar and run the **Setup Dev Environment** hook, then try again.
-
-Do not mention this if `.venv` already exists.
+If setup fails, let the user know they can also run the **Setup Dev Environment** hook manually from the Kiro sidebar.

.kiro/steering/workflow.md

@@ -16,7 +16,9 @@ This prevents the "code first, debug later" cycle. Start a spec with: "Create a
 
 ## Python Environment
 
-Use `python3` for all commands.
+Use the project's virtual environment for all commands:
+- Windows: `.venv\Scripts\python make.py ...`
+- Mac/Linux: `.venv/bin/python make.py ...`
 
 ## Saved Prompt Shortcuts
 
@@ -28,9 +30,8 @@ Use `python3` for all commands.
 
 **ALWAYS deploy after creating or modifying an app.** After any code change to an app's Python files, automatically run:
 
-```bash
-python3 make.py deploy {app_name}
-```
+- Windows: `.venv\Scripts\python make.py deploy {app_name}`
+- Mac/Linux: `.venv/bin/python make.py deploy {app_name}`
 
 Do NOT ask the user if they want to deploy — just do it.
 
@@ -69,7 +70,10 @@ app_name/
 ## Create App
 
 ```bash
-python3 make.py create {app_name}
+# Windows:
+.venv\Scripts\python make.py create {app_name}
+# Mac/Linux:
+.venv/bin/python make.py create {app_name}
 ```
 
 This generates all required files from app_template (package.ini, start.sh, cp.py, {app_name}.py, readme.md).
@@ -90,11 +94,11 @@ This generates all required files from app_template (package.ini, start.sh, cp.p
 
 **NEVER overwrite package.ini, start.sh, or cp.py after creation** - these are auto-generated and correct.
 
-**ALWAYS deploy after creating or modifying an app** - use `python3 make.py deploy {app_name}` immediately after code changes.
+**ALWAYS deploy after creating or modifying an app** - use `.venv/bin/python make.py deploy {app_name}` (Mac/Linux) or `.venv\Scripts\python make.py deploy {app_name}` (Windows) immediately after code changes.
 
 ## Deploy to Router
 
-**ALWAYS use make.py deploy** - `python3 make.py deploy {app_name}`
+**ALWAYS use make.py deploy** - `.venv/bin/python make.py deploy {app_name}` (Mac/Linux) or `.venv\Scripts\python make.py deploy {app_name}` (Windows)
 
 This handles:
 - Purging old apps
@@ -103,7 +107,7 @@ This handles:
 - Starting the app (auto_start=true in package.ini)
 - Showing status and logs
 
-**Just run `python3 make.py deploy {app_name}`** - no need to run `make.py clean` or remove old tar.gz files first. It handles everything. The app auto-starts after install, so there's no need to run `make.py start` either.
+**Just run `make.py deploy`** - no need to run `make.py clean` or remove old tar.gz files first. It handles everything. The app auto-starts after install, so there's no need to run `make.py start` either.
 
 **NEVER use make.py install directly** - always use `make.py deploy` for deployment.
 
@@ -114,9 +118,17 @@ This handles:
 ## Other Commands
 
 ```bash
-python3 make.py status {app_name}     # Check app status
-python3 make.py start {app_name}      # Start app
-python3 make.py stop {app_name}       # Stop app
-python3 make.py uninstall {app_name}  # Remove app
-python3 make.py clean {app_name}      # Remove build artifacts
+# Windows:
+.venv\Scripts\python make.py status {app_name}     # Check app status
+.venv\Scripts\python make.py start {app_name}      # Start app
+.venv\Scripts\python make.py stop {app_name}       # Stop app
+.venv\Scripts\python make.py uninstall {app_name}  # Remove app
+.venv\Scripts\python make.py clean {app_name}      # Remove build artifacts
+
+# Mac/Linux:
+.venv/bin/python make.py status {app_name}
+.venv/bin/python make.py start {app_name}
+.venv/bin/python make.py stop {app_name}
+.venv/bin/python make.py uninstall {app_name}
+.venv/bin/python make.py clean {app_name}
 ```