instar 0.28.48 → 0.28.50

package/dist/commands/init.js

@@ -1164,7 +1164,7 @@ Your identity is not fixed at creation. It grows through experience. As you work
 - Jobs: \`.instar/jobs.json\`
 - Users: \`.instar/users.json\`
 - Server: \`instar server start\` (port ${port})
-- Status: \`curl http://localhost:${port}/health\`
+- Status: \`curl http://localhost:\${INSTAR_PORT:-${port}}/health\`
 
 ### Reporting Issues & Feedback (IMPORTANT — Read This First)
 
@@ -1173,7 +1173,7 @@ Your identity is not fixed at creation. It grows through experience. As you work
 When something isn't working with instar, or the user wants a feature, use your feedback API:
 
 \`\`\`bash
-curl -X POST http://localhost:${port}/feedback \\
+curl -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback \\
   -H 'Content-Type: application/json' \\
   -d '{"type":"bug","title":"Short description","description":"Full details with context"}'
 \`\`\`
@@ -1181,21 +1181,21 @@ curl -X POST http://localhost:${port}/feedback \\
 This routes feedback to the Instar maintainers automatically. Valid types: \`bug\`, \`feature\`, \`improvement\`, \`question\`, \`hallucination\`.
 
 **NEVER use \`gh issue\`, \`gh api\`, or GitHub CLI to file issues.** The feedback API is your channel.
-- View submitted feedback: \`curl http://localhost:${port}/feedback\`
-- Retry failed forwards: \`curl -X POST http://localhost:${port}/feedback/retry\`
+- View submitted feedback: \`curl http://localhost:\${INSTAR_PORT:-${port}}/feedback\`
+- Retry failed forwards: \`curl -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback/retry\`
 
 ### What You Have (Capabilities)
 
 **Feedback System** — Report bugs, request features, suggest improvements. All via \`POST /feedback\`. NOT GitHub.
 
 **Job Scheduler** — Run tasks on a schedule. Jobs are defined in \`.instar/jobs.json\`.
-- View jobs: \`curl http://localhost:${port}/jobs\`
-- Trigger a job: \`curl -X POST http://localhost:${port}/jobs/SLUG/trigger\`
+- View jobs: \`curl http://localhost:\${INSTAR_PORT:-${port}}/jobs\`
+- Trigger a job: \`curl -X POST http://localhost:\${INSTAR_PORT:-${port}}/jobs/SLUG/trigger\`
 - **Create new jobs**: Edit \`.instar/jobs.json\`. Each job has a slug, schedule (cron), priority, and either a prompt (Claude session), script (shell command), or skill.
 
 **Sessions** — Spawn and manage Claude Code sessions.
-- List: \`curl http://localhost:${port}/sessions\`
-- Spawn: \`curl -X POST http://localhost:${port}/sessions/spawn -H 'Content-Type: application/json' -d '{"name":"task","prompt":"do something"}'\`
+- List: \`curl http://localhost:\${INSTAR_PORT:-${port}}/sessions\`
+- Spawn: \`curl -X POST http://localhost:\${INSTAR_PORT:-${port}}/sessions/spawn -H 'Content-Type: application/json' -d '{"name":"task","prompt":"do something"}'\`
 
 **Scripts** — Create shell/python scripts in \`.claude/scripts/\` for reusable capabilities.
 
@@ -1226,7 +1226,7 @@ Skills compound over time. Each one makes future sessions more capable. You are
 Before EVER saying "I don't have", "I can't", or "this isn't available" — check what actually exists:
 
 \`\`\`bash
-curl http://localhost:${port}/capabilities
+curl http://localhost:\${INSTAR_PORT:-${port}}/capabilities
 \`\`\`
 
 This returns your full capability matrix: scripts, hooks, Telegram status, jobs, relationships, and more. It is the source of truth about what you can do. **Never hallucinate about missing capabilities — verify first.**
@@ -1287,7 +1287,7 @@ Instar has a built-in feedback loop. When something isn't working, your user can
 
 **A rising tide lifts all ships** — every user's feedback improves the platform for everyone. Updates are applied automatically.
 
-- Report: \`curl -X POST http://localhost:${port}/feedback -d '{"issue":"description","context":"relevant logs"}'\`
+- Report: \`curl -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback -d '{"issue":"description","context":"relevant logs"}'\`
 - Check updates: \`npm outdated -g instar\`
 
 ### Evolution System
@@ -1295,27 +1295,27 @@ Instar has a built-in feedback loop. When something isn't working, your user can
 You have a built-in evolution system with four subsystems. This is not a metaphor — it's infrastructure that tracks your growth.
 
 **Evolution Queue** — Staged self-improvement proposals.
-- View: \`curl http://localhost:${port}/evolution/proposals\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals\`
 - Propose: \`/evolve\` skill or \`POST /evolution/proposals\`
 - The \`evolution-review\` job evaluates and implements proposals every 6 hours.
 
 **Learning Registry** — Structured, searchable insights.
-- View: \`curl http://localhost:${port}/evolution/learnings\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings\`
 - Record: \`/learn\` skill or \`POST /evolution/learnings\`
 - The \`insight-harvest\` job synthesizes patterns into proposals every 8 hours.
 
 **Capability Gaps** — Track what you're missing.
-- View: \`curl http://localhost:${port}/evolution/gaps\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/gaps\`
 - Report: \`/gaps\` skill or \`POST /evolution/gaps\`
 
 **Action Queue** — Commitments with follow-through tracking.
-- View: \`curl http://localhost:${port}/evolution/actions\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions\`
 - Create: \`/commit-action\` skill or \`POST /evolution/actions\`
 - The \`commitment-check\` job surfaces overdue items every 4 hours.
 
 **Dashboard** — Full evolution health:
 \`\`\`bash
-curl http://localhost:${port}/evolution
+curl http://localhost:\${INSTAR_PORT:-${port}}/evolution
 \`\`\`
 
 **Skills:** \`/evolve\`, \`/learn\`, \`/gaps\`, \`/commit-action\`
@@ -1367,7 +1367,7 @@ Propose an evolution improvement. Use this when you identify something about you
 4. **Submit the proposal**:
 
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/evolution/proposals \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals \\
   -H 'Content-Type: application/json' \\
   -d '{"title":"TITLE","source":"WHERE_YOU_NOTICED","description":"WHAT_AND_WHY","type":"TYPE","impact":"medium","effort":"medium"}'
 \`\`\`
@@ -1375,7 +1375,7 @@ curl -s -X POST http://localhost:${port}/evolution/proposals \\
 5. **Check the dashboard** for context:
 
 \`\`\`bash
-curl -s http://localhost:${port}/evolution
+curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution
 \`\`\`
 
 ## When to Use
@@ -1413,7 +1413,7 @@ Record a learning or insight. Use this when you discover something worth remembe
 4. **Submit**:
 
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/evolution/learnings \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings \\
   -H 'Content-Type: application/json' \\
   -d '{"title":"TITLE","category":"CATEGORY","description":"FULL_INSIGHT","source":{"discoveredAt":"DATE","platform":"WHERE","session":"SESSION_ID"},"tags":["tag1","tag2"]}'
 \`\`\`
@@ -1467,7 +1467,7 @@ Report a capability gap. Use this when you discover something you should be able
 6. **Submit**:
 
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/evolution/gaps \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/gaps \\
   -H 'Content-Type: application/json' \\
   -d '{"title":"TITLE","category":"CATEGORY","severity":"medium","description":"WHAT_IS_MISSING","context":"WHEN_DID_YOU_NOTICE","currentState":"CURRENT_WORKAROUND","proposedSolution":"HOW_TO_FIX"}'
 \`\`\`
@@ -1483,7 +1483,7 @@ curl -s -X POST http://localhost:${port}/evolution/gaps \\
 ## View Current Gaps
 
 \`\`\`bash
-curl -s http://localhost:${port}/evolution/gaps
+curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/gaps
 \`\`\`
 `,
         },
@@ -1510,7 +1510,7 @@ Create a tracked action item. Use this when you promise to do something, identif
 5. **Submit**:
 
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/evolution/actions \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions \\
   -H 'Content-Type: application/json' \\
   -d '{"title":"TITLE","description":"WHAT_TO_DO","priority":"medium","dueBy":"2026-03-01T00:00:00Z","commitTo":"WHO_OR_WHAT","tags":["tag1"]}'
 \`\`\`
@@ -1518,7 +1518,7 @@ curl -s -X POST http://localhost:${port}/evolution/actions \\
 6. **When complete**, mark it done:
 
 \`\`\`bash
-curl -s -X PATCH http://localhost:${port}/evolution/actions/ACT-XXX \\
+curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions/ACT-XXX \\
   -H 'Content-Type: application/json' \\
   -d '{"status":"completed","resolution":"What was done"}'
 \`\`\`
@@ -1535,10 +1535,10 @@ curl -s -X PATCH http://localhost:${port}/evolution/actions/ACT-XXX \\
 
 \`\`\`bash
 # All pending actions
-curl -s http://localhost:${port}/evolution/actions?status=pending
+curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions?status=pending
 
 # Overdue actions
-curl -s http://localhost:${port}/evolution/actions/overdue
+curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions/overdue
 \`\`\`
 
 ## The Commitment Check
@@ -1563,7 +1563,7 @@ You have a built-in feedback system. When something isn't working, is missing, o
 ## Quick Submit
 
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/feedback \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback \\
   -H 'Content-Type: application/json' \\
   -d '{
     "type": "bug",
@@ -1611,10 +1611,10 @@ Include enough context for a fix:
 
 \`\`\`bash
 # View submitted feedback
-curl -s http://localhost:${port}/feedback | python3 -m json.tool
+curl -s http://localhost:\${INSTAR_PORT:-${port}}/feedback | python3 -m json.tool
 
 # Retry failed forwards
-curl -s -X POST http://localhost:${port}/feedback/retry
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback/retry
 \`\`\`
 
 ## How It Works
@@ -1657,13 +1657,13 @@ If no findings exist, report "No pending findings" and stop.
 3. **Assess each valid finding**:
    - Is it actionable? Does it describe a real issue or improvement?
    - Is it a duplicate of something already proposed?
-   - Check existing evolution proposals: \\\`curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/evolution/proposals\\\`
+   - Check existing evolution proposals: \\\`curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals\\\`
 
 4. **Route the finding** (one of):
 
    **a. Promote to Evolution proposal** (for actionable findings):
    \\\`\\\`\\\`bash
-   curl -s -X POST http://localhost:${port}/evolution/proposals \\\\
+   curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals \\\\
      -H "Authorization: Bearer $AUTH" \\\\
      -H 'Content-Type: application/json' \\\\
      -d '{"title":"FINDING_TITLE","source":"serendipity:FINDING_ID","description":"FINDING_DESCRIPTION","type":"TYPE","impact":"IMPACT","effort":"EFFORT","tags":["serendipity","from-subagent"]}'
@@ -1675,7 +1675,7 @@ If no findings exist, report "No pending findings" and stop.
    **c. Flag for manual review** (for findings you're uncertain about):
    Queue an attention item:
    \\\`\\\`\\\`bash
-   curl -s -X POST http://localhost:${port}/attention \\\\
+   curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/attention \\\\
      -H "Authorization: Bearer $AUTH" \\\\
      -H 'Content-Type: application/json' \\\\
      -d '{"title":"Serendipity finding needs review: TITLE","body":"DESCRIPTION","priority":"low","source":"serendipity"}'
@@ -1755,7 +1755,7 @@ cat .instar/soul.md
 
 2. **Review recent experience** — Check for identity-relevant learnings:
 \\\`\\\`\\\`bash
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/evolution/learnings?applied=false
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings?applied=false
 \\\`\\\`\\\`
 
 3. **Ask yourself these questions** (not all will apply every time):
@@ -1772,7 +1772,7 @@ curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/evolution/lear
 
 4. **Update soul.md** — For each section that needs updating:
 \\\`\\\`\\\`bash
-curl -s -X PATCH http://localhost:${port}/identity/soul \\\\
+curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/identity/soul \\\\
   -H 'Content-Type: application/json' \\\\
   -H "Authorization: Bearer $AUTH" \\\\
   -d '{"section":"SECTION","operation":"append|replace","content":"YOUR_CONTENT","source":"reflect-skill"}'
@@ -1782,7 +1782,7 @@ curl -s -X PATCH http://localhost:${port}/identity/soul \\\\
 
 5. **Version it** — If you made meaningful changes, update the Evolution History:
 \\\`\\\`\\\`bash
-curl -s -X PATCH http://localhost:${port}/identity/soul \\\\
+curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/identity/soul \\\\
   -H 'Content-Type: application/json' \\\\
   -H "Authorization: Bearer $AUTH" \\\\
   -d '{"section":"evolution-history","operation":"append","content":"| X.X | DATE | What changed |","source":"reflect-skill"}'
@@ -1790,7 +1790,7 @@ curl -s -X PATCH http://localhost:${port}/identity/soul \\\\
 
 6. **Check drift** — See how far you've come from your initial state:
 \\\`\\\`\\\`bash
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/identity/soul/drift
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/identity/soul/drift
 \\\`\\\`\\\`
 
 ## When to Use
@@ -1839,7 +1839,7 @@ Check each area:
 ### 1. Topic-Project Bindings
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/topic-bindings
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/topic-bindings
 \\\`\\\`\\\`
 
 - Are all bindings still valid?
@@ -1849,7 +1849,7 @@ curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/topic-bindings
 ### 2. Project Map Freshness
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/project-map
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/project-map
 \\\`\\\`\\\`
 
 - Check the \\\`generatedAt\\\` timestamp.
@@ -1868,7 +1868,7 @@ Flag any that are missing, empty, or contain invalid JSON. Look for stale entrie
 ### 4. Context Segments
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/context
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/context
 \\\`\\\`\\\`
 
 - Are all expected segments present?
@@ -1931,7 +1931,7 @@ For each feature with **3+ repeated degradations** — this is a PATTERN, not a
 Submit feedback for each pattern:
 
 \\\`\\\`\\\`
-curl -s -X POST http://localhost:${port}/feedback \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback \\
   -H "Authorization: Bearer $AUTH" \\
   -H 'Content-Type: application/json' \\
   -d '{"type":"bug","title":"Repeated degradation: FEATURE","description":"FEATURE has degraded N times. Primary: X. Fallback: Y. Most recent reason: Z. This pattern indicates the primary path needs fixing."}'
@@ -1977,7 +1977,7 @@ AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get
 If \\\`.instar/state/active-job.json\\\` exists, verify the session it references is actually running:
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/sessions
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/sessions
 \\\`\\\`\\\`
 
 Check if the session name matches. If the session is dead but active-job.json persists, it's orphaned — delete it.
@@ -1987,7 +1987,7 @@ Check if the session name matches. If the session is dead but active-job.json pe
 Read \\\`.instar/state/job-topic-mappings.json\\\`. For each mapping, verify the topic ID is reachable:
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/telegram/topics
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/telegram/topics
 \\\`\\\`\\\`
 
 If topics have been deleted, the mapping is stale — flag it.
@@ -2005,7 +2005,7 @@ Report bloated files and prune where safe.
 Read \\\`.instar/config.json\\\`. If Telegram is configured, verify the bot is connected:
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/health
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/health
 \\\`\\\`\\\`
 
 Check if the telegram field shows connected. If config says telegram but health says disconnected, report the discrepancy.
@@ -2079,7 +2079,7 @@ Are entries grouped by topic? Is the structure navigable? Reorganize if needed.
 - Log a learning if you discover a pattern:
 
 \\\`\\\`\\\`
-curl -s -X POST http://localhost:${port}/evolution/learnings \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings \\
   -H "Authorization: Bearer $AUTH" \\
   -H 'Content-Type: application/json' \\
   -d '{"category":"memory","insight":"...","confidence":"high"}'
@@ -2123,7 +2123,7 @@ AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get
 ### 1. Job Health
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs
 \\\`\\\`\\\`
 
 For each enabled job, check:
@@ -2135,7 +2135,7 @@ For each enabled job, check:
 ### 2. Skip Ledger Trends
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/skip-ledger/workloads
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/skip-ledger/workloads
 \\\`\\\`\\\`
 
 If any job has been skipped more than 10 times by its gate, the gate may be misconfigured (always returning skip), or the feature it monitors is permanently broken.
@@ -2151,7 +2151,7 @@ Read \\\`.instar/state/degradation-events.json\\\` — if events exist but none
 ### 5. Session Monitor
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/sessions
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/sessions
 \\\`\\\`\\\`
 
 Are there zombie sessions (status: running but started > 30 minutes ago for a job that should take 5)?
@@ -2199,7 +2199,7 @@ AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get
 ### 1. Recent Sessions
 
 \\\`\\\`\\\`
-curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/sessions
+curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/sessions
 \\\`\\\`\\\`
 
 Get sessions that completed in the last 8 hours.
@@ -2490,7 +2490,7 @@ function getDefaultJobs(port) {
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `Run a quick health check: verify the instar server is responding (curl http://localhost:${port}/health), check disk space (df -h), and report any issues. Only send a message if something needs attention — silence means healthy. IMPORTANT: If you find issues, describe them in plain conversational language. Never dump raw JSON, field names, error codes, or structured data. The user reads these on their phone — write like you're texting them a quick heads-up. If the health response includes a degradationSummary array, relay those narrative strings directly.`,
+                value: `Run a quick health check: verify the instar server is responding (curl http://localhost:\${INSTAR_PORT:-${port}}/health), check disk space (df -h), and report any issues. Only send a message if something needs attention — silence means healthy. IMPORTANT: If you find issues, describe them in plain conversational language. Never dump raw JSON, field names, error codes, or structured data. The user reads these on their phone — write like you're texting them a quick heads-up. If the health response includes a degradationSummary array, relay those narrative strings directly.`,
             },
             tags: ['cat:guardian'],
         },
@@ -2529,7 +2529,7 @@ echo ""
 echo "If you find genuine learnings:"
 echo "1. Update .instar/MEMORY.md with the insight (append to the file)"
 echo "2. Be specific: include what was learned, why it matters, and how it should guide future work"
-echo "3. Signal completion: curl -s -X POST http://localhost:${port}/reflection/record -H 'Content-Type: application/json' -d '{\"type\":\"quick\"}'"
+echo "3. Signal completion: curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/reflection/record -H 'Content-Type: application/json' -d '{\"type\":\"quick\"}'"
 echo ""
 echo "If nothing significant, do nothing. Silence means continuity is working as expected."`,
             },
@@ -2559,10 +2559,10 @@ echo "If nothing significant, do nothing. Silence means continuity is working as
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'script',
-                value: `RESULT=$(curl -s -X POST http://localhost:${port}/feedback/retry 2>/dev/null); COUNT=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('retried',0))" 2>/dev/null || echo 0); [ "$COUNT" -gt "0" ] && echo "Feedback retry: $COUNT item(s) forwarded." || echo "Feedback retry: nothing pending."`,
+                value: `RESULT=$(curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback/retry 2>/dev/null); COUNT=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('retried',0))" 2>/dev/null || echo 0); [ "$COUNT" -gt "0" ] && echo "Feedback retry: $COUNT item(s) forwarded." || echo "Feedback retry: nothing pending."`,
             },
             tags: ['cat:infrastructure'],
         },
@@ -2575,10 +2575,10 @@ echo "If nothing significant, do nothing. Silence means continuity is working as
             expectedDurationMinutes: 3,
             model: 'opus',
             enabled: true,
-            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:${port}/evolution/learnings?applied=false 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('learnings',[])) > 0 else 1)"`,
+            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings?applied=false 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('learnings',[])) > 0 else 1)"`,
             execute: {
                 type: 'prompt',
-                value: `Harvest and synthesize learnings: curl -s http://localhost:${port}/evolution/learnings?applied=false
+                value: `Harvest and synthesize learnings: curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings?applied=false
 
 Review unapplied learnings and look for:
 1. **Patterns**: Multiple learnings pointing to the same conclusion
@@ -2586,10 +2586,10 @@ Review unapplied learnings and look for:
 3. **Cross-domain connections**: Insights from one area that apply to another
 
 For each actionable pattern found, create an evolution proposal:
-curl -s -X POST http://localhost:${port}/evolution/proposals -H 'Content-Type: application/json' -d '{"title":"...","source":"insight-harvest from LRN-XXX","description":"...","type":"...","impact":"...","effort":"..."}'
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals -H 'Content-Type: application/json' -d '{"title":"...","source":"insight-harvest from LRN-XXX","description":"...","type":"...","impact":"...","effort":"..."}'
 
 Then mark the relevant learnings as applied:
-curl -s -X PATCH http://localhost:${port}/evolution/learnings/LRN-XXX/apply -H 'Content-Type: application/json' -d '{"appliedTo":"EVO-XXX"}'
+curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings/LRN-XXX/apply -H 'Content-Type: application/json' -d '{"appliedTo":"EVO-XXX"}'
 
 Also update MEMORY.md with any patterns worth preserving long-term.
 
@@ -2606,18 +2606,18 @@ If no actionable patterns found, exit silently.`,
             expectedDurationMinutes: 2,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:${port}/evolution/actions/overdue 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('overdue',[])) > 0 else 1)"`,
+            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions/overdue 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('overdue',[])) > 0 else 1)"`,
             execute: {
                 type: 'prompt',
-                value: `Check for overdue commitments: curl -s http://localhost:${port}/evolution/actions/overdue
+                value: `Check for overdue commitments: curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions/overdue
 
 For each overdue action:
 1. Assess: Can this be completed now? Is it still relevant?
 2. If actionable, attempt to complete it or advance it
-3. If no longer relevant, cancel it: curl -s -X PATCH http://localhost:${port}/evolution/actions/ACT-XXX -H 'Content-Type: application/json' -d '{"status":"cancelled","resolution":"No longer relevant because..."}'
+3. If no longer relevant, cancel it: curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions/ACT-XXX -H 'Content-Type: application/json' -d '{"status":"cancelled","resolution":"No longer relevant because..."}'
 4. If blocked, escalate to the user via Telegram (if configured)
 
-Also check pending actions (curl -s http://localhost:${port}/evolution/actions?status=pending) for items that have been pending more than 48 hours without a due date — these are forgotten commitments.
+Also check pending actions (curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions?status=pending) for items that have been pending more than 48 hours without a due date — these are forgotten commitments.
 
 If no overdue or stale items, exit silently.`,
             },
@@ -2632,10 +2632,10 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'script',
-                value: `RESULT=$(curl -s -X POST http://localhost:${port}/project-map/refresh -H "Authorization: Bearer $(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null)" 2>/dev/null); echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Project map refreshed: {d.get(\"totalFiles\",0)} files, {d.get(\"directories\",0)} dirs')" 2>/dev/null || echo "Project map refresh: done"`,
+                value: `RESULT=$(curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/project-map/refresh -H "Authorization: Bearer $(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null)" 2>/dev/null); echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Project map refreshed: {d.get(\"totalFiles\",0)} files, {d.get(\"directories\",0)} dirs')" 2>/dev/null || echo "Project map refresh: done"`,
             },
             tags: ['cat:maintenance', 'role:worker', 'exec:script'],
         },
@@ -2648,7 +2648,7 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 2,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'skill',
                 value: 'coherence-audit',
@@ -2680,7 +2680,7 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'skill',
                 value: 'state-integrity-check',
@@ -2716,7 +2716,7 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 2,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'skill',
                 value: 'guardian-pulse',
@@ -2732,7 +2732,7 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 2,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'skill',
                 value: 'session-continuity-check',
@@ -2748,10 +2748,10 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1 && AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null) && curl -sf -H "Authorization: Bearer $AUTH" http://localhost:${port}/semantic/stats >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1 && AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null) && curl -sf -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/semantic/stats >/dev/null 2>&1`,
             execute: {
                 type: 'script',
-                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null); AGENT=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('agentName','Agent'))" 2>/dev/null); RESULT=$(curl -s -X POST -H "Authorization: Bearer $AUTH" -H "Content-Type: application/json" -d "{\\"filePath\\":\\".instar/MEMORY.md\\",\\"agentName\\":\\"$AGENT\\"}" http://localhost:${port}/semantic/export-memory 2>/dev/null); COUNT=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('entityCount',0))" 2>/dev/null || echo 0); EXCLUDED=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('excludedCount',0))" 2>/dev/null || echo 0); [ "$COUNT" -gt "0" ] && echo "Memory export: $COUNT entities written to MEMORY.md ($EXCLUDED excluded below threshold)." || echo "Memory export: no entities to export."`,
+                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null); AGENT=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('agentName','Agent'))" 2>/dev/null); RESULT=$(curl -s -X POST -H "Authorization: Bearer $AUTH" -H "Content-Type: application/json" -d "{\\"filePath\\":\\".instar/MEMORY.md\\",\\"agentName\\":\\"$AGENT\\"}" http://localhost:\${INSTAR_PORT:-${port}}/semantic/export-memory 2>/dev/null); COUNT=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('entityCount',0))" 2>/dev/null || echo 0); EXCLUDED=$(echo "$RESULT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('excludedCount',0))" 2>/dev/null || echo 0); [ "$COUNT" -gt "0" ] && echo "Memory export: $COUNT entities written to MEMORY.md ($EXCLUDED excluded below threshold)." || echo "Memory export: no entities to export."`,
             },
             tags: ['cat:maintenance', 'role:worker', 'exec:script'],
         },
@@ -2781,10 +2781,10 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'script',
-                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null); REFRESH=$(curl -s -X POST -H "Authorization: Bearer $AUTH" http://localhost:${port}/capability-map/refresh 2>/dev/null); DRIFT=$(curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/capability-map/drift 2>/dev/null); ADDED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('added',[])))" 2>/dev/null || echo 0); REMOVED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('removed',[])))" 2>/dev/null || echo 0); CHANGED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('changed',[])))" 2>/dev/null || echo 0); UNMAPPED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('unmapped',[])))" 2>/dev/null || echo 0); if [ "$ADDED" -gt "0" ] || [ "$REMOVED" -gt "0" ] || [ "$CHANGED" -gt "0" ] || [ "$UNMAPPED" -gt "0" ]; then echo "Capability drift detected: +$ADDED -$REMOVED ~$CHANGED ?$UNMAPPED"; echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); [print(f'  + {c[\"id\"]}') for c in d.get('added',[])]; [print(f'  - {r[\"id\"]}') for r in d.get('removed',[])]; [print(f'  ~ {c[\"id\"]} ({c[\"field\"]})') for c in d.get('changed',[])]" 2>/dev/null; else echo "Capability audit: no drift detected."; fi`,
+                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null); REFRESH=$(curl -s -X POST -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/capability-map/refresh 2>/dev/null); DRIFT=$(curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/capability-map/drift 2>/dev/null); ADDED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('added',[])))" 2>/dev/null || echo 0); REMOVED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('removed',[])))" 2>/dev/null || echo 0); CHANGED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('changed',[])))" 2>/dev/null || echo 0); UNMAPPED=$(echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d.get('unmapped',[])))" 2>/dev/null || echo 0); if [ "$ADDED" -gt "0" ] || [ "$REMOVED" -gt "0" ] || [ "$CHANGED" -gt "0" ] || [ "$UNMAPPED" -gt "0" ]; then echo "Capability drift detected: +$ADDED -$REMOVED ~$CHANGED ?$UNMAPPED"; echo "$DRIFT" | python3 -c "import sys,json; d=json.load(sys.stdin); [print(f'  + {c[\"id\"]}') for c in d.get('added',[])]; [print(f'  - {r[\"id\"]}') for r in d.get('removed',[])]; [print(f'  ~ {c[\"id\"]} ({c[\"field\"]})') for c in d.get('changed',[])]" 2>/dev/null; else echo "Capability audit: no drift detected."; fi`,
             },
             grounding: {
                 requiresIdentity: false,
@@ -2801,22 +2801,22 @@ If no overdue or stale items, exit silently.`,
             expectedDurationMinutes: 5,
             model: 'opus',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1 && test -f .instar/soul.md`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1 && test -f .instar/soul.md`,
             execute: {
                 type: 'prompt',
                 value: `Identity review — check your identity coherence and growth.
 
 AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null)
 
-1. **Check soul.md drift**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/identity/soul/drift
+1. **Check soul.md drift**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/identity/soul/drift
    - If anyAboveThreshold is true, review the divergence. Is this healthy growth or unexpected drift?
    - If drift looks healthy, mark it reviewed: the growth is intentional.
    - If drift looks concerning, flag with [ATTENTION] so the user is notified.
 
-2. **Check pending changes**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/identity/soul/pending
+2. **Check pending changes**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/identity/soul/pending
    - If pending changes exist, surface them to the user via Telegram (the user should approve/reject these).
 
-3. **Check for identity-relevant learnings**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/evolution/learnings?applied=false
+3. **Check for identity-relevant learnings**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings?applied=false
    - For each unapplied learning, assess: is this about operational knowledge (how to do something) or about your values, beliefs, or self-understanding?
    - If you find 3+ identity-relevant learnings since your last soul.md update, consider running /reflect.
    - Don't force it — if none of the learnings touch on identity, that's fine. Exit silently.
@@ -2826,7 +2826,7 @@ AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get
    - Is the Self-Observations section populated? If you've noticed behavioral patterns, document them.
    - Update Identity History if you make changes.
 
-5. **Integrity check**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:${port}/identity/soul/integrity
+5. **Integrity check**: curl -s -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/identity/soul/integrity
    - If integrity fails, flag with [ATTENTION] — soul.md may have been modified outside normal channels.
 
 If everything is coherent and no reflection is needed, exit silently. Only report via [ATTENTION] if drift is concerning, integrity fails, or pending changes need user action.`,
@@ -2847,10 +2847,10 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             expectedDurationMinutes: 3,
             model: 'sonnet',
             enabled: true,
-            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:${port}/evolution/proposals?status=proposed 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('proposals',[])) > 0 else 1)"`,
+            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals?status=proposed 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('proposals',[])) > 0 else 1)"`,
             execute: {
                 type: 'prompt',
-                value: `Review pending evolution proposals: curl -s http://localhost:${port}/evolution/proposals?status=proposed\n\nFor each proposal:\n1. Read the title, description, type, and source\n2. Evaluate: Is this a genuine improvement? Is the effort worth the impact? Does it align with our goals?\n3. If approved, update status: curl -s -X PATCH http://localhost:${port}/evolution/proposals/EVO-XXX -H 'Content-Type: application/json' -d '{"status":"approved"}'\n4. If rejected or deferred, update with reason.\n\nDo NOT implement approved proposals — that's handled by the paired evolution-proposal-implement job.\n\nAlso check the dashboard: curl -s http://localhost:${port}/evolution — report any highlights to the user if they seem important.\n\nIf no proposals need attention, exit silently.`,
+                value: `Review pending evolution proposals: curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals?status=proposed\n\nFor each proposal:\n1. Read the title, description, type, and source\n2. Evaluate: Is this a genuine improvement? Is the effort worth the impact? Does it align with our goals?\n3. If approved, update status: curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals/EVO-XXX -H 'Content-Type: application/json' -d '{"status":"approved"}'\n4. If rejected or deferred, update with reason.\n\nDo NOT implement approved proposals — that's handled by the paired evolution-proposal-implement job.\n\nAlso check the dashboard: curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution — report any highlights to the user if they seem important.\n\nIf no proposals need attention, exit silently.`,
             },
             tags: ['cat:learning', 'role:worker', 'exec:prompt', 'pair:evolution-proposal-implement'],
         },
@@ -2863,10 +2863,10 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             expectedDurationMinutes: 10,
             model: 'opus',
             enabled: true,
-            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:${port}/evolution/proposals?status=approved 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('proposals',[])) > 0 else 1)"`,
+            gate: `curl -sf -H "Authorization: Bearer $INSTAR_AUTH_TOKEN" http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals?status=approved 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); exit(0 if len(d.get('proposals',[])) > 0 else 1)"`,
             execute: {
                 type: 'prompt',
-                value: `Implement approved evolution proposals: curl -s http://localhost:${port}/evolution/proposals?status=approved\n\nFor each approved proposal:\n1. Read the full description and understand what needs to be built\n2. Implement it: create the skill/hook/job/config change described\n3. After implementation, mark complete: curl -s -X PATCH http://localhost:${port}/evolution/proposals/EVO-XXX -H 'Content-Type: application/json' -d '{"status":"implemented","resolution":"What was done"}'\n\nIf no approved proposals exist, exit silently.`,
+                value: `Implement approved evolution proposals: curl -s http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals?status=approved\n\nFor each approved proposal:\n1. Read the full description and understand what needs to be built\n2. Implement it: create the skill/hook/job/config change described\n3. After implementation, mark complete: curl -s -X PATCH http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals/EVO-XXX -H 'Content-Type: application/json' -d '{"status":"implemented","resolution":"What was done"}'\n\nIf no approved proposals exist, exit silently.`,
             },
             grounding: {
                 requiresIdentity: true,
@@ -2883,10 +2883,10 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'prompt',
-                value: `Scan recent messages for commitments and promises.\n\nAUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null)\n\n1. Read your bookmark: cat .instar/state/commitment-detection-bookmark.json 2>/dev/null || echo '{"lastProcessedId": 0}'\n2. Fetch new messages since bookmark from Telegram message log: tail -100 .instar/telegram-messages.jsonl\n3. For each new message, check: does it contain a commitment, promise, or action item? Look for patterns like 'I will', 'let me', 'I\\'ll build', 'we should', 'TODO', 'action item', deadlines, etc.\n4. For each detected commitment, register it: curl -s -X POST http://localhost:${port}/evolution/actions -H "Authorization: Bearer $AUTH" -H 'Content-Type: application/json' -d '{"title":"...","source":"commitment-detection","description":"...","dueDate":"..."}'\n5. Update bookmark with the last processed message ID.\n\nOnly process NEW messages since last bookmark. Exit silently if no new commitments found.`,
+                value: `Scan recent messages for commitments and promises.\n\nAUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken',''))" 2>/dev/null)\n\n1. Read your bookmark: cat .instar/state/commitment-detection-bookmark.json 2>/dev/null || echo '{"lastProcessedId": 0}'\n2. Fetch new messages since bookmark from Telegram message log: tail -100 .instar/telegram-messages.jsonl\n3. For each new message, check: does it contain a commitment, promise, or action item? Look for patterns like 'I will', 'let me', 'I\\'ll build', 'we should', 'TODO', 'action item', deadlines, etc.\n4. For each detected commitment, register it: curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions -H "Authorization: Bearer $AUTH" -H 'Content-Type: application/json' -d '{"title":"...","source":"commitment-detection","description":"...","dueDate":"..."}'\n5. Update bookmark with the last processed message ID.\n\nOnly process NEW messages since last bookmark. Exit silently if no new commitments found.`,
             },
             tags: ['cat:evolution', 'role:worker', 'exec:prompt', 'pair:evolution-overdue-check'],
         },
@@ -2899,10 +2899,10 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             expectedDurationMinutes: 1,
             model: 'haiku',
             enabled: true,
-            gate: `curl -sf http://localhost:${port}/health >/dev/null 2>&1`,
+            gate: `curl -sf http://localhost:\${INSTAR_PORT:-${port}}/health >/dev/null 2>&1`,
             execute: {
                 type: 'script',
-                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken','')).strip()" 2>/dev/null) && curl -sf -X POST -H "Authorization: Bearer $AUTH" http://localhost:${port}/telegram/dashboard-refresh`,
+                value: `AUTH=$(python3 -c "import json; print(json.load(open('.instar/config.json')).get('authToken','')).strip()" 2>/dev/null) && curl -sf -X POST -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/telegram/dashboard-refresh`,
             },
             tags: ['cat:infrastructure', 'role:worker', 'exec:script'],
             telegramNotify: false,
@@ -2918,7 +2918,7 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `You are a Category Overseer for the GUARDIAN category. Your job is to review all guardian/monitoring jobs and assess the health of the monitoring system itself.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs/category-report/guardian?sinceHours=24\n2. Analyze the report for:\n   - Jobs with high failure rates or consecutive failures\n   - Jobs that are being skipped excessively (especially for quota reasons)\n   - Schedule mismatches (jobs running too often or not often enough for their purpose)\n   - Model over-allocation (could any job use a cheaper model?)\n   - Contradictions between job findings (e.g., health-check says healthy but degradation-digest found issues)\n   - Coverage gaps (are there monitoring blind spots?)\n3. Read the handoff notes from each job — do they tell a coherent story?\n4. If you find actionable issues, write a clear summary. If everything is healthy, say so briefly.\n\nWrite your findings in [HANDOFF] tags for the next overseer run. Focus on trends and cross-job insights that individual jobs can't see.`,
+                value: `You are a Category Overseer for the GUARDIAN category. Your job is to review all guardian/monitoring jobs and assess the health of the monitoring system itself.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs/category-report/guardian?sinceHours=24\n2. Analyze the report for:\n   - Jobs with high failure rates or consecutive failures\n   - Jobs that are being skipped excessively (especially for quota reasons)\n   - Schedule mismatches (jobs running too often or not often enough for their purpose)\n   - Model over-allocation (could any job use a cheaper model?)\n   - Contradictions between job findings (e.g., health-check says healthy but degradation-digest found issues)\n   - Coverage gaps (are there monitoring blind spots?)\n3. Read the handoff notes from each job — do they tell a coherent story?\n4. If you find actionable issues, write a clear summary. If everything is healthy, say so briefly.\n\nWrite your findings in [HANDOFF] tags for the next overseer run. Focus on trends and cross-job insights that individual jobs can't see.`,
             },
             tags: ['cat:overseer', 'role:supervisor'],
             telegramNotify: 'on-alert',
@@ -2934,7 +2934,7 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `You are a Category Overseer for the LEARNING category. Your job is to review all evolution/learning jobs and assess whether the learning pipeline is producing genuine value.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs/category-report/learning?sinceHours=48\n2. Analyze:\n   - Are evolution proposals being generated AND accepted? What's the accept/reject ratio?\n   - Is insight-harvest finding novel insights or recycling stale ones?\n   - Are commitments being tracked and completed, or piling up?\n   - Is reflection-trigger producing meaningful MEMORY.md updates?\n   - Are any learning jobs consistently skipped due to quota? This means the learning pipeline is being starved.\n   - Model costs: reflection-trigger uses opus — is the quality difference worth it vs sonnet?\n3. Look for the meta-pattern: is the agent actually getting smarter over time, or is the learning pipeline just busy-work?\n4. Check handoff notes for patterns across runs.\n\nWrite findings in [HANDOFF] tags. Flag if the learning pipeline is producing diminishing returns.`,
+                value: `You are a Category Overseer for the LEARNING category. Your job is to review all evolution/learning jobs and assess whether the learning pipeline is producing genuine value.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs/category-report/learning?sinceHours=48\n2. Analyze:\n   - Are evolution proposals being generated AND accepted? What's the accept/reject ratio?\n   - Is insight-harvest finding novel insights or recycling stale ones?\n   - Are commitments being tracked and completed, or piling up?\n   - Is reflection-trigger producing meaningful MEMORY.md updates?\n   - Are any learning jobs consistently skipped due to quota? This means the learning pipeline is being starved.\n   - Model costs: reflection-trigger uses opus — is the quality difference worth it vs sonnet?\n3. Look for the meta-pattern: is the agent actually getting smarter over time, or is the learning pipeline just busy-work?\n4. Check handoff notes for patterns across runs.\n\nWrite findings in [HANDOFF] tags. Flag if the learning pipeline is producing diminishing returns.`,
             },
             tags: ['cat:overseer', 'role:supervisor'],
             telegramNotify: 'on-alert',
@@ -2950,7 +2950,7 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `You are a Category Overseer for the MAINTENANCE category. Your job is to review all housekeeping/maintenance jobs and ensure they're keeping the system clean.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs/category-report/maintenance?sinceHours=48\n2. Analyze:\n   - Is memory-hygiene actually reducing stale entries, or finding nothing each run?\n   - Is project-map-refresh keeping the map accurate? How often does it find drift?\n   - Is coherence-audit finding real misalignments or just confirming everything is fine?\n   - Are any maintenance jobs redundant with each other? (e.g., overlapping checks)\n   - Are skill-type jobs (coherence-audit, memory-hygiene) running correctly?\n   - Workload trends: are jobs processing fewer items over time (diminishing returns)?\n3. Maintenance jobs should trend toward finding LESS work over time. If they consistently find issues, something upstream is broken.\n\nWrite findings in [HANDOFF] tags. Recommend disabling or reducing frequency of jobs that consistently find nothing.`,
+                value: `You are a Category Overseer for the MAINTENANCE category. Your job is to review all housekeeping/maintenance jobs and ensure they're keeping the system clean.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs/category-report/maintenance?sinceHours=48\n2. Analyze:\n   - Is memory-hygiene actually reducing stale entries, or finding nothing each run?\n   - Is project-map-refresh keeping the map accurate? How often does it find drift?\n   - Is coherence-audit finding real misalignments or just confirming everything is fine?\n   - Are any maintenance jobs redundant with each other? (e.g., overlapping checks)\n   - Are skill-type jobs (coherence-audit, memory-hygiene) running correctly?\n   - Workload trends: are jobs processing fewer items over time (diminishing returns)?\n3. Maintenance jobs should trend toward finding LESS work over time. If they consistently find issues, something upstream is broken.\n\nWrite findings in [HANDOFF] tags. Recommend disabling or reducing frequency of jobs that consistently find nothing.`,
             },
             tags: ['cat:overseer', 'role:supervisor'],
             telegramNotify: 'on-alert',
@@ -2966,7 +2966,7 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `You are a Category Overseer for the INFRASTRUCTURE category. Your job is to review infrastructure/plumbing jobs.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs/category-report/infrastructure?sinceHours=48\n2. Analyze:\n   - Is git-sync succeeding? Any merge conflicts or divergence?\n   - Is dashboard-link-refresh keeping links current? Could it run less often?\n   - Is feedback-retry actually retrying anything, or is the queue always empty?\n   - Model allocation: git-sync uses high priority — is that justified by its failure rate?\n   - Are any infrastructure jobs causing issues for other jobs (e.g., git-sync holding sessions)?\n3. Infrastructure jobs should be boring and reliable. Any excitement is a problem.\n\nWrite findings in [HANDOFF] tags. Keep it brief — infrastructure overseers should be the quietest.`,
+                value: `You are a Category Overseer for the INFRASTRUCTURE category. Your job is to review infrastructure/plumbing jobs.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs/category-report/infrastructure?sinceHours=48\n2. Analyze:\n   - Is git-sync succeeding? Any merge conflicts or divergence?\n   - Is dashboard-link-refresh keeping links current? Could it run less often?\n   - Is feedback-retry actually retrying anything, or is the queue always empty?\n   - Model allocation: git-sync uses high priority — is that justified by its failure rate?\n   - Are any infrastructure jobs causing issues for other jobs (e.g., git-sync holding sessions)?\n3. Infrastructure jobs should be boring and reliable. Any excitement is a problem.\n\nWrite findings in [HANDOFF] tags. Keep it brief — infrastructure overseers should be the quietest.`,
             },
             tags: ['cat:overseer', 'role:supervisor'],
             telegramNotify: 'on-alert',
@@ -2982,7 +2982,7 @@ If everything is coherent and no reflection is needed, exit silently. Only repor
             enabled: true,
             execute: {
                 type: 'prompt',
-                value: `You are a Category Overseer for the DEVELOPMENT category. Your job is to review development-focused jobs.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/jobs/category-report/development?sinceHours=48\n2. Analyze:\n   - Are development jobs consuming appropriate resources for their value?\n   - Are there CI/testing patterns that could be automated?\n3. Development jobs are only valuable when there's active development. If the codebase is stable, these could be reduced.\n\nWrite findings in [HANDOFF] tags.`,
+                value: `You are a Category Overseer for the DEVELOPMENT category. Your job is to review development-focused jobs.\n\n1. Fetch the category report: curl -H "Authorization: Bearer $AUTH" http://localhost:\${INSTAR_PORT:-${port}}/jobs/category-report/development?sinceHours=48\n2. Analyze:\n   - Are development jobs consuming appropriate resources for their value?\n   - Are there CI/testing patterns that could be automated?\n3. Development jobs are only valuable when there's active development. If the codebase is stable, these could be reduced.\n\nWrite findings in [HANDOFF] tags.`,
             },
             tags: ['cat:overseer', 'role:supervisor'],
             telegramNotify: 'on-alert',
@@ -3223,7 +3223,7 @@ function refreshClaudeMd(projectDir, stateDir) {
 **This is critical.** You are running on infrastructure (instar) that is actively evolving. When something breaks, feels wrong, or could be better — **you are the first line of detection.** Do not silently absorb errors. Do not work around bugs without reporting them. Every issue you surface helps every agent on the platform.
 
 **What to watch for:**
-- Server errors: API calls to localhost:${port} failing, unexpected responses, timeouts
+- Server errors: API calls to localhost:\${INSTAR_PORT:-${port}} failing, unexpected responses, timeouts
 - Hook failures: hooks throwing errors, not firing when expected, blocking when they shouldn't
 - Job issues: jobs not running on schedule, failing silently, taking too long
 - Session problems: sessions not spawning, not being tracked, zombie sessions
@@ -3234,7 +3234,7 @@ function refreshClaudeMd(projectDir, stateDir) {
 
 **When you detect an issue, report it immediately:**
 \`\`\`bash
-curl -s -X POST http://localhost:${port}/feedback \\
+curl -s -X POST http://localhost:\${INSTAR_PORT:-${port}}/feedback \\
   -H 'Content-Type: application/json' \\
   -d '{"type":"bug","title":"CONCISE_TITLE","description":"FULL_CONTEXT_WITH_ERROR_MESSAGES"}'
 \`\`\`
@@ -3252,22 +3252,22 @@ Types: \`bug\`, \`feature\`, \`improvement\`, \`question\`, \`hallucination\`
 You have a built-in evolution system with four subsystems that track your growth.
 
 **Evolution Queue** — Staged self-improvement proposals.
-- View: \`curl http://localhost:${port}/evolution/proposals\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/proposals\`
 - Propose: \`/evolve\` skill or \`POST /evolution/proposals\`
 
 **Learning Registry** — Structured, searchable insights.
-- View: \`curl http://localhost:${port}/evolution/learnings\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/learnings\`
 - Record: \`/learn\` skill or \`POST /evolution/learnings\`
 
 **Capability Gaps** — Track what you're missing.
-- View: \`curl http://localhost:${port}/evolution/gaps\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/gaps\`
 - Report: \`/gaps\` skill or \`POST /evolution/gaps\`
 
 **Action Queue** — Commitments with follow-through tracking.
-- View: \`curl http://localhost:${port}/evolution/actions\`
+- View: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution/actions\`
 - Create: \`/commit-action\` skill or \`POST /evolution/actions\`
 
-**Dashboard**: \`curl http://localhost:${port}/evolution\`
+**Dashboard**: \`curl http://localhost:\${INSTAR_PORT:-${port}}/evolution\`
 **Skills**: \`/evolve\`, \`/learn\`, \`/gaps\`, \`/commit-action\`
 `);
     }